VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80074d2010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff880157431c0, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
Unable to load image \SystemRoot\system32\DRIVERS\amdkmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for amdkmdag.sys
GetUlongPtrFromAddress: unable to read from fffff80003705300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1593
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 18969
Key : Analysis.Init.CPU.mSec
Value: 734
Key : Analysis.Init.Elapsed.mSec
Value: 37560
Key : Analysis.Memory.CommitPeak.Mb
Value: 67
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2021-07-12T17:46:00Z
Key : WER.OS.Version
Value: 7.1.7601.25682
FILE_IN_CAB: 121921-22651-01.dmp
BUGCHECK_CODE: 116
BUGCHECK_P1: fffffa80074d2010
BUGCHECK_P2: fffff880157431c0
BUGCHECK_P3: 0
BUGCHECK_P4: 2
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT fffffa80074d2010
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: dxgkrnl!_TDR_RECOVERY_CONTEXT ***
*** ***
*************************************************************************
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.
PROCESS_OBJECT: 0000000000000002
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff880`09f36888 fffff880`07166400 : 00000000`00000116 fffffa80`074d2010 fffff880`157431c0 00000000`00000000 : nt!KeBugCheckEx
fffff880`09f36890 fffff880`0716610a : fffff880`157431c0 fffffa80`074d2010 fffffa80`11bde010 fffffa80`11bd9010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`09f368d0 fffff880`1560ffef : fffffa80`074d2010 00000000`00000000 fffffa80`11bde010 fffffa80`11bd9010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`09f36900 fffff880`15639dc9 : 00000000`ffffffff 00000000`00005fca 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`09f369e0 fffff880`1563850f : 00000000`00000102 00000000`00000004 00000000`00005fca 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`09f36a10 fffff880`1560b306 : ffffffff`ff676980 fffffa80`11bd9010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`09f36ab0 fffff880`156380ce : 00000000`00000000 fffffa80`0692ed50 00000000`00000080 fffffa80`11bd9010 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`09f36bc0 fffff800`037a5dd8 : 00000000`fffffc32 fffff800`0364c180 00000000`00000001 fffffa80`11c12b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`09f36c00 fffff800`035012c6 : fffff800`0364c180 fffffa80`11c12b50 fffff800`0365c1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`09f36c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_NAME: amdkmdag+b21c0
MODULE_NAME: amdkmdag
IMAGE_NAME: amdkmdag.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_amdkmdag.sys
OS_VERSION: 7.1.7601.25682
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {1c94a7e8-453f-c7b9-1484-0a0454a0ee36}
Followup: MachineOwner
