VIDEO TDR FAILURE within a few mins of opening something that displays anything in 3D
Update: I have reinstalled drivers and am now using the outdated one from windows, as long as I keep the VRAM usage below 2GB it doesn't BSOD nor Freeze
Update Update: The old computer is now in the garbage, couldn't use it because the specs were fake ;-;
Okay this has been happening on and off for almost a year by now but the problem kept changing but am still 100% sure its the drivers. The BSOD was always VIDEO\_TDR\_FAILURE
First time problems started showing up were graphical glitches that looked like my graphics card was dead and then after that as soon as I inputted my password and logged onto windows it would BSOD. I got tired of the BSODs and googled a way to make it stop and a youtube video said to just delete the TdrDelay in the registry which just turned the BSOD into a freeze. This disappeared the next day
Then the second time it just froze on boot up on the part where you can open the BIOS. I ran sfc /scannow and it fixed stuff and I checked the TdrDelay thing and it was back but set to 0. This disappeared in around 4-6 hours
Then the third time was it just freezing the moment I opened a game. Kept trying and there was no BSOD most of the time but sometimes it BSOD. I tried multiple driver versions and uninstalled them using DDU. Disappeared in 3 days.
Fourth time it just decided to randomly die or BSOD or freeze. I uninstalled the driver with DDU and just waited for windows to install it's outdated driver but this kept happening but less and less often. It took a day till it was useable again and about a week till it completely went away.
Now the fifth time is where it dies within 2mins of displaying something in 3D but only in a game. I've tried the latest one and it fixed itself for the first 4 hours and came back. I tried using the backup VGA drivers and it worked even though it was at 3seconds per frame there was no BSOD, idk if that means anything though. **EDIT:** It still freezes after 2mins even if I close the game.
Disclaimer: my shitty memory may have misremembered some things
I have no idea what am supposed to do now. Im getting a new pc in a month but I wanna turn this into a server or something so I still wanna fix this. heres the dump result ig
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
\* \*
\* Bugcheck Analysis \*
\* \*
\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
​
VIDEO\_TDR\_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: ffffcb88ca57a010, Optional pointer to internal TDR recovery context (TDR\_RECOVERY\_CONTEXT).
Arg2: fffff80316a10960, 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:
\------------------
​
\*\*\* WARNING: Unable to verify timestamp for nvlddmkm.sys
\*\*\* WARNING: Unable to verify timestamp for win32k.sys
​
BUGCHECK\_CODE: 116
​
BUGCHECK\_P1: ffffcb88ca57a010
​
BUGCHECK\_P2: fffff80316a10960
​
BUGCHECK\_P3: ffffffffc000009a
​
BUGCHECK\_P4: 4
​
PROCESS\_NAME: System
​
SYMBOL\_NAME: nvlddmkm+eb0960
​
MODULE\_NAME: nvlddmkm
​
IMAGE\_NAME: nvlddmkm.sys
​
FAILURE\_BUCKET\_ID: 0x116\_IMAGE\_nvlddmkm.sys
​