| Previous | Next |
| ACTIVE_EX_WORKER_THREAD_TERMINATION | DIRTY_MAPPED_PAGES_CONGESTION |
THREAD_STUCK_IN_DEVICE_DRIVER
THREAD_STUCK_IN_DEVICE_DRIVER Parameters
| Parameter | Description |
|---|---|
1 |
A pointer to the stuck thread object |
2 |
A pointer to the DEFERRED_WATCHDOG object |
3 |
A pointer to the offending driver name |
4 |
In the kernel debugger: The number of times the "intercepted" bug check 0xEA was hit On the blue screen: 1 |
Cause
A device driver is spinning in an infinite loop, most likely waiting for hardware to become idle.
This usually indicates problem with the hardware itself, or with the device driver programming the hardware incorrectly. Frequently, this is the result of a bad video card or a bad display driver.
Diagnostic approach
Use .thread with Parameter 1 to select the stuck thread, then inspect the stack with kb. Parameter 3 can identify the offending driver name, but the repeated stack location and the hardware operation being polled are stronger evidence than the module name alone.
If a kernel debugger intercepted the watchdog before the system issued the stop, the watchdog data can be inspected directly. On a 32-bit target use dd watchdog!g_WdBugCheckData L5; on a 64-bit target use dq watchdog!g_WdBugCheckData L5. Preserve the reported parameters and stuck-thread stack from the same timeout.
Determine whether the thread is spinning in driver code while waiting for hardware, in an ISR/DPC path, or after a device stopped responding. This distinction separates a driver loop from a hardware/firmware stall and avoids generic display-driver replacement when the stack points to another device class.
References
Looking for a different code? Search another status or error code.