Question Video TDR Failure: Computer black screen restarts, problem going on for 2 years

HamCity

Prominent
Jul 5, 2020
10
0
510
0
I've posted about this before but new things have happened since and I'm still as baffled as ever. My dad is a software engineer and he has no idea (works with linux but still).

Current spec:
  • i9 9900KF, Noctua NH U9S
  • Gigabyte RTX 2070
  • Gigabyte Z390 AORUS PRO
  • 32GB TridentZ 3600MHz DDR4
  • 1TB Samsung 970 EVO
  • Corsair RM750x
  • Windows 10
Previous post: https://forums.tomshardware.com/threads/computer-freezing-and-restarting-ive-done-everything.3625129/

tl;dr computer black screen crashes, tried various methods to fix (microcenter help, new hard drives, windows memory diagnostic/testing 1 stick at a time, etc.)

Since that post I have installed a new PSU and formatted my SSD and reinstalled windows. Overall PC is running much smoother but it still will black screen crash randomly (4 hours in, 1 hour in, after playing a game, browsing chrome, etc.). For a few seconds my audio still works (I can hear friends talking in discord) but it cuts out and my keyboard lights freeze. Since reinstalling windows it has happened twice, my computer rebooted after a few seconds and it gave me a dump file. Previously it would not reboot and stay stuck on a black screen, and I would never get a dump file. Before I did try and fix it by putting my old 760 in to see if it was the 2070 causing the crash and I'm pretty sure it still crashed, cannot test it because I no longer have another card. Any help is greatly appreciated.

Dump file:
***
  • *
  • Bugcheck Analysis *
  • *
***

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff908d9c4c0010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80793f6cfe8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2936

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5438

Key : Analysis.Init.CPU.mSec
Value: 327

Key : Analysis.Init.Elapsed.mSec
Value: 3186

Key : Analysis.Memory.CommitPeak.Mb
Value: 105

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


FILE_IN_CAB: 031822-7859-01.dmp

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff908d9c4c0010

BUGCHECK_P2: fffff80793f6cfe8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff908d9c4c0010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe20240e4f918 fffff8078f6f650e : 0000000000000116 ffff908d9c4c0010 fffff80793f6cfe8 ffffffffc000009a : nt!KeBugCheckEx
ffffe20240e4f920 fffff8078f6a6b04 : fffff80793f6cfe8 ffff908d9728a820 0000000000002000 ffff908d9728a8e0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffe20240e4f960 fffff8078f69f63c : ffff908d972a5000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffe20240e4f990 fffff8078f6f5c35 : 0000000000000100 ffff908d972a5a70 0000000097eb5ee0 fffff80777d24440 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffffe20240e4fa10 fffff8078f6f5da7 : fffff80777d24440 ffff908d9d1543a0 0000000000000000 0000000000000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe20240e4fa40 fffff807772b86d5 : ffff908d99f31040 fffff8078f6f5d80 ffff908d8c6b2cf0 0000000000000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffe20240e4fa70 fffff80777355a15 : ffff908d99f31040 0000000000000080 ffff908d8c6d60c0 0000000000000000 : nt!ExpWorkerThread+0x105
ffffe20240e4fb10 fffff807773fec78 : ffffb88037960180 ffff908d99f31040 fffff807773559c0 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffffe20240e4fb60 0000000000000000 : ffffe20240e50000 ffffe20240e49000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+e2cfe8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
---------
 
I've posted about this before but new things have happened since and I'm still as baffled as ever. My dad is a software engineer and he has no idea (works with linux but still).

Current spec:
  • i9 9900KF, Noctua NH U9S
  • Gigabyte RTX 2070
  • Gigabyte Z390 AORUS PRO
  • 32GB TridentZ 3600MHz DDR4
  • 1TB Samsung 970 EVO
  • Corsair RM750x
  • Windows 10
Previous post: https://forums.tomshardware.com/threads/computer-freezing-and-restarting-ive-done-everything.3625129/

tl;dr computer black screen crashes, tried various methods to fix (microcenter help, new hard drives, windows memory diagnostic/testing 1 stick at a time, etc.)

Since that post I have installed a new PSU and formatted my SSD and reinstalled windows. Overall PC is running much smoother but it still will black screen crash randomly (4 hours in, 1 hour in, after playing a game, browsing chrome, etc.). For a few seconds my audio still works (I can hear friends talking in discord) but it cuts out and my keyboard lights freeze. Since reinstalling windows it has happened twice, my computer rebooted after a few seconds and it gave me a dump file. Previously it would not reboot and stay stuck on a black screen, and I would never get a dump file. Before I did try and fix it by putting my old 760 in to see if it was the 2070 causing the crash and I'm pretty sure it still crashed, cannot test it because I no longer have another card. Any help is greatly appreciated.

Dump file:
***
  • *
  • Bugcheck Analysis *
  • *
***

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff908d9c4c0010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80793f6cfe8, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------

Unable to load image \SystemRoot\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3b12ac0f95b18b9d\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2936

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 5438

Key : Analysis.Init.CPU.mSec
Value: 327

Key : Analysis.Init.Elapsed.mSec
Value: 3186

Key : Analysis.Memory.CommitPeak.Mb
Value: 105

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


FILE_IN_CAB: 031822-7859-01.dmp

BUGCHECK_CODE: 116

BUGCHECK_P1: ffff908d9c4c0010

BUGCHECK_P2: fffff80793f6cfe8

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffff908d9c4c0010
Symbol dxgkrnl!_TDR_RECOVERY_CONTEXT not found.

PROCESS_OBJECT: 0000000000000004

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffe20240e4f918 fffff8078f6f650e : 0000000000000116 ffff908d9c4c0010 fffff80793f6cfe8 ffffffffc000009a : nt!KeBugCheckEx
ffffe20240e4f920 fffff8078f6a6b04 : fffff80793f6cfe8 ffff908d9728a820 0000000000002000 ffff908d9728a8e0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
ffffe20240e4f960 fffff8078f69f63c : ffff908d972a5000 0000000001000000 0000000000000004 0000000000000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
ffffe20240e4f990 fffff8078f6f5c35 : 0000000000000100 ffff908d972a5a70 0000000097eb5ee0 fffff80777d24440 : dxgkrnl!DXGADAPTER::Reset+0x4dc
ffffe20240e4fa10 fffff8078f6f5da7 : fffff80777d24440 ffff908d9d1543a0 0000000000000000 0000000000000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe20240e4fa40 fffff807772b86d5 : ffff908d99f31040 fffff8078f6f5d80 ffff908d8c6b2cf0 0000000000000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffffe20240e4fa70 fffff80777355a15 : ffff908d99f31040 0000000000000080 ffff908d8c6d60c0 0000000000000000 : nt!ExpWorkerThread+0x105
ffffe20240e4fb10 fffff807773fec78 : ffffb88037960180 ffff908d99f31040 fffff807773559c0 0000000000000000 : nt!PspSystemThreadStartup+0x55
ffffe20240e4fb60 0000000000000000 : ffffe20240e50000 ffffe20240e49000 0000000000000000 0000000000000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+e2cfe8

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}

Followup: MachineOwner
---------
Are there any applied OC's to the system?
 
VIDEO_TDR failure gets generated when the display driver for the GPU crashes, attempts to recover, and crashes during recovery. Typically, it's one of the BSODs thats indicative of some form of GPU failure, so I'd start looking there first. I'm assuming you've changed/updated GPU drivers since the problem first started, which would imply it's not a GPU driver problem.

Based on that, I'd say the most likely failure cause if a bum GPU; possibly a bad location in VRAM or something similar. Unfortunately, the only way to really verify this is to test with another GPU and confirm if the problem goes away. There's also the outside chance of a motherboard problem, but I'd be willing to bet the GPU is the culprit for this one.
 
Reactions: Satan-IR

HamCity

Prominent
Jul 5, 2020
10
0
510
0
VIDEO_TDR failure gets generated when the display driver for the GPU crashes, attempts to recover, and crashes during recovery. Typically, it's one of the BSODs thats indicative of some form of GPU failure, so I'd start looking there first. I'm assuming you've changed/updated GPU drivers since the problem first started, which would imply it's not a GPU driver problem.

Based on that, I'd say the most likely failure cause if a bum GPU; possibly a bad location in VRAM or something similar. Unfortunately, the only way to really verify this is to test with another GPU and confirm if the problem goes away. There's also the outside chance of a motherboard problem, but I'd be willing to bet the GPU is the culprit for this one.
I feel like I did try using a different GPU back when I had one handy but I guess its worth another shot at this point. Will update.
 

ASK THE COMMUNITY

TRENDING THREADS