VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa801b1974e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3e6b60, 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\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
GetUlongPtrFromAddress: unable to read from fffff80002f04300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 2343
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 10744
Key : Analysis.Init.CPU.mSec
Value: 905
Key : Analysis.Init.Elapsed.mSec
Value: 14834
Key : Analysis.Memory.CommitPeak.Mb
Value: 64
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2021-10-04T19:08:00Z
Key : WER.OS.Version
Value: 7.1.7601.25740
FILE_IN_CAB: 122621-10561-01.dmp
BUGCHECK_CODE: 116
BUGCHECK_P1: fffffa801b1974e0
BUGCHECK_P2: fffff8800f3e6b60
BUGCHECK_P3: 0
BUGCHECK_P4: 2
VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT fffffa801b1974e0
*************************************************************************
*** ***
*** ***
*** 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`03e5f4f8 fffff880`04cbe400 : 00000000`00000116 fffffa80`1b1974e0 fffff880`0f3e6b60 00000000`00000000 : nt!KeBugCheckEx
fffff880`03e5f500 fffff880`04cbe10a : fffff880`0f3e6b60 fffffa80`1b1974e0 fffffa80`1bbdc400 fffffa80`1bbad010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`03e5f540 fffff880`04d65fef : fffffa80`1b1974e0 00000000`00000000 fffffa80`1bbdc400 fffffa80`1bbad010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`03e5f570 fffff880`04d93fae : fffffa80`ffffffff 00000000`00017cf7 fffff880`03e5f6c0 00000000`00000006 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`03e5f650 fffff880`04d79d91 : fffffa80`1bc0f000 ffffffff`feced300 00000000`00000006 fffffa80`1bc0f000 : dxgmms1!VidSchWaitForCompletionEvent+0x196
fffff880`03e5f690 fffff880`04d7722c : 00000000`00000001 fffff8a0`09b0d010 fffffa80`1bc0f000 00000000`00000000 : dxgmms1!VIDMM_GLOBAL::xWaitForAllEngines+0x1e9
fffff880`03e5f790 fffff880`04d749d1 : 00000000`00000000 fffffa80`1701d000 00000000`00000006 fffff8a0`09b0d010 : dxgmms1!VIDMM_GLOBAL::ReferenceAllocationForSubmission+0xfc
fffff880`03e5f7d0 fffff880`04d8e8b1 : 00000000`00000000 fffff8a0`0274a990 fffffa80`00000000 fffffa80`1b8992f0 : dxgmms1!VIDMM_GLOBAL::PrepareDmaBuffer+0xd7d
fffff880`03e5f9a0 fffff880`04d8e5ec : fffff880`04d8e014 00000000`00000000 fffffa80`00000000 fffffa80`00000000 : dxgmms1!VidSchiSubmitRenderCommand+0x241
fffff880`03e5fb90 fffff880`04d8e0ea : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`1b2636f8 : dxgmms1!VidSchiSubmitQueueCommand+0x50
fffff880`03e5fbc0 fffff800`02fa3e30 : 00000000`00fba264 fffff800`02e4b180 00000000`00000001 fffffa80`1bbde060 : dxgmms1!VidSchiWorkerThread+0xd6
fffff880`03e5fc00 fffff800`02d001c6 : fffff800`02e4b180 fffffa80`1bbde060 fffff800`02e5b1c0 00000000`00000000 : nt!PspSystemThreadStartup+0x194
fffff880`03e5fc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
SYMBOL_NAME: nvlddmkm+164b60
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
OS_VERSION: 7.1.7601.25740
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}
Followup: MachineOwner
