Basic Facts, Periodic Error and Defamiliarizing Effect
This is a synthesized case study with the simplified ETW77 trace output based on real events (consider it as an exercise in a software narrative fiction). In a client-server environment a server session was always active regardless of whether a client was active or not. There was a workaround to enable a registry key to force checking for user activity via CheckActivity registry key. Unfortunately this didn't help and a software trace was recorded for the offline analysis. First, we checked for Basic Facts (Volume 3, page 345) and found the correspondence that confirmed the registry key setting:
# PID TID Message [...] 3200 1428 5476 ...