EVENT_TRACING_FATAL_ERROR

Code: 0x11d (285)

As HRESULT:As NTSTATUS:

Description

The EVENT_TRACING_FATAL_ERROR bug check has a value of 0x0000011D. This bug check indicates that the Event Tracing subsystem has encountered an unexpected fatal error.

Important

This article is for programmers. If you're a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

Resolution

In a kernel debugger, use the !analyze -v command to perform the initial bug check analysis. Parameter 1 will list the subtype of the bugcheck.

0x01 : Unable to initialize security.

0x02 : Unable to initialize processor.

0x03 : Kernel mode registration corruption.

0x04 : Invalid handle in unregistration.

0x05 : Data overrun in EventWrite call.

0x06 : Event has been lost.

0x07 : Trace buffer corruption.

0x08 : Unable to allocate cache-aware rundown protection for ETW LoggerContext. Parameter 2 will contain the Logger Id.

0x09 : The reference count of ETW GuidEntry is illegal for the current state of the object. Parameter 2 will contain a pointer to ETW_GUID_ENTRY.

See also

Crash dump analysis using the Windows debuggers (WinDbg)

Analyzing a Kernel-Mode Dump File with WinDbg

Article text from the Windows driver documentation (opens in a new tab), by Microsoft, under the CC BY 4.0 (opens in a new tab) licence.

Associated Modules

ModuleCodeFound inDescription
EventCreate.exe0x11d78.11011%1
mispace.dll0x11d1011Resizing volume
storagewmi.dll0x11d1011Resizing volume
webservices.dll0x11d78.11011The signed 32 bit integer %1 could not be converted to an unsigned 16 bit integer because it is out of range.
4 entries