| Previous | Next |
| FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION | VIDEO_MEMORY_MANAGEMENT_INTERNAL |
WDF_VIOLATION
Kernel-Mode Driver Framework violation
WDF_VIOLATION is bug check code 0x0000010D. The built-in table identifies it as WDF_VIOLATION
; the useful diagnostic question is what Windows component raised the stop and which invariant failed.
This bug check is raised by the Windows Driver Frameworks runtime when a KMDF driver violates framework rules: wrong object handle type, bad request lifecycle, lock misuse, power-operation timeout, invalid PnP/power ownership, DMA transaction state error, or callback IRQL mismatch.
How to read the parameters
- Parameter 1 is the framework-specific violation code.
- Other parameters can identify a WDF object, request, DMA transaction, callback, or WDF log structure depending on Parameter 1.
- Parameter 4 is reserved in the public documentation.
What to check in the dump
- Use !wdfkd.wdflogdump for the failing driver when symbols and WDF extensions are available.
- For request lifecycle failures, inspect WDFREQUEST references, queues, and completion paths.
- For power and PnP failures, check ownership, callback return IRQL, and whether a driver blocked pageable work after the power stack changed state.
References
Looking for a different code? Search another status or error code.