nvlddmkm.sys CONSTANT crash

Hi.

Hoping someone can help as I'm at my wits end, been dealing with this crash related to nvlddmkm.sys for over a year. At any time my pc will suddenly lose signal and go completley unresponsive (much more common when gaming though), sometimes it will go days without doing it then gets really bad again. Pressing the caps lock and number lock etc will not even work and I have to reboot the pc. It happened 3 times just yesterday. I have used DDU multiple times to wipe the drivers and reinstall, I have reinstalled windows as I thought this was because the install was on a dying SSD, I have used memtest to test my ram and came back fine.

I have attached the error in event viewer.
The description for Event ID 153 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

\Device\Video3
Error occurred on GPUID: a00

The message resource is present but the message was not found in the message table

I have also attached a minidump of the crash.

Can anyone help please!?

Just noticed the minidump won't attach so have copied and pasted below.

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffe70f79371010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff80178c46790, 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
*** WARNING: Check Image - Checksum mismatch - Dump: 0xc2ed94, File: 0xc31fe0 - C:\ProgramData\Dbg\sym\ntkrnlmp.exe\783A7A83144f000\ntkrnlmp.exe

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1921

Key : Analysis.Elapsed.mSec
Value: 2653

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 0

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x116

Key : Bugcheck.Code.TargetModel
Value: 0x116

Key : Dump.Attributes.AsUlong
Value: 0x21008

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: 0x116_IMAGE_nvlddmkm.sys

Key : Failure.Exception.IP.Address
Value: 0xfffff80178c46790

Key : Failure.Exception.IP.Module
Value: nvlddmkm

Key : Failure.Exception.IP.Offset
Value: 0x1856790

Key : Failure.Hash
Value: {c89bfe8c-ed39-f658-ef27-f2898997fdbd}


BUGCHECK_CODE: 116

BUGCHECK_P1: ffffe70f79371010

BUGCHECK_P2: fffff80178c46790

BUGCHECK_P3: ffffffffc000009a

BUGCHECK_P4: 4

FILE_IN_CAB: 031625-6984-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
Kernel Generated Triage Dump

FAULTING_THREAD: ffffe70f75f56040

VIDEO_TDR_CONTEXT: dt dxgkrnl!_TDR_RECOVERY_CONTEXT ffffe70f79371010
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:
ffffe584`9f2b58c8 fffff801`67de15ad : 00000000`00000116 ffffe70f`79371010 fffff801`78c46790 ffffffff`c000009a : nt!KeBugCheckEx
ffffe584`9f2b58d0 fffff801`68069f7e : fffff801`78c46790 ffffe70f`70930010 00000000`00002000 ffffe70f`709300d0 : dxgkrnl!TdrBugcheckOnTimeout+0x101
ffffe584`9f2b5910 fffff801`67df049d : ffffe70f`7092c000 00000000`00000000 00000000`00000004 00000000`00000000 : dxgkrnl!ADAPTER_RENDER::Reset+0x12a
ffffe584`9f2b5940 fffff801`67e26bf5 : ffff9681`991d0180 ffffe70f`75f56040 ffffe70f`00000000 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x589
ffffe584`9f2b59d0 fffff801`67e26d52 : ffffe70f`6a2d5260 ffffe70f`6469cd30 00000000`00000000 00000000`00000000 : dxgkrnl!TdrResetFromTimeout+0x15
ffffe584`9f2b5a00 fffff801`d6117b02 : ffffe70f`75f56040 ffffe70f`64723b60 ffffe584`9f2b5b00 ffffe70f`00000000 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x22
ffffe584`9f2b5a40 fffff801`d624fd8a : ffffe70f`75f56040 ffffe70f`75f56040 fffff801`d6117950 ffffe70f`64723b60 : nt!ExpWorkerThread+0x1b2
ffffe584`9f2b5bf0 fffff801`d647a024 : ffff9681`991d8180 ffffe70f`75f56040 fffff801`d624fd30 fffff801`d608b1cb : nt!PspSystemThreadStartup+0x5a
ffffe584`9f2b5c40 00000000`00000000 : ffffe584`9f2b6000 ffffe584`9f2b0000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME: nvlddmkm+1856790

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffffe70f646c8040; .thread 0xffffe70f75f56040 ; kb

FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

Followup: MachineOwner
---------

In safe mode, Uninstall your graphics driver AND its software using DDU Display Driver Uninstaller (DDU) download version 18.1.0.0

Instructions here Display Driver Uninstaller Thread

Reinstall drivers from here Download The Latest Official GeForce Drivers

If that does not fix the problem open another post here. BSOD Crash Analysis
Gather the necessary logfiles for further analysis using these instructions BSOD - Posting Instructions

glasskuter said:

In safe mode, Uninstall your graphics driver AND its software using DDU Display Driver Uninstaller (DDU) download version 18.1.0.0

Click to expand...

The OP has tried using DDU three times. He doesn't state whether or not DDU was used in safe mode.

Marcus Vinicus said:

The OP has tried using DDU three times.

Click to expand...

You're right. That didn't soak in with me so sorry about that. I'm wondering if the OP is installing the latest version of the driver issued yesterday 3/18/25

Hi everyone

I did use DDU in safe mode. Also I updated to the new driver today.

Small update, I have found online a way to extend TDRDELAY in registry editor, and applied these settings. I then played a game and everything seemed ok however I am now getting a new BSOD (DPC_WATCHDOG_VIOLATION (133)). This is a new error but says nvlddmkm.sys is still responsible.