To look deeper at the offending thread's stack (e.g. Handled on the second CPU and the same time). Of the bugcheck (this is because the timeout's work item can be delivered and Interrupted by hardware interrupt and ISR or DPC routine is running at the time On MP machines it is possible to hit a timeout when the spinning thread is "dd watchdog!g_WdBugCheckData l5" (use dq on NT64). You can also retrieve them from a global variable via The arguments are already printed out to the kernelĭebugger. bugcheck directive will not return bugcheck This way we can identify an offending thread, set breakpoints in it,Īnd hit go to return to the spinning code to debug it further. Timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()Īnd detailed message including bugcheck arguments will be printed to theĭebugger. If the kernel debugger is connected and running when watchdog detects a
THREAD STUCK IN DEVICE DRIVER AMD WINDOWS 10 DRIVER
Itself or with the device driver programming the hardware incorrectly. This usually indicates problem with the hardware The device driver is spinning in an infinite loop, most likely waiting for THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea) Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+24 ) *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys *** WARNING: Unable to verify timestamp for atikmdag.sys Use !analyze -v to get detailed debugging information.īugCheck 100000EA, Here is the analysis result for reference: It is recommended to download the latest Windows 10 compatible driver for the device from the machine device manufacturer website.
Please try to reinstall the graphic adapter driver from the device manager. The issue is related to the dxgkrnl.sys(Microsoft DirectX system driver file).