HREAD_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: ffffe18e981210c0, 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:
------------------
***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
DUMP_TYPE: 2
BUGCHECK_P1: ffffe18e981210c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffe18e981210c0
DEFAULT_BUCKET_ID: CORRUPT_MODULELIST_0xEA
CPU_COUNT: 4
CPU_MHZ: e10
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 18
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-GULEPCP
ANALYSIS_SESSION_TIME: 05-31-2020 14:34:42.0097
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
LAST_CONTROL_TRANSFER: from fffff8047db71005 to fffff8046f7c2390
STACK_TEXT:
ffffa48f`6117f528 fffff804`7db71005 : 00000000`000000ea ffffe18e`981210c0 00000000`00000000 00000000`00000000 : 0xfffff804`6f7c2390
ffffa48f`6117f530 00000000`000000ea : ffffe18e`981210c0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xfffff804`7db71005
ffffa48f`6117f538 ffffe18e`981210c0 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff804`7db70ea8 : 0xea
ffffa48f`6117f540 00000000`00000000 : 00000000`00000000 00000000`00000000 fffff804`7db70ea8 00000000`00000028 : 0xffffe18e`981210c0
SYMBOL_NAME: ANALYSIS_INCONCLUSIVE
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: Unknown_Module
IMAGE_NAME: Unknown_Image
DEBUG_FLR_IMAGE_TIMESTAMP: 0
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID: CORRUPT_MODULELIST_0xEA
PRIMARY_PROBLEM_CLASS: CORRUPT_MODULELIST_0xEA
FAILURE_BUCKET_ID: CORRUPT_MODULELIST_0xEA
TARGET_TIME: 2020-05-19T09:33:20.000Z
OSBUILD: 18362
OSSERVICEPACK: 0
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: unknown_date
ANALYSIS_SESSION_ELAPSED_TIME: 54
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:corrupt_modulelist_0xea
FAILURE_ID_HASH: {c68cbf3f-8d4e-3460-b21b-b5bac9deffb4}
Followup: MachineOwner
