Her latest case was an anomaly: a word processor on a classified government terminal kept closing itself. No error message. No crash dump. It simply vanished , like a thought interrupted.
She typed:
She realized the truth: the word processor wasn't crashing. It was a canary in a coal mine. Some deeper kernel-level agent—maybe an AI governor, maybe an APT—was using WNF as a covert channel. It would query the state data of any process that touched classified information. If the state didn't match a pre-approved pattern, the process was terminated.
NtQueryWnfStateData(\System\ProcessMon\Thread_4428)
When the machine went dark, the last thing she saw was her own reflection in the black screen—wondering if, somewhere in the kernel’s non-paged pool, a tiny state flag labeled ARIS_THORNE_ACTIVE was still set to TRUE .
Aris ran the GUID through a hash reverse lookup. Nothing in public databases. But her kernel debugger had a live pipe to the machine. She decided to peek at the actual state data being returned.
All signs pointed to a deadlock in user mode. But after three weeks, Aris was desperate. She loaded WinDbg, attached to the live process, and began walking up the call stack of the suspended thread.
dt nt!_WNF_STATE_DATA (address)
