The SYSTEM_TRACE_HEADER is one of several types of fixed-size header that introduce variable-size data for events that are logged through Event Tracing for Windows (ETW). As with other types of event, those that begin with a SYSTEM_TRACE_HEADER accumulate first in trace buffers. To have these events persist in this raw form for ready inspection, configure the event tracing session to flush the trace buffers to an Event Trace Log (ETL) file.

Documentation Status

The SYSTEM_TRACE_HEADER is not documented, but a C-language definition is published in the NTWMI.H header from some editions of the Windows Driver Kit (WDK) for Windows 10.

Were it not for this relatively recent and possibly unintended disclosure, much but certainly not all would anyway be known from type information in symbol files. Curiously though, type information for this structure has never appeared in any public symbol files for the kernel or for the obvious low-level user-mode DLLs. In the whole of Microsoft’s packages of public symbol files, relevant type information is unknown before Windows 8 and appears in symbol files only for appxdeploymentclient.dll, certenroll.dll (before Windows 10) and


The SYSTEM_TRACE_HEADER is 0x20 bytes in both 32-bit and 64-bit Windows in all known versions. Be aware however that the structure can exist in a so-called compact form that is only 0x18 bytes.

Offset Definition Remarks
union {
    ULONG Marker;
    struct {
        USHORT Version;
        UCHAR HeaderType;
        UCHAR Flags;
union {
    ULONG Header;
ULONG ThreadId;
ULONG ProcessId;
last member in compact SYSTEM_TRACE_HEADER
ULONG KernelTime;
ULONG UserTime;

The first 4 bytes have common elements in all the various Trace Headers. All have the high bit set in the Flags and all but one have the high two bits set. What distinguishes a header as continuing specifically as a SYSTEM_TRACE_HEADER is the HeaderType. NTWMI.H defines the following:

Value Name Implied Layout
0x01 TRACE_HEADER_TYPE_SYSTEM32 full 0x20 bytes of header followed by 32-bit event data
0x02 TRACE_HEADER_TYPE_SYSTEM64 full 0x20 bytes of header followed by 64-bit event data
0x03 TRACE_HEADER_TYPE_COMPACT32 first 0x18 bytes of header followed by 32-bit event data
0x04 TRACE_HEADER_TYPE_COMPACT64 first 0x18 bytes of header followed by 64-bit event data

Also defined in NTWMI.H are combinations of the Flags and HeaderType, ready for use as a basis for the Marker in the internal headers:

Value Name
0xC0010000 (32-bit event data)
0xC0020000 (64-bit event data)
0xC0030000 (32-bit event data)
0xC0040000 (64-bit event data)

To these markers must yet be added the Version. Though NTWMI.H defines a 16-bit Version, the kernel treats it as 8-bit. It is not presently clear what is meant by this Version. Both 0x02 and 0x03 are observed in Windows 10.

The WMI_TRACE_PACKET at offset 0x04 is two words:

Offset Definition
union {
    USHORT HookId;
    struct {
        UCHAR Type;
        UCHAR Group;

The total size of data for the event, i.e., both the fixed-size header and the variable-size event data, is given by the Size member of the Packet, i.e., at offset 0x04 in the header. The HookId at offset 0x06 in the header tells what type of event is logged and determines the meaning of whatever data follows the header. In the absense of an EVENT_DESCRIPTOR for events that have a SYSTEM_TRACE_HEADER, the HookId is effectively the event identifier. A separate list of these system events is in preparation.