Question ntlddmkm event 0

outlawstar15a2

Distinguished
Mar 25, 2010
81
0
18,540
Yesterday the GPU display driver crashed, hung for about 10 seconds, then recovered. I looked in Event Viewer and saw this:

"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\Video3
Resetting TDR occurred on GPUID:100

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

What the hell is this?I had a similar problem last year with 531.79 it was so bad that it was happening at least once a week and in the final days it was happening every 2-3 minutes. So I took some advice from here and downgraded to 517.48 which ran fine then 10/31 of this year I upgraded to 537.58 to troubleshoot an issue with SSTE (it didn't help) but I had no issue with the driver itself so I kept it then this morning the error above occured and that's what was printed in Event Viewer, source ntlddmkm, so for the time being I downgraded back to 517.48 thing is some of my games don't run with 517.48 (Ruined Nurse) so I want to upgrade to the latest driver. But anything above 517.48 seems to eventually trigger this error after about a month or more of use. I thought it was temp related so I am monitoring temps but I am not seeing any problems. And even if I did I originally ran 517.48 for over a year with no problem. I have to upgrade the driver later today and there's a very good chance I will see this error in the future. WHAT IS CAUSING IT? Cause I can't camp on 517.48 forever. I have an EVGA RTX 2070 Super XC Gaming Edition GPU. I put this system together back in early 2020 so I doubt the card is dying from age.

Might the info from HWinfo64 be of any use?
==================================================================================================================================================================================================================================================================================
Windows 10 64-bit Professional
i5-9600K
Gigabyte Z390 AORUS Pro Wifi
32GB G.Skill (F4-3600C19-8GVRB) DDR4 RAM @1800MHz
EVGA RTX 2070 Super XC Gaming GPU
Two Dell 2721DGF Monitors
Two Crucial P1 NVMEs (CT1000P1SSD8)

Key Takeaways

-Ran SFC /verifyonly and Windows detected no issues
-Problem does not seem to occur on the 517.48 at least so far
-Problem occured when Windows auto updated to 531.79 (this is how I discovered this issue)
-Problem also occured with 537.58 after a little over a month with no issue
-All version changes were done with DDU updated, except the Windows auto install (because Windows snuck that in).
-I have the newest OS updates Windows is not offering me anything right now
-The problem is intermittent and random with very long mean time between incidents. When I had 531.79 it used to be about 2-3 months between occurences however over time it became more frequent till it was happening multiple times a day. I fixed it back then by rolling back to 517.48
-I need update past 517.48 as some of my newer games do not run at all under this version. So I need to find out what is missing or a way to circumvent this issue.
-System was initially put together back in early 2020 so it's not ancient.
-Have to install drivers in safe mode otherwise Windows will auto install some random driver before I can install mine and then I have to DDU all over again to remove it. Changing policies or forbiding it doesn't seem to work if there is no driver. Unhooking from internet doesn't stop it either.
-Been monitoring temps while gaming or watching videos. GPU and CPU temps are well within their respective green zones.

Quick question when I install my drivers I do a custom installation. I leave the path as default but choose to only install the driver, the optional components like the UEBC driver or whatever it's called is not installed. Is that a factor?
 
Last edited: