*******************************************************************************
* *
* 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: ffffa40a506ee080, 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 amdkmdag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 20249
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on EMB
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 33085
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : Analysis.System
Value: CreateObject
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
ADDITIONAL_XML: 1
OS_BUILD_LAYERS: 1
BUGCHECK_CODE: ea
BUGCHECK_P1: ffffa40a506ee080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffa40a506ee080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: opera.exe
STACK_TEXT:
ffffea87`63f7f438 fffff800`584a267d : 00000000`000000ea ffffa40a`506ee080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffea87`63f7f440 fffff800`584a275e : ffffea87`63f7f520 fffff800`58476abb ffffea87`63f7f520 fffff800`5e1125bc : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffea87`63f7f4b0 fffff800`5dfdd8e0 : 00000020`6ece8a5e fffff800`5e1125bc 00000000`00000000 ffffa40a`44c91000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffea87`63f7f4f0 00000020`6ece8a5e : fffff800`5e1125bc 00000000`00000000 ffffa40a`44c91000 00000000`00989680 : amdkmdag+0x6d8e0
ffffea87`63f7f4f8 fffff800`5e1125bc : 00000000`00000000 ffffa40a`44c91000 00000000`00989680 00000000`00000001 : 0x00000020`6ece8a5e
ffffea87`63f7f500 00000000`00000000 : ffffa40a`44c91000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a25bc
STACK_COMMAND: .thread 0xffffa40a506ee080 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.450
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
drive.google.com
