*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: ffffb60639644040, 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 this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1531
Key : Analysis.Elapsed.mSec
Value: 1876
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 93
Key : Analysis.Init.Elapsed.mSec
Value: 19869
Key : Analysis.Memory.CommitPeak.Mb
Value: 152
Key : Bugcheck.Code.LegacyAPI
Value: 0xea
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0xEA_IMAGE_dxgkrnl.sys
Key : Failure.Hash
Value: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
BUGCHECK_CODE: ea
BUGCHECK_P1: ffffb60639644040
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 052423-53109-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
FAULTING_THREAD: ffffb60639644040
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff500`065a34d8 fffff805`4784449d : 00000000`000000ea ffffb606`39644040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
fffff500`065a34e0 fffff805`4784457e : fffff500`065a35c0 fffff805`47816d5b fffff500`065a35c0 fffff500`065a3568 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
fffff500`065a3550 fffff805`59712210 : 00000000`ff320247 fffff805`596fcfe0 00000000`00000000 ffffb606`3dd57000 : dxgkrnl!TdrTimedOperationDelay+0xce
fffff500`065a3590 00000000`ff320247 : fffff805`596fcfe0 00000000`00000000 ffffb606`3dd57000 00000000`00989680 : amdkmdag+0x72210
fffff500`065a3598 fffff805`596fcfe0 : 00000000`00000000 ffffb606`3dd57000 00000000`00989680 00000000`00000001 : 0xff320247
fffff500`065a35a0 00000000`00000000 : ffffb606`3dd57000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x5cfe0
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.2913
STACK_COMMAND: .process /r /p 0xffffb60637c66100; .thread 0xffffb60639644040 ; kb
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff8031a456f96, The address that the exception occurred at
Arg3: ffff868f42e76308, Exception Record Address
Arg4: ffff868f42e75b40, Context Record Address
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1453
Key : Analysis.Elapsed.mSec
Value: 2113
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 202
Key : Analysis.Init.Elapsed.mSec
Value: 11669
Key : Analysis.Memory.CommitPeak.Mb
Value: 150
Key : Bugcheck.Code.LegacyAPI
Value: 0x1000007e
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x7E_C000001D_BAD_IP_vgk!unknown_function
Key : Failure.Hash
Value: {7a68f8b8-64ef-2b8a-1e2f-905aaaf8acd3}
BUGCHECK_CODE: 7e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff8031a456f96
BUGCHECK_P3: ffff868f42e76308
BUGCHECK_P4: ffff868f42e75b40
FILE_IN_CAB: 052323-46828-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
EXCEPTION_RECORD: ffff868f42e76308 -- (.exr 0xffff868f42e76308)
ExceptionAddress: fffff8031a456f96 (vgk+0x0000000000126f96)
ExceptionCode: c000001d (Illegal instruction)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: ffff868f42e75b40 -- (.cxr 0xffff868f42e75b40)
rax=000000ee49055a3b rbx=fffff8031a3b100a rcx=0000000000015ea0
rdx=000000ee00000000 rsi=fffff8031a3b3000 rdi=0000000000000000
rip=fffff8031a456f96 rsp=ffff868f42e76540 rbp=ffff868f42e76640
r8=00000000c000009c r9=0000000000000002 r10=000000000000001e
r11=00000000c0000189 r12=0000000000000008 r13=0000000000000080
r14=0000000000000001 r15=fffff8031a3b1000
iopl=0 nv up ei pl nz na pe nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010202
vgk+0x126f96:
fffff803`1a456f96 0f01f9 rdtscp
Resetting default scope
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
ERROR_CODE: (NTSTATUS) 0xc000001d - { ZEL DURUM} Ge ersiz Y nerge Ge ersiz bir y nerge y r t lmeye al ld .
EXCEPTION_CODE_STR: c000001d
EXCEPTION_STR: 0xc000001d
FAILED_INSTRUCTION_ADDRESS:
vgk+126f96
fffff803`1a456f96 0f01f9 rdtscp
STACK_TEXT:
ffff868f`42e76540 00000000`fed40000 : 00000000`00000000 00000000`000000c8 ffffffff`ffffffff 00000000`00000000 : vgk+0x126f96
ffff868f`42e76548 00000000`00000000 : 00000000`000000c8 ffffffff`ffffffff 00000000`00000000 00000000`00000000 : 0xfed40000
SYMBOL_NAME: vgk+126f96
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .cxr 0xffff868f42e75b40 ; kb
BUCKET_ID_FUNC_OFFSET: 126f96
FAILURE_BUCKET_ID: 0x7E_C000001D_BAD_IP_vgk!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {7a68f8b8-64ef-2b8a-1e2f-905aaaf8acd3}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffc20b7f54d010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80626939630, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc0000001, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000003, Optional internal context dependent data.
Debugging Details:
------------------
Unable to load image amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1546
Key : Analysis.Elapsed.mSec
Value: 3730
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 171
Key : Analysis.Init.Elapsed.mSec
Value: 11391
Key : Analysis.Memory.CommitPeak.Mb
Value: 152
Key : Bugcheck.Code.LegacyAPI
Value: 0x116
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0x116_IMAGE_amdkmdag.sys
Key : Failure.Hash
Value: {1c94a7e8-453f-c7b9-1484-0a0454a0ee36}
BUGCHECK_CODE: 116
BUGCHECK_P1: ffffc20b7f54d010
BUGCHECK_P2: fffff80626939630
BUGCHECK_P3: ffffffffc0000001
BUGCHECK_P4: 3
FILE_IN_CAB: 052223-35984-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffc20b7f54d010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000000003
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffffd605`2fc3eaf8 fffff806`10b265be : 00000000`00000116 ffffc20b`7f54d010 fffff806`26939630 ffffffff`c0000001 : nt!KeBugCheckEx
ffffd605`2fc3eb00 fffff806`10ace67b : fffff806`26939630 ffffc20b`7e4e1000 ffffc20b`7e4e10f0 00000000`00000000 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffd605`2fc3eb40 fffff806`10acf455 : ffffc20b`00000101 00000000`00002000 ffffc20b`7e4e1000 00000000`01000000 : dxgkrnl!DXGADAPTER::PrepareToReset+0x1a3
ffffd605`2fc3eb90 fffff806`10b25ce5 : 00000000`00000100 ffffc20b`7e4e1a70 00000000`7f491040 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x295
ffffd605`2fc3ec10 fffff806`10b25e57 : fffff806`0cd25440 00000000`00000000 00000000`00000000 00000000`00000400 : dxgkrnl!TdrResetFromTimeout+0x15
ffffd605`2fc3ec40 fffff806`0c28e5c5 : ffffc20b`7819b080 fffff806`10b25e30 ffffc20b`780b5a60 ffffc20b`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffd605`2fc3ec70 fffff806`0c3265f5 : ffffc20b`7819b080 00000000`00000080 ffffc20b`780a2080 854dd233`398b4c20 : nt!ExpWorkerThread+0x105
ffffd605`2fc3ed10 fffff806`0c4048d8 : fffff806`08522180 ffffc20b`7819b080 fffff806`0c3265a0 ba83e98b`4c4072f8 : nt!PspSystemThreadStartup+0x55
ffffd605`2fc3ed60 00000000`00000000 : ffffd605`2fc3f000 ffffd605`2fc39000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28
SYMBOL_NAME: amdkmdag+b9630
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_amdkmdag.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {1c94a7e8-453f-c7b9-1484-0a0454a0ee36}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: ffffad8bce51f040, 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 this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1468
Key : Analysis.Elapsed.mSec
Value: 1543
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 218
Key : Analysis.Init.Elapsed.mSec
Value: 11548
Key : Analysis.Memory.CommitPeak.Mb
Value: 152
Key : Bugcheck.Code.LegacyAPI
Value: 0xea
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0xEA_IMAGE_dxgkrnl.sys
Key : Failure.Hash
Value: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
BUGCHECK_CODE: ea
BUGCHECK_P1: ffffad8bce51f040
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 052223-34812-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
FAULTING_THREAD: ffffad8bce51f040
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff870c`a4e7b4d8 fffff805`1da6449d : 00000000`000000ea ffffad8b`ce51f040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff870c`a4e7b4e0 fffff805`1da6457e : ffff870c`a4e7b5c0 fffff805`1da36d5b ffff870c`a4e7b5c0 ffff870c`a4e7b568 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff870c`a4e7b550 fffff805`2e592210 : 00000007`f6b10e78 fffff805`2e57cfe0 00000000`00000000 ffffad8b`c6880000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff870c`a4e7b590 00000007`f6b10e78 : fffff805`2e57cfe0 00000000`00000000 ffffad8b`c6880000 00000000`00989680 : amdkmdag+0x72210
ffff870c`a4e7b598 fffff805`2e57cfe0 : 00000000`00000000 ffffad8b`c6880000 00000000`00989680 00000000`00000001 : 0x00000007`f6b10e78
ffff870c`a4e7b5a0 00000000`00000000 : ffffad8b`c6880000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x5cfe0
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.2913
STACK_COMMAND: .process /r /p 0xffffad8bc4aa2080; .thread 0xffffad8bce51f040 ; kb
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
THREAD_STUCK_IN_DEVICE_DRIVER (ea)
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 (OS builds <= 3790) 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: ffffb6855f02c040, 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 this error occurred. If a debugger is attached,
this error is not always fatal -- see DESCRIPTION below. On the
blue screen, this will always equal 1.
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1609
Key : Analysis.Elapsed.mSec
Value: 1673
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 156
Key : Analysis.Init.Elapsed.mSec
Value: 12948
Key : Analysis.Memory.CommitPeak.Mb
Value: 152
Key : Bugcheck.Code.LegacyAPI
Value: 0xea
Key : Dump.Attributes.AsUlong
Value: 8
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Failure.Bucket
Value: 0xEA_IMAGE_dxgkrnl.sys
Key : Failure.Hash
Value: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
BUGCHECK_CODE: ea
BUGCHECK_P1: ffffb6855f02c040
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
FILE_IN_CAB: 052223-35781-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
FAULTING_THREAD: ffffb6855f02c040
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
ffff9e80`db3154d8 fffff801`0ba5449d : 00000000`000000ea ffffb685`5f02c040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff9e80`db3154e0 fffff801`0ba5457e : ffff9e80`db3155c0 fffff801`0ba26d5b ffff9e80`db3155c0 ffff9e80`db315568 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff9e80`db315550 fffff801`218e2210 : 00000007`277af99b fffff801`218ccfe0 00000000`00000000 ffffb685`5be0e000 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff9e80`db315590 00000007`277af99b : fffff801`218ccfe0 00000000`00000000 ffffb685`5be0e000 00000000`00989680 : amdkmdag+0x72210
ffff9e80`db315598 fffff801`218ccfe0 : 00000000`00000000 ffffb685`5be0e000 00000000`00989680 00000000`00000001 : 0x00000007`277af99b
ffff9e80`db3155a0 00000000`00000000 : ffffb685`5be0e000 00000000`00989680 00000000`00000001 00000000`00000028 : amdkmdag+0x5cfe0
SYMBOL_NAME: dxgkrnl!TdrTimedOperationBugcheckOnTimeout+45
MODULE_NAME: dxgkrnl
IMAGE_NAME: dxgkrnl.sys
IMAGE_VERSION: 10.0.19041.2913
STACK_COMMAND: .process /r /p 0xffffb68559a81040; .thread 0xffffb6855f02c040 ; kb
FAILURE_BUCKET_ID: 0xEA_IMAGE_dxgkrnl.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {ea458ad2-d5ab-aa6c-7a11-54653c70dfb8}
Followup: MachineOwner
---------
