BSOD - video_tdr_failure nvlddmkm.sys error (keeps recurring)

BestPwnz said:

As the title notes, I keep on getting a BSOD followed by the nvlddmkm.sys error. I tried basically every fix that I could find on Google but I could not find anything that worked. Here is my link to the V2 BSOD Log Collector DAB-(2022-06-23_17-54-32).zip - Google Drive

If you haven't tried this yet... I would try it.

DDU Instructions - Nvidia
1. Get this program, here: Display Driver Uninstaller (DDU) | Wagnardsoft ...get the latest version, and save it to your desktop.
2. Get the Standard/Game Ready vid card driver here, use the Manual Search: Advanced Driver Search | NVIDIA ...save this to your desktop.
Unhook the internet completely.
3. Reboot into Safe Mode and run DDU (Display Driver Uninstaller) choose the "Highly Recommend Option", and just do what it tells you.
4. After it's done, reboot to normal mode, then just double click the Nvidia driver to install.
[See pics below]. If it want's to reboot, let it.
Rehook the internet.

How long have you had the PC? Is the video card an upgrade and if so when was it installed?

When did this problem start happening?

Looking at the most recent dump it's definitely a video problem:

Code:

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffff9405b2fe9010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8015bbdafb0, 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 nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys

Code:

FAULTING_IP: 
nvlddmkm+eaafb0
fffff801`5bbdafb0 488b0549e4b8ff  mov     rax,qword ptr [nvlddmkm+0xa39400 (fffff801`5b769400)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

Code:

STACK_TEXT:  
fffff004`90f0f918 fffff801`556654ee : 00000000`00000116 ffff9405`b2fe9010 fffff801`5bbdafb0 ffffffff`c000009a : nt!KeBugCheckEx
fffff004`90f0f920 fffff801`55615b04 : fffff801`5bbdafb0 ffff9405`a6bf9010 00000000`00002000 ffff9405`a6bf90d0 : dxgkrnl!TdrBugcheckOnTimeout+0xfe
fffff004`90f0f960 fffff801`5560e63c : ffff9405`a6bf6000 00000000`01000000 00000000`00000004 00000000`00000004 : dxgkrnl!ADAPTER_RENDER::Reset+0x174
fffff004`90f0f990 fffff801`55664c15 : 00000000`00000100 ffff9405`a6bf6a70 00000000`a5a2f540 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x4dc
fffff004`90f0fa10 fffff801`55664d87 : fffff801`3d525440 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
fffff004`90f0fa40 fffff801`3cabfae5 : ffff9405`a5c3f100 fffff801`55664d60 ffff9405`9c89ec40 ffff9405`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
fffff004`90f0fa70 fffff801`3caeea75 : ffff9405`a5c3f100 00000000`00000080 ffff9405`9c8bb040 000fa4ef`bd9bbfff : nt!ExpWorkerThread+0x105
fffff004`90f0fb10 fffff801`3cbff428 : ffff8200`d7ae3180 ffff9405`a5c3f100 fffff801`3caeea20 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffff004`90f0fb60 00000000`00000000 : fffff004`90f10000 fffff004`90f09000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

FOLLOWUP_IP: 
nvlddmkm+eaafb0
fffff801`5bbdafb0 488b0549e4b8ff  mov     rax,qword ptr [nvlddmkm+0xa39400 (fffff801`5b769400)]

FAULT_INSTR_CODE:  49058b48

SYMBOL_NAME:  nvlddmkm+eaafb0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  629e9918

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  0x116_IMAGE_nvlddmkm.sys

PRIMARY_PROBLEM_CLASS:  0x116_IMAGE_nvlddmkm.sys

If you can remember when this started happening, check Windows Update History to see if there was a driver update for your Nvidia GeForce GTX 1080 card.

Try going back to an older driver, one released prior to that time.

If that doesn't help then you should try a different video card. You could get a replacement from Amazon and if it doesn't make any difference, return it.

Would a clean windows reinstall potentially resolve anything?

Unlikely, but worth trying if you take a full backup first using a program like Macrium Reflect. Then if it makes no difference simply restore the backup and you are right back where you are now with no loss of data or installed software.

Great that you have one to try.