| Previous | Next |
| RESOURCE_OWNER_POINTER_INVALID | DRIVE_EXTENDER |
DPC_WATCHDOG_VIOLATION
DPC and ISR watchdog
DPC_WATCHDOG_VIOLATION is bug check code 0x00000133.
This bug check is raised when the system spends too long at elevated IRQL, either in a single DPC/ISR path or cumulatively. It is a latency watchdog for code that prevents normal scheduling and interrupt processing.
How to read the parameters
- Parameter 1 distinguishes a single long-running DPC/ISR from cumulative time at DISPATCH_LEVEL or above.
- Other parameters identify timeout information and triage blocks depending on the case.
- A storage, network, graphics, or security driver can be involved if it monopolizes high-IRQL execution.
What to check in the dump
- Use !analyze -v, DPC/ISR-related debugger output, and stack traces to identify the long-running code path.
- Check driver updates, interrupt storms, high-rate device activity, and code paths that hold spin locks or busy-wait.
- Do not confuse this with CLOCK_WATCHDOG_TIMEOUT; 0x133 is about elevated IRQL/DPC time, not a missing processor clock interrupt.
References
Looking for a different code? Search another status or error code.