........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80081194e0, fffff88007599010, 0, 2}
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+13b010 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80081194e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88007599010, 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:
------------------
FAULTING_IP:
nvlddmkm+13b010
fffff880`07599010 4055 push rbp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`05fe99c8 fffff880`07076054 : 00000000`00000116 fffffa80`081194e0 fffff880`07599010 00000000`00000000 : nt!KeBugCheckEx
fffff880`05fe99d0 fffff880`07075d5e : fffff880`07599010 fffffa80`081194e0 fffffa80`08a70d50 fffffa80`08d6e410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05fe9a10 fffff880`0711cf13 : fffffa80`081194e0 00000000`00000000 fffffa80`08a70d50 fffffa80`08d6e410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`05fe9a40 fffff880`07146cf1 : 00000000`ffffffff 00000000`0001b405 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`05fe9b20 fffff880`07145437 : 00000000`00000102 00000000`00000006 00000000`0001b405 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`05fe9b50 fffff880`071182d2 : ffffffff`ff676980 fffffa80`08d6e410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`05fe9bf0 fffff880`07144ff6 : 00000000`00000000 fffffa80`06baa850 00000000`00000080 fffffa80`08d6e410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`05fe9d00 fffff800`03564ede : 00000000`fffffc32 fffffa80`08a72b50 fffffa80`0670a040 fffffa80`08a72b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`05fe9d40 fffff800`032b7906 : fffff800`03441e80 fffffa80`08a72b50 fffff800`0344fcc0 00000004`dcaff000 : nt!PspSystemThreadStartup+0x5a
fffff880`05fe9d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+13b010
fffff880`07599010 4055 push rbp
SYMBOL_NAME: nvlddmkm+13b010
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 518fe8f9
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------