No public Windows contract cited here guarantees that a classic kernel Process End event timestamp is less than or equal to—or strictly less than—the instant when the process object becomes signaled.
What is documented
-
[GUID]is the classic kernelProcessGuid, distinct from the NT Kernel Logger session-control GUID.^1^ - For that event class, type/opcode 2 is
EVENT_TRACE_TYPE_END, the End process event.^2^ - The classic event header’s
TimeStampis described as the time the event occurred. With raw timestamp processing, its representation depends on the session’sWnode.ClientContext.^3^ - With
ClientContext == 1, the timestamp uses QPC.ReservedFlags == 1confirms the raw ETL timestamp scale is QPC, andPerfFreqsupplies the conversion frequency.^4^ -
WaitForSingleObjectreturningWAIT_TIMEOUTsays the object was nonsignaled when the wait completed by timeout;WAIT_OBJECT_0says the object was signaled when that wait returned.^5^ - In the documented
ExitProcesssequence, the process object becomes signaled at step 8. Returning from an application’smainresults in a call toExitProcess.^6^
What is not documented is where the classic Process End event is timestamped or emitted relative to step 8 of that termination sequence. The generic statement that TimeStamp contains “the time that the event occurred” does not define the event’s instrumentation point and therefore cannot establish either:
- Non-strict ordering:
T_end ≤ T_signaled, including equality; or - Strict precedence:
T_end < T_signaled.
Nor does the ExitProcess sequence mention the ETW Process End event. Combining those two independently documented behaviors would be an implementation inference, not a behavioral contract.
Event version and build applicability
The public classic Process documentation identifies an EventVersion(3) parent class and maps End events to Process_TypeGroup1.^2^ That payload class documents the End event and fields such as ExitStatus, but it does not define any ordering against process-object signaling.^7^
The separately documented Process_V2 lineage covers event version 2.^8^ The available public documentation does not describe the semantics or instrumentation point of the observed version-4 End record. Consequently, it supplies no version-4 or build-specific ordering contract for Windows build 26100, including the managed-return path.
The missing UBR, complete kernel patch version, and kernel binary hash would matter if the objective were to identify and analyze the exact implementation. They would not turn undocumented implementation ordering into a supported Windows contract. For implementation-level attribution, the useful missing data would include:
- Exact guest build and UBR.
- Relevant kernel binary versions and hashes.
- Matching symbols.
- A kernel termination/event-emission call stack or another direct observation of both instrumentation points.
No available documentation supports extending an ordering claim to TerminateProcess, abnormal termination, or other paths either.
Interpretation of the preserved experiment
Your current conclusion—indeterminate—is appropriate:
- Each End timestamp falling inside a timeout/success interval is consistent with multiple possible orderings.
- The post-timeout QPC value was correctly excluded as a nonsignaled bound.
- The post-success QPC value is only an upper observation bound, not the signal-transition time.
- Zero-timeout polling could narrow observational intervals, but it still would not establish the exact transition instant or create a documented ETW/signaling guarantee.
- For QPC values acquired on different threads, Microsoft advises treating differences of ±1 tick as ambiguously ordered.^9^
Therefore, the trace neither demonstrates a Windows defect nor proves T_end ≤ T_signaled or T_end < T_signaled. Establishing behavior for one exact kernel build would require implementation analysis or direct instrumentation, and any resulting conclusion should be scoped to that build and exercised termination path.
References