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: ffffbf0f5f5e1400, 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 checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5530
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 66875
Key : Analysis.Memory.CommitPeak.Mb
Value: 91
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: ffffbf0f5f5e1400
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffbf0f5f5e1400
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffe604`2d6dee38 fffff802`81db289d : 00000000`000000ea ffffbf0f`5f5e1400 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffe604`2d6dee40 fffff802`81db297e : ffffe604`2d6def20 fffff802`81d8727b ffffe604`2d6def20 fffff802`86d61c90 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffe604`2d6deeb0 fffff802`86c2d100 : 0000000b`54757082 fffff802`86d61c90 00000000`00000000 ffffbf0f`57276000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffe604`2d6deef0 0000000b`54757082 : fffff802`86d61c90 00000000`00000000 ffffbf0f`57276000 00000000`00989680 : amdkmdag+0x6d100
ffffe604`2d6deef8 fffff802`86d61c90 : 00000000`00000000 ffffbf0f`57276000 00000000`00989680 00000000`00000001 : 0x0000000b`54757082
ffffe604`2d6def00 00000000`00000000 : ffffbf0f`57276000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a1c90
STACK_COMMAND: .thread 0xffffbf0f5f5e1400 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
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
---------
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: ffffd50f1cd6c080, 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
Key : Analysis.CPU.mSec
Value: 4437
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 48663
Key : Analysis.Memory.CommitPeak.Mb
Value: 83
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: ffffd50f1cd6c080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffd50f1cd6c080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: AUEPUF.exe
STACK_TEXT:
ffffd38b`9d875798 fffff807`5c90289d : 00000000`000000ea ffffd50f`1cd6c080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd38b`9d8757a0 fffff807`5c90297e : ffffd38b`9d875880 fffff807`5c8d727b ffffd38b`9d875880 fffff807`6286a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffd38b`9d875810 fffff807`62730c00 : 00000003`b222ea77 fffff807`6286a764 00000000`00000000 ffffd50f`0a612000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffd38b`9d875850 00000003`b222ea77 : fffff807`6286a764 00000000`00000000 ffffd50f`0a612000 00000000`00989680 : amdkmdag+0x70c00
ffffd38b`9d875858 fffff807`6286a764 : 00000000`00000000 ffffd50f`0a612000 00000000`00989680 00000000`00000001 : 0x00000003`b222ea77
ffffd38b`9d875860 00000000`00000000 : ffffd50f`0a612000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764
STACK_COMMAND: .thread 0xffffd50f1cd6c080 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
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
---------
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: ffff8d0c85e57080, 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
Key : Analysis.CPU.mSec
Value: 4108
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 54557
Key : Analysis.Memory.CommitPeak.Mb
Value: 92
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: ffff8d0c85e57080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffff8d0c85e57080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RadeonSoftware.exe
STACK_TEXT:
ffff8208`a0afa798 fffff807`52cd289d : 00000000`000000ea ffff8d0c`85e57080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff8208`a0afa7a0 fffff807`52cd297e : ffff8208`a0afa880 fffff807`52ca727b ffff8208`a0afa880 fffff807`599fa764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff8208`a0afa810 fffff807`598c0c00 : 00000000`a1e4a3aa fffff807`599fa764 00000000`00000000 ffff8d0c`74764000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff8208`a0afa850 00000000`a1e4a3aa : fffff807`599fa764 00000000`00000000 ffff8d0c`74764000 00000000`00989680 : amdkmdag+0x70c00
ffff8208`a0afa858 fffff807`599fa764 : 00000000`00000000 ffff8d0c`74764000 00000000`00989680 00000000`00000001 : 0xa1e4a3aa
ffff8208`a0afa860 00000000`00000000 : ffff8d0c`74764000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764
STACK_COMMAND: .thread 0xffff8d0c85e57080 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
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
---------
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: ffffc201c307c440, 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 checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 4765
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 98422
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
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: ffffc201c307c440
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffffc201c307c440
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff890a`b9cca278 fffff807`71dd289d : 00000000`000000ea ffffc201`c307c440 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff890a`b9cca280 fffff807`71dd297e : ffff890a`b9cca360 fffff807`71da727b ffff890a`b9cca360 fffff807`77d51c90 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff890a`b9cca2f0 fffff807`77c1d100 : 00000002`1999d7e5 fffff807`77d51c90 00000000`00000000 ffffc201`bcbdd000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff890a`b9cca330 00000002`1999d7e5 : fffff807`77d51c90 00000000`00000000 ffffc201`bcbdd000 00000000`00989680 : amdkmdag+0x6d100
ffff890a`b9cca338 fffff807`77d51c90 : 00000000`00000000 ffffc201`bcbdd000 00000000`00989680 00000000`00000001 : 0x00000002`1999d7e5
ffff890a`b9cca340 00000000`00000000 : ffffc201`bcbdd000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1a1c90
STACK_COMMAND: .thread 0xffffc201c307c440 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
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
---------
KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8077a51da68, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000578, Parameter 1 of the exception
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2999
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 12540
Key : Analysis.Memory.CommitPeak.Mb
Value: 86
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: 1e
BUGCHECK_P1: ffffffffc0000005
BUGCHECK_P2: fffff8077a51da68
BUGCHECK_P3: 0
BUGCHECK_P4: 578
READ_ADDRESS: fffff8077aafa390: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff8077aa0f330: Unable to get Flags value from nt!KdVersionBlock
fffff8077aa0f330: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
0000000000000578
EXCEPTION_PARAMETER2: 0000000000000578
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: Teams.exe
TRAP_FRAME: ffff800000000000 -- (.trap 0xffff800000000000)
Unable to read trap frame at ffff8000`00000000
STACK_TEXT:
ffffd287`cafa2538 fffff807`7a29128d : 00000000`0000001e ffffffff`c0000005 fffff807`7a51da68 00000000`00000000 : nt!KeBugCheckEx
ffffd287`cafa2540 fffff807`7a2078ac : 00000000`00001000 ffffd287`cafa2de0 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x16688d
ffffd287`cafa2c00 fffff807`7a203a43 : ffff940f`4c010100 00000000`00000001 ffff940f`5e101fc0 fffff807`7a0afea8 : nt!KiExceptionDispatch+0x12c
ffffd287`cafa2de0 fffff807`7a51da68 : 00000000`00000000 ffff9ef7`838121bd 00000000`00000000 ffff8080`061c5ae0 : nt!KiPageFault+0x443
ffffd287`cafa2f70 fffff807`7a12ad34 : ffffd287`cafa3a58 ffffd287`cafa3a58 ffffd287`cafa3120 0000009c`e44fe870 : nt!DbgkForwardException+0x98
ffffd287`cafa30f0 fffff807`7a2078ac : 00000000`00001000 ffffd287`cafa3b00 ffff8000`00000000 00000000`00000000 : nt!KiDispatchException+0x334
ffffd287`cafa3920 fffff807`7a203a43 : ffff940f`60f020c0 ffff940f`4eedca60 00000000`00000001 ffff940f`00000000 : nt!KiExceptionDispatch+0x12c
ffffd287`cafa3b00 00007ff7`424ea2a3 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x443
0000009c`e44fe870 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff7`424ea2a3
SYMBOL_NAME: nt!DbgkForwardException+98
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
IMAGE_VERSION: 10.0.19041.685
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 98
FAILURE_BUCKET_ID: 0x1E_c0000005_R_nt!DbgkForwardException
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {60f9b890-2436-bf13-76ab-c258341f402c}
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: ffff830c81f77080, 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
Key : Analysis.CPU.mSec
Value: 5421
Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-1IBQR0U
Key : Analysis.DebugData
Value: CreateObject
Key : Analysis.DebugModel
Value: CreateObject
Key : Analysis.Elapsed.mSec
Value: 63675
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
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: ffff830c81f77080
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FAULTING_THREAD: ffff830c81f77080
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: AUEPUF.exe
STACK_TEXT:
ffffd184`6c17f798 fffff802`5206289d : 00000000`000000ea ffff830c`81f77080 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd184`6c17f7a0 fffff802`5206297e : ffffd184`6c17f880 fffff802`5203727b ffffd184`6c17f880 fffff802`57c4a764 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffffd184`6c17f810 fffff802`57b10c00 : 0000007f`8d2870d6 fffff802`57c4a764 00000000`00000000 ffff830c`80a8c000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffffd184`6c17f850 0000007f`8d2870d6 : fffff802`57c4a764 00000000`00000000 ffff830c`80a8c000 00000000`00989680 : amdkmdag+0x70c00
ffffd184`6c17f858 fffff802`57c4a764 : 00000000`00000000 ffff830c`80a8c000 00000000`00989680 00000000`00000001 : 0x0000007f`8d2870d6
ffffd184`6c17f860 00000000`00000000 : ffff830c`80a8c000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x1aa764
STACK_COMMAND: .thread 0xffff830c81f77080 ; kb
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.685
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
---------
