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: ffff92097da756c0, 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:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd
SYSTEM_PRODUCT_NAME: MS-7B86
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.72
BIOS_DATE: 03/04/2019
BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd
BASEBOARD_PRODUCT: B450 GAMING PLUS (MS-7B86)
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
BUGCHECK_P1: ffff92097da756c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffff92097da756c0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: dac
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 1
CPU_STEPPING: 1
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-NG9H4F5
ANALYSIS_SESSION_TIME: 04-10-2019 01:02:15.0942
ANALYSIS_VERSION: 10.0.18317.1001 amd64fre
LAST_CONTROL_TRANSFER: from fffff8013579a710 to fffff804531bff30
STACK_TEXT:
ffff868b`1a7a7d78 fffff801`3579a710 : 00000000`000000ea ffff9209`7da756c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff868b`1a7a7d80 fffff801`3579a7ea : ffff868b`1a7a7e58 fffff801`3a298890 ffff868b`1a7a7e58 ffff868b`1a7a7f40 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x40
ffff868b`1a7a7df0 fffff801`3a236970 : ffff9209`7af9e000 00000000`00000000 ffff868b`1a7a7f40 fffff801`3a29887c : dxgkrnl!TdrTimedOperationDelay+0xca
ffff868b`1a7a7e30 ffff9209`7af9e000 : 00000000`00000000 ffff868b`1a7a7f40 fffff801`3a29887c 00000000`00002710 : atikmdag+0x56970
ffff868b`1a7a7e38 00000000`00000000 : ffff868b`1a7a7f40 fffff801`3a29887c 00000000`00002710 00000000`00000028 : 0xffff9209`7af9e000
STACK_COMMAND: .thread 0xffff92097da756c0 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1b6e0a437c60d2c16d9ebaaae9cc861a6e13529c
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40
fffff801`3579a710 0f1f440000 nop dword ptr [rax+rax]
FAULT_INSTR_CODE: 441f0f
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 69efb842
IMAGE_VERSION: 10.0.17763.10000
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2019-04-02T20:59:46.000Z
OSBUILD: 17763
OSSERVICEPACK: 1
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 1986-10-28 08:40:20
BUILDDATESTAMP_STR: 180914-1434
BUILDLAB_STR: rs5_release
BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
ANALYSIS_SESSION_ELAPSED_TIME: 16fda
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
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: ffffa2821fa76640, 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:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd
SYSTEM_PRODUCT_NAME: MS-7B86
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.72
BIOS_DATE: 03/04/2019
BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd
BASEBOARD_PRODUCT: B450 GAMING PLUS (MS-7B86)
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffa2821fa76640
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffa2821fa76640
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: dac
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 1
CPU_STEPPING: 1
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXPNP: 1 (!blackboxpnp)
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-NG9H4F5
ANALYSIS_SESSION_TIME: 04-10-2019 01:02:19.0200
ANALYSIS_VERSION: 10.0.18317.1001 amd64fre
LAST_CONTROL_TRANSFER: from fffff8067a13a710 to fffff80678bb7f30
STACK_TEXT:
ffff8b8c`a4dcb148 fffff806`7a13a710 : 00000000`000000ea ffffa282`1fa76640 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8b8c`a4dcb150 fffff806`7a13a7ea : ffff8b8c`a4dcb228 fffff806`86fd8890 ffff8b8c`a4dcb228 ffff8b8c`a4dcb310 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x40
ffff8b8c`a4dcb1c0 fffff806`86f76970 : ffffa282`1f1e2000 00000000`00000000 ffff8b8c`a4dcb310 fffff806`86fd887c : dxgkrnl!TdrTimedOperationDelay+0xca
ffff8b8c`a4dcb200 ffffa282`1f1e2000 : 00000000`00000000 ffff8b8c`a4dcb310 fffff806`86fd887c 00000000`00002710 : atikmdag+0x56970
ffff8b8c`a4dcb208 00000000`00000000 : ffff8b8c`a4dcb310 fffff806`86fd887c 00000000`00002710 00000000`00000028 : 0xffffa282`1f1e2000
STACK_COMMAND: .thread 0xffffa2821fa76640 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1b6e0a437c60d2c16d9ebaaae9cc861a6e13529c
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40
fffff806`7a13a710 0f1f440000 nop dword ptr [rax+rax]
FAULT_INSTR_CODE: 441f0f
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 69efb842
IMAGE_VERSION: 10.0.17763.10000
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2019-04-04T16:33:59.000Z
OSBUILD: 17763
OSSERVICEPACK: 1
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 272
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 1986-10-28 08:40:20
BUILDDATESTAMP_STR: 180914-1434
BUILDLAB_STR: rs5_release
BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
ANALYSIS_SESSION_ELAPSED_TIME: 11fec
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
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: ffffa401f9281640, 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:
------------------
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434
SYSTEM_MANUFACTURER: Micro-Star International Co., Ltd
SYSTEM_PRODUCT_NAME: MS-7B86
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.72
BIOS_DATE: 03/04/2019
BASEBOARD_MANUFACTURER: Micro-Star International Co., Ltd
BASEBOARD_PRODUCT: B450 GAMING PLUS (MS-7B86)
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffa401f9281640
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffa401f9281640
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: dac
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 1
CPU_STEPPING: 1
BLACKBOXBSD: 1 (!blackboxbsd)
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-NG9H4F5
ANALYSIS_SESSION_TIME: 04-10-2019 00:50:46.0538
ANALYSIS_VERSION: 10.0.18317.1001 amd64fre
LAST_CONTROL_TRANSFER: from fffff80582cfa7e0 to fffff805784565e0
STACK_TEXT:
ffff9982`13a06148 fffff805`82cfa7e0 : 00000000`000000ea ffffa401`f9281640 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9982`13a06150 fffff805`82cfa8ba : ffff9982`13a06228 fffff805`873b8890 ffff9982`13a06228 ffff9982`13a06310 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x40
ffff9982`13a061c0 fffff805`87356970 : ffffa401`f84aa000 00000000`00000000 ffff9982`13a06310 fffff805`873b887c : dxgkrnl!TdrTimedOperationDelay+0xca
ffff9982`13a06200 ffffa401`f84aa000 : 00000000`00000000 ffff9982`13a06310 fffff805`873b887c 00000000`00002710 : atikmdag+0x56970
ffff9982`13a06208 00000000`00000000 : ffff9982`13a06310 fffff805`873b887c 00000000`00002710 00000000`00000028 : 0xffffa401`f84aa000
STACK_COMMAND: .thread 0xffffa401f9281640 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 1b6e0a437c60d2c16d9ebaaae9cc861a6e13529c
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40
fffff805`82cfa7e0 0f1f440000 nop dword ptr [rax+rax]
FAULT_INSTR_CODE: 441f0f
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+40
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.17763.379
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2019-03-27T20:13:52.000Z
OSBUILD: 17763
OSSERVICEPACK: 379
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
BUILDDATESTAMP_STR: 180914-1434
BUILDLAB_STR: rs5_release
BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434
ANALYSIS_SESSION_ELAPSED_TIME: 164b6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
