| Previous | Next |
| ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE | TOO_MANY_RECURSIVE_FAULTS |
EVENT_TRACING_FATAL_ERROR
ETW fatal tracing failure
EVENT_TRACING_FATAL_ERROR is bug check code 0x0000011D. The built-in table identifies it as EVENT_TRACING_FATAL_ERROR
; the useful diagnostic question is what Windows component raised the stop and which invariant failed.
This code belongs to the kernel Event Tracing for Windows path. It is not a normal trace-session warning; Windows stopped because tracing state or a tracing operation became inconsistent enough to be fatal.
How to read the parameters
- Use the stack and active trace-session state to identify whether the issue involves logger setup, buffers, provider state, or an ETW control operation.
- The bug check parameters are less useful without the exact build and symbols.
- High trace volume and low resources can expose tracing bugs but are not automatically the root cause.
What to check in the dump
- List active ETW sessions and recent tracing tools if the machine can be reproed.
- Check security, performance, antivirus, and diagnostic agents that create kernel trace sessions.
- Correlate with low-memory conditions and with drivers that register high-volume providers.
References
Looking for a different code? Search another status or error code.