*******************************************************************************
* *
* 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: ffffe70b367ad080, 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:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7721
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 9.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: V8.4
BIOS_DATE: 08/10/2016
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: A68HM-E33 V2 (MS-7721)
BASEBOARD_VERSION: 9.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffe70b367ad080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: 367ad080
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: e09
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 38
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: backgroundTaskHost.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: UHHHH_COLIF-PC
ANALYSIS_SESSION_TIME: 05-13-2017 11:48:04.0986
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff8060ed62dff to fffff8002d3ca6f0
STACK_COMMAND: .thread 0xffffe70b367ad080 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f06fd082cb2917db6ba2ffb622d7ed8279835b17
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
fffff806`0ed62dff cc int 3
FAULT_INSTR_CODE: c48b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 584a7780
IMAGE_VERSION: 10.0.14393.576
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2017-03-11T20:07:06.000Z
OSBUILD: 14393
OSSERVICEPACK: 693
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: 2016-12-21 01:50:57
BUILDDATESTAMP_STR: 161220-1747
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.693
ANALYSIS_SESSION_ELAPSED_TIME: 164d4
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Uhhhhhh_COLIF\Desktop\031117-19625-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 14393.693.amd64fre.rs1_release.161220-1747
Machine Name:
Kernel base = 0xfffff800`2d280000 PsLoadedModuleList = 0xfffff800`2d585060
Debug session time: Sat Mar 11 16:07:06.024 2017 (UTC - 4:00)
System Uptime: 0 days 0:04:58.721
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
.......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 100000EA, {ffffe70b367ad080, 0, 0, 0}
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
Probably caused by : dxgkrnl.sys ( dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* 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: ffffe70b367ad080, 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:
------------------
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10.0.14393.693 (rs1_release.161220-1747)
SYSTEM_MANUFACTURER: MSI
SYSTEM_PRODUCT_NAME: MS-7721
SYSTEM_SKU: To be filled by O.E.M.
SYSTEM_VERSION: 9.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: V8.4
BIOS_DATE: 08/10/2016
BASEBOARD_MANUFACTURER: MSI
BASEBOARD_PRODUCT: A68HM-E33 V2 (MS-7721)
BASEBOARD_VERSION: 9.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffe70b367ad080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: 367ad080
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 4
CPU_MHZ: e09
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 15
CPU_MODEL: 38
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: backgroundTaskHost.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: UHHHH_COLIF-PC
ANALYSIS_SESSION_TIME: 05-13-2017 11:46:33.0554
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff8060ed62dff to fffff8002d3ca6f0
STACK_TEXT:
ffffbb01`67e74ac8 fffff806`0ed62dff : 00000000`000000ea ffffe70b`367ad080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffbb01`67e74ad0 fffff806`0ed62ebe : ffffbb01`67e74ba8 fffff806`11c2f430 ffffbb01`67e74ba8 ffffbb01`67e74c90 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x3f
ffffbb01`67e74b40 fffff806`11bd36d0 : ffffe70b`3705a000 00000000`00000000 ffffbb01`67e74c90 fffff806`11c2f41c : dxgkrnl!TdrTimedOperationDelay+0xbe
ffffbb01`67e74b80 ffffe70b`3705a000 : 00000000`00000000 ffffbb01`67e74c90 fffff806`11c2f41c 00000000`00002710 : atikmdag+0x536d0
ffffbb01`67e74b88 00000000`00000000 : ffffbb01`67e74c90 fffff806`11c2f41c 00000000`00002710 00000000`00000028 : 0xffffe70b`3705a000
STACK_COMMAND: .thread 0xffffe70b367ad080 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 260988b723f057138fe45b239c381c934e8a7f90
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f06fd082cb2917db6ba2ffb622d7ed8279835b17
THREAD_SHA1_HASH_MOD: b9a6b0a1888ce93becee46671d601e0839dd0b94
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
fffff806`0ed62dff cc int 3
FAULT_INSTR_CODE: c48b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+3f
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 584a7780
IMAGE_VERSION: 10.0.14393.576
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2017-03-11T20:07:06.000Z
OSBUILD: 14393
OSSERVICEPACK: 693
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: 2016-12-21 01:50:57
BUILDDATESTAMP_STR: 161220-1747
BUILDLAB_STR: rs1_release
BUILDOSVER_STR: 10.0.14393.693
ANALYSIS_SESSION_ELAPSED_TIME: 16524
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner