Freezes then restarts nvlddmkm.sys

StarDude said:

My crashing is back so have been doing more testing.

I used the Microsoft Process Monitor tool this morning to capture all the process, registry, network and file activity that are happening while a crash happens.

Process Monitor - Sysinternals

Monitor file system, Registry, process, thread and DLL activity in real-time.

learn.microsoft.com

I can see Windows starting up the Window Error Reporting process: PID: 30708, Command line: C:\WINDOWS\System32\svchost.exe -k WerSvcGroup

I went looking for these error logs in C:\ProgramData\Microsoft\Windows\WER\ReportArchive

All the crashes are Kernel 141 errors which refers to a hardware failure. That lead me to this thread which is a lot of the stuff I've already tried to no avail. Tried the PCMark10 test and it came through at the 97 percentile rating with no errors.

Redirecting

Still thinking it's a video card issue or a Windows issue dealing with a game and other stuff running in the background, but don't have the luxury of having a second expensive card to swap out and try.

Click to expand...

0x141 is related to the same old TDR problem.

Thanks for that link. I guess that proves for sure it's a TDR issue.

I had to upgrade my nVidia drivers from 496.13 to 516.59 because some of my software wouldn't run on the older driver. I played on that version without any crashes which is good. I know the TDR delay is taking effect when I use my VR headset because I can see the pauses on the screen.

I supposed I could start rolling ahead driver versions to see when it starts crashing again. That would pinpoint the version where the TDR setting stops taking effect. Anyone done this already?

I also ran a 3DMark benchmark test and the result is up to 3500 from 3000 with the old drivers (v496.13) which is only halfway to the 4000 mark I had with 528.02.

What shows in Event Viewer>Admin Events when it freezes and restarts

Log Name: System
Source: nvlddmkm
Date: 1/14/2023 9:18:24 PM
Event ID: 14
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-FLF0F1Q
Description:
The description for Event ID 14 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\000000a5
0000(0000) 00000000 00000000

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="nvlddmkm" />
<EventID Qualifiers="49322">14</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-01-15T02:18:24.6394018Z" />
<EventRecordID>8508</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="1308" />
<Channel>System</Channel>
<Computer>DESKTOP-FLF0F1Q</Computer>
<Security />
</System>
<EventData>
<Data>\Device\000000a5</Data>
<Data>0000(0000) 00000000 00000000</Data>
<Binary>0000000002003000000000000E00AAC0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

And This Tooo..............................

Log Name: System
Source: nvlddmkm
Date: 1/14/2023 9:18:24 PM
Event ID: 0
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-FLF0F1Q
Description:
The description for Event ID 0 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\000000a5
UCodeReset TDR occurred on GPUID:100

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="nvlddmkm" />
<EventID Qualifiers="0">0</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2023-01-15T02:18:24.6394018Z" />
<EventRecordID>8509</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="1308" />
<Channel>System</Channel>
<Computer>DESKTOP-FLF0F1Q</Computer>
<Security />
</System>
<EventData>
<Data>\Device\000000a5</Data>
<Data>UCodeReset TDR occurred on GPUID:100</Data>
<Binary>00000000020030000000000000000000000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

StarDude said:

Thanks for that link. I guess that proves for sure it's a TDR issue.

I had to upgrade my nVidia drivers from 496.13 to 516.59 because some of my software wouldn't run on the older driver. I played on that version without any crashes which is good. I know the TDR delay is taking effect when I use my VR headset because I can see the pauses on the screen.

I supposed I could start rolling ahead driver versions to see when it starts crashing again. That would pinpoint the version where the TDR setting stops taking effect. Anyone done this already?

I also ran a 3DMark benchmark test and the result is up to 3500 from 3000 with the old drivers (v496.13) which is only halfway to the 4000 mark I had with 528.02.

Click to expand...

Able to get a dump file from your crashes ????

Newer driver out today............
Latest NVIDIA GeForce Graphics Drivers for Windows 11

So I havent had a crash in a few days after going back to 496.13 and setting TDR to 20 whereas it was crashing every 30 minutes to an hour before. Strange how quiet nvidia is being on this, every single new driver update has loads of people mentioning this. Perhaps they just take all nvlddmkm errors as generic. Would also be interested in what the most recent driver is that TDR changes stop being applied if that really is whats happening, how a driver would stop registry changes from happening is a bit confusing though.

Anyone tried 528.34?

The crash dumps are protected files in Windows.

I haven't tried 528.34. I'll be sticking with 516.59 for a while as my crashing has disappeared for now. Still need more testing though.

Another thought is that the new drivers are crashing differently which doesn't invoke the TdrDelay setting. I certainly get better graphics performance with the new drivers but maybe that's pushing the card too hard and causing a different type of failure. Underclocking didn't do anything to help with my crashes.

StarDude said:

The crash dumps are protected files in Windows.

Click to expand...

There are programs to analyze minidump files get a better understanding of your crashes.
Believe i listed them here.

Windbg is the most user friendly, you can get pretty deep traces.

Maxon Cinebench results told try to tests by someone