*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)
The 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.
If the kernel debugger is connected and running when watchdog detects a
timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx()
and detailed message including BugCheck arguments will be printed to the
debugger. This way we can identify an offending thread, set breakpoints in it,
and hit go to return to the spinning code to debug it further. Because
KeBugCheckEx() is not called the .BugCheck directive will not return BugCheck
information in this case. The arguments are already printed out to the kernel
debugger. You can also retrieve them from a global variable via
"dd watchdog!g_WdBugCheckData l5" (use dq on NT64).
On MP machines it is possible to hit a timeout when the spinning thread is
interrupted by hardware interrupt and ISR or DPC routine is running at the time
of the BugCheck (this is because the timeout's work item can be delivered and
handled on the second CPU and the same time). If this is the case you will have
to look deeper at the offending thread's stack (e.g. using dds) to determine
spinning code which caused the timeout to occur.
Arguments:
Arg1: ffffe000fcd1c080, Pointer to a stuck thread object. Do .thread then kb on it to find
the hung location.
Arg2: 0000000000000000, Pointer to a DEFERRED_WATCHDOG object.
Arg3: 0000000000000000, Pointer to offending driver name.
Arg4: 0000000000000000, Number of times "intercepted" BugCheck 0xEA was hit (see notes).
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for atikmdag.sys
GetUlongPtrFromAddress: unable to read from fffff80134fd5308
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1452
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 18171
Key : Analysis.Init.CPU.mSec
Value: 781
Key : Analysis.Init.Elapsed.mSec
Value: 47343
Key : Analysis.Memory.CommitPeak.Mb
Value: 77
Key : Bugcheck.Code.DumpHeader
Value: 0x100000ea
Key : Bugcheck.Code.Register
Value: 0xea
Key : WER.OS.Branch
Value: winblue_ltsb_escrow
Key : WER.OS.Timestamp
Value: 2022-06-02T17:30:00Z
Key : WER.OS.Version
Value: 8.1.9600.20396
FILE_IN_CAB: 062522-6875-01.dmp
BUGCHECK_CODE: ea
BUGCHECK_P1: ffffe000fcd1c080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffe000fcd1c080
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: csgo.exe
STACK_TEXT:
ffffd000`418bad28 fffff800`90475a49 : 00000000`000000ea ffffe000`fcd1c080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`418bad30 fffff800`9046f0fe : ffffd000`418bae28 00000000`00000001 00000000`00000000 00000000`00000018 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x4d
ffffd000`418bada0 fffff800`90cf2043 : 00000000`00000000 ffffe000`f9b57000 00000000`00000000 00000000`00000000 : dxgkrnl!TdrTimedOperationDelay+0x7f42
ffffd000`418bae00 00000000`00000000 : ffffe000`f9b57000 00000000`00000000 00000000`00000000 00000000`01c9c380 : atikmdag+0x42043
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+4d
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 6.3.9600.19622
STACK_COMMAND: .process /r /p 0xffffe000fcd07600; .thread 0xffffe000fcd1c080 ; kb
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OS_VERSION: 8.1.9600.20396
BUILDLAB_STR: winblue_ltsb_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 8.1
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------