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: ffffd10aa10c00c0, 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
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: 18362.1.amd64fre.19h1_release.190318-1202
DUMP_TYPE: 2
BUGCHECK_P1: ffffd10aa10c00c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffd10aa10c00c0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 8
CPU_MHZ: 8f8
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 18
CPU_STEPPING: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: atieclxx.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-BKJR0DQ
ANALYSIS_SESSION_TIME: 03-16-2020 22:12:59.0795
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
LAST_CONTROL_TRANSFER: from fffff80238db1085 to fffff8022d3c2380
STACK_TEXT:
ffffa601`09822618 fffff802`38db1085 : 00000000`000000ea ffffd10a`a10c00c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffa601`09822620 fffff802`38db115e : ffffa601`09822700 fffff802`38d8bffb ffffa601`09822700 fffff802`425d3954 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffa601`09822690 fffff802`4253db00 : 00000018`cba755f7 fffff802`425d3954 00000000`00000000 ffffd10a`9569a000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffa601`098226d0 00000018`cba755f7 : fffff802`425d3954 00000000`00000000 ffffd10a`9569a000 00000000`00989680 : atikmdag+0x6db00
ffffa601`098226d8 fffff802`425d3954 : 00000000`00000000 ffffd10a`9569a000 00000000`00989680 00000000`00000001 : 0x00000018`cba755f7
ffffa601`098226e0 00000000`00000000 : ffffd10a`9569a000 00000000`00989680 00000000`00000001 00000000`00000028 : atikmdag+0x103954
STACK_COMMAND: .thread 0xffffd10aa10c00c0 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 72fdf9c2701b15ee3875c8d84432bb6f4f878992
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8733c7833060fb02ce8c6a0258e1674615927de1
THREAD_SHA1_HASH_MOD: 7711aec31f9092c0b1e7c4bf053e92961bf05370
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
fffff802`38db1085 cc int 3
FAULT_INSTR_CODE: cccccccc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.18362.719
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2020-03-13T17:28:31.000Z
OSBUILD: 18362
OSSERVICEPACK: 720
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: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 165b8
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: ffffe5859d5c8080, 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
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: 18362.1.amd64fre.19h1_release.190318-1202
SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.
SYSTEM_PRODUCT_NAME: TUF Gaming FX505DT_FX505DT
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: FX505DT.308
BIOS_DATE: 09/19/2019
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: FX505DT
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
BUGCHECK_P1: ffffe5859d5c8080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffe5859d5c8080
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 8
CPU_MHZ: 8f8
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 18
CPU_STEPPING: 1
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: atieclxx.exe
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-BKJR0DQ
ANALYSIS_SESSION_TIME: 03-16-2020 22:13:04.0666
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
LAST_CONTROL_TRANSFER: from fffff80322ad1085 to fffff803191c2380
STACK_TEXT:
ffffbb08`db4da588 fffff803`22ad1085 : 00000000`000000ea ffffe585`9d5c8080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffbb08`db4da590 fffff803`22ad115e : ffffbb08`db4da670 fffff803`22aabffb ffffbb08`db4da670 fffff803`2b363954 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffbb08`db4da600 fffff803`2b2cdb00 : 00000066`d61ea385 fffff803`2b363954 00000000`00000000 ffffe585`90e9f000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffbb08`db4da640 00000066`d61ea385 : fffff803`2b363954 00000000`00000000 ffffe585`90e9f000 00000000`00989680 : atikmdag+0x6db00
ffffbb08`db4da648 fffff803`2b363954 : 00000000`00000000 ffffe585`90e9f000 00000000`00989680 00000000`00000001 : 0x00000066`d61ea385
ffffbb08`db4da650 00000000`00000000 : ffffe585`90e9f000 00000000`00989680 00000000`00000001 00000000`00000028 : atikmdag+0x103954
STACK_COMMAND: .thread 0xffffe5859d5c8080 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 72fdf9c2701b15ee3875c8d84432bb6f4f878992
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8733c7833060fb02ce8c6a0258e1674615927de1
THREAD_SHA1_HASH_MOD: 7711aec31f9092c0b1e7c4bf053e92961bf05370
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
fffff803`22ad1085 cc int 3
FAULT_INSTR_CODE: cccccccc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.18362.719
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2020-03-14T09:30:48.000Z
OSBUILD: 18362
OSSERVICEPACK: 720
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: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 147ec
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffd2088679b060, Physical Device Object of the stack
Arg3: ffff960b91a298b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffd2088987a010, The blocked IRP
Debugging Details:
------------------
Implicit thread is now ffffd208`846eb040
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
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: 18362.1.amd64fre.19h1_release.190318-1202
SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.
SYSTEM_PRODUCT_NAME: TUF Gaming FX505DT_FX505DT
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: FX505DT.308
BIOS_DATE: 09/19/2019
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: FX505DT
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffffd2088679b060
BUGCHECK_P3: ffff960b91a298b0
BUGCHECK_P4: ffffd2088987a010
DRVPOWERSTATE_SUBCODE: 3
FAULTING_THREAD: ffffd208846eb040
CPU_COUNT: 8
CPU_MHZ: 8f8
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 18
CPU_STEPPING: 1
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-BKJR0DQ
ANALYSIS_SESSION_TIME: 03-16-2020 22:13:08.0422
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
LAST_CONTROL_TRANSFER: from fffff8071231508d to fffff807123c9106
STACK_TEXT:
ffff960b`91a1b4f0 fffff807`1231508d : fffff807`1083a180 00000000`fffffffe fffff807`ffffffff 00000000`00000001 : nt!KiSwapContext+0x76
ffff960b`91a1b630 fffff807`12313f14 : ffffd208`846eb040 ffffd208`00000000 ffffd208`00000000 00000000`00000000 : nt!KiSwapThread+0xbfd
ffff960b`91a1b6d0 fffff807`123136b5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x144
ffff960b`91a1b770 fffff807`1f652a6a : ffff960b`91a1b890 ffffd208`00000000 00000000`00000000 00000000`00000000 : nt!KeWaitForSingleObject+0x255
ffff960b`91a1b850 fffff807`1f6521f0 : ffff960b`91a1b800 00000000`00000008 ffffd208`8987a200 ffffd208`8987a010 : dxgkrnl!DpiFdoHandleDevicePower+0x22a
ffff960b`91a1b8f0 fffff807`1f6532c0 : ffffd208`8987a010 ffffd208`8961b180 ffffd208`8961b030 00000000`00000004 : dxgkrnl!DpiFdoDispatchPower+0x20
ffff960b`91a1b920 fffff807`219f00d3 : 00000000`00000001 ffffd208`927ec000 00000000`00000001 ffffd208`8987a010 : dxgkrnl!DpiDispatchPower+0xe0
ffff960b`91a1ba40 00000000`00000001 : ffffd208`927ec000 00000000`00000001 ffffd208`8987a010 ffff960b`91a1bb48 : nvlddmkm+0x1700d3
ffff960b`91a1ba48 ffffd208`927ec000 : 00000000`00000001 ffffd208`8987a010 ffff960b`91a1bb48 ffff960b`00000004 : 0x1
ffff960b`91a1ba50 00000000`00000001 : ffffd208`8987a010 ffff960b`91a1bb48 ffff960b`00000004 00000000`00000000 : 0xffffd208`927ec000
ffff960b`91a1ba58 ffffd208`8987a010 : ffff960b`91a1bb48 ffff960b`00000004 00000000`00000000 fffff807`12313601 : 0x1
ffff960b`91a1ba60 ffff960b`91a1bb48 : ffff960b`00000004 00000000`00000000 fffff807`12313601 ffffd208`89355000 : 0xffffd208`8987a010
ffff960b`91a1ba68 ffff960b`00000004 : 00000000`00000000 fffff807`12313601 ffffd208`89355000 ffffd208`00000000 : 0xffff960b`91a1bb48
ffff960b`91a1ba70 00000000`00000000 : fffff807`12313601 ffffd208`89355000 ffffd208`00000000 ffffd208`89384c00 : 0xffff960b`00000004
STACK_COMMAND: .thread 0xffffd208846eb040 ; kb
THREAD_SHA1_HASH_MOD_FUNC: f4e16074d73fc246f362417b4492425a06a85466
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: d177ca632534543504f23bc4254f6a367aa5e14b
THREAD_SHA1_HASH_MOD: decee8a647443db199bd66ee6f306d4fd815c914
FOLLOWUP_IP:
dxgkrnl!DpiFdoHandleDevicePower+22a
fffff807`1f652a6a 4863f0 movsxd rsi,eax
FAULT_INSTR_CODE: 85f06348
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: dxgkrnl!DpiFdoHandleDevicePower+22a
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.18362.719
BUCKET_ID_FUNC_OFFSET: 22a
FAILURE_BUCKET_ID: 0x9F_3_dxgkrnl!DpiFdoHandleDevicePower
BUCKET_ID: 0x9F_3_dxgkrnl!DpiFdoHandleDevicePower
PRIMARY_PROBLEM_CLASS: 0x9F_3_dxgkrnl!DpiFdoHandleDevicePower
TARGET_TIME: 2020-03-14T14:22:33.000Z
OSBUILD: 18362
OSSERVICEPACK: 720
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: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 2bbd
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_dxgkrnl!dpifdohandledevicepower
FAILURE_ID_HASH: {8058ca7c-9d12-86b8-15a2-3340127a0162}
Followup: MachineOwner
---------
DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffff9f0e4a74ae00, Physical Device Object of the stack
Arg3: fffffc08380458b0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff9f0e4adcc8a0, The blocked IRP
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for win32k.sys
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: 18362.1.amd64fre.19h1_release.190318-1202
SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.
SYSTEM_PRODUCT_NAME: TUF Gaming FX505DT_FX505DT
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: FX505DT.308
BIOS_DATE: 09/19/2019
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: FX505DT
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
BUGCHECK_P1: 3
BUGCHECK_P2: ffff9f0e4a74ae00
BUGCHECK_P3: fffffc08380458b0
BUGCHECK_P4: ffff9f0e4adcc8a0
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffff9f0e486be9f0
IMAGE_NAME: ACPI.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: ACPI
FAULTING_MODULE: fffff8000e4a0000 ACPI
CPU_COUNT: 8
CPU_MHZ: 8f8
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 18
CPU_STEPPING: 1
BLACKBOXACPI: 1 (!blackboxacpi)
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x9F
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_SESSION_HOST: DESKTOP-BKJR0DQ
ANALYSIS_SESSION_TIME: 03-16-2020 22:13:11.0864
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
STACK_TEXT:
fffffc08`38045878 fffff800`0a2ee7f7 : 00000000`0000009f 00000000`00000003 ffff9f0e`4a74ae00 fffffc08`380458b0 : nt!KeBugCheckEx
fffffc08`38045880 fffff800`0a2ee701 : ffff9f0e`4dec71e8 ffff9f0e`5aa071f0 ffffde81`49f23100 ffffde81`49f23180 : nt!PopIrpWatchdogBugcheck+0xef
fffffc08`380458f0 fffff800`0a0c1d59 : ffff9f0e`4dec7220 00000000`00000080 00000000`00000004 ffff9f0e`00000002 : nt!PopIrpWatchdog+0x31
fffffc08`38045940 fffff800`0a0c0ab9 : 00000000`00000012 00000000`00989680 00000000`0026803f 00000000`00000057 : nt!KiProcessExpiredTimerList+0x169
fffffc08`38045a30 fffff800`0a1c5ec4 : ffffffff`00000000 ffffde81`49f23180 00000000`00000000 ffffde81`49f34240 : nt!KiRetireDpcList+0x4e9
fffffc08`38045c60 00000000`00000000 : fffffc08`38046000 fffffc08`38040000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x84
THREAD_SHA1_HASH_MOD_FUNC: 418dcf5cc7a95525fe8ac8ffec7980c508fac304
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 380ee536789d4b77d82e9ab3a599c8d978e0118f
THREAD_SHA1_HASH_MOD: ee8fcf1fb60cb6e3e2f60ddbed2ec02b5748a693
FOLLOWUP_NAME: MachineOwner
IMAGE_VERSION: 10.0.18362.329
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_amdi2c_DEV_AMDI0010_IMAGE_ACPI.sys
BUCKET_ID: 0x9F_3_amdi2c_DEV_AMDI0010_IMAGE_ACPI.sys
PRIMARY_PROBLEM_CLASS: 0x9F_3_amdi2c_DEV_AMDI0010_IMAGE_ACPI.sys
TARGET_TIME: 2020-03-15T09:56:33.000Z
OSBUILD: 18362
OSSERVICEPACK: 720
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: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 254b
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x9f_3_amdi2c_dev_amdi0010_image_acpi.sys
FAILURE_ID_HASH: {4a47bf2d-33a2-c37b-edc8-078440157129}
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: ffff930be9f5b680, 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
*** WARNING: Unable to verify timestamp for win32k.sys
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: 18362.1.amd64fre.19h1_release.190318-1202
SYSTEM_MANUFACTURER: ASUSTeK COMPUTER INC.
SYSTEM_PRODUCT_NAME: TUF Gaming FX505DT_FX505DT
SYSTEM_VERSION: 1.0
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: FX505DT.308
BIOS_DATE: 09/19/2019
BASEBOARD_MANUFACTURER: ASUSTeK COMPUTER INC.
BASEBOARD_PRODUCT: FX505DT
BASEBOARD_VERSION: 1.0
DUMP_TYPE: 2
BUGCHECK_P1: ffff930be9f5b680
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffff930be9f5b680
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT
CPU_COUNT: 8
CPU_MHZ: 8f8
CPU_VENDOR: AuthenticAMD
CPU_FAMILY: 17
CPU_MODEL: 18
CPU_STEPPING: 1
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0xEA
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-BKJR0DQ
ANALYSIS_SESSION_TIME: 03-16-2020 22:13:15.0315
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
LAST_CONTROL_TRANSFER: from fffff8036b171085 to fffff8035e9c2380
STACK_TEXT:
ffffbd0c`10dfcec8 fffff803`6b171085 : 00000000`000000ea ffff930b`e9f5b680 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffbd0c`10dfced0 fffff803`6b17115e : ffffbd0c`10dfcfb0 fffff803`6b14bffb ffffbd0c`10dfcfb0 fffff803`74ed3954 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffbd0c`10dfcf40 fffff803`74e3db00 : 000000fd`fe223114 fffff803`74ed3954 00000000`00000000 ffff930b`defd5000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffbd0c`10dfcf80 000000fd`fe223114 : fffff803`74ed3954 00000000`00000000 ffff930b`defd5000 00000000`00989680 : atikmdag+0x6db00
ffffbd0c`10dfcf88 fffff803`74ed3954 : 00000000`00000000 ffff930b`defd5000 00000000`00989680 00000000`00000001 : 0x000000fd`fe223114
ffffbd0c`10dfcf90 00000000`00000000 : ffff930b`defd5000 00000000`00989680 00000000`00000001 00000000`00000028 : atikmdag+0x103954
STACK_COMMAND: .thread 0xffff930be9f5b680 ; kb
THREAD_SHA1_HASH_MOD_FUNC: 72fdf9c2701b15ee3875c8d84432bb6f4f878992
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 8733c7833060fb02ce8c6a0258e1674615927de1
THREAD_SHA1_HASH_MOD: 7711aec31f9092c0b1e7c4bf053e92961bf05370
FOLLOWUP_IP:
dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
fffff803`6b171085 cc int 3
FAULT_INSTR_CODE: cccccccc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 0
IMAGE_VERSION: 10.0.18362.719
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
PRIMARY_PROBLEM_CLASS: 0xEA_IMAGE_dxgkrnl.sys
TARGET_TIME: 2020-03-16T15:15:55.000Z
OSBUILD: 18362
OSSERVICEPACK: 720
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: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: 17a27
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xea_image_dxgkrnl.sys
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
