| Previous | Next |
| BITLOCKER_FATAL_ERROR | WHEA_INTERNAL_ERROR |
DRIVER_VIOLATION
General driver rule violation
DRIVER_VIOLATION is bug check code 0x00000121. The built-in table identifies it as DRIVER_VIOLATION
; the useful diagnostic question is what Windows component raised the stop and which invariant failed.
This code is a broad driver-integrity stop. It is useful when the dump points to a driver action that violates kernel rules but does not fit a narrower verifier, IRQL, pool, or WDF-specific bug check.
How to read the parameters
- The arguments are best interpreted from !analyze -v and the call stack for the specific Windows build.
- A named driver in the analysis is more important than the symbolic bug check name.
- Related codes include DRIVER_VERIFIER_DETECTED_VIOLATION, WDF_VIOLATION, and DRIVER_IRQL_NOT_LESS_OR_EQUAL.
What to check in the dump
- Start with the stack, KiBugCheckDriver if present, and recently loaded third-party drivers.
- Use Driver Verifier selectively for the suspect driver rather than enabling every option system-wide on production machines.
- Collect reproduction steps and I/O workload because the violation may appear only under specific timing.
References
Looking for a different code? Search another status or error code.