Question VIDEO_TDR_ERROR (I swear I have tried everything)

[Colif]

seems unlikely a M.2 would cause tdr errors. pretty specific error, I would think the driver isn't stored in exactly same spot on drive over multiple installs.
Same could be said for a CPU that doesn't have its own igpu - https://ark.intel.com/content/www/us/en/ark/products/212276/intel-core-i511600kf-processor-12m-cache-up-to-4-90-ghz.html

wonder if its worthwhile running off a Ubuntu live USB just to see if it gets tdr errors too. I see they exist on it.
https://ubuntu.com/tutorials/create-a-usb-stick-on-windows#1-overview

 

[gardenman]

Hi, I ran the dump file through the debugger and got the following information: https://jsfiddle.net/fqgdbe51/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

File information:	040622-7281-01.dmp (Apr 6 2022 - 06:34:11)
Bugcheck:	VIDEO_TDR_ERROR (116)
Driver warnings:	*** WARNING: Unable to verify timestamp for nvlddmkm.sys
Probably caused by:	memory_corruption (Process running at time of crash: System)
Uptime:	1 Day(s), 23 Hour(s), 02 Min(s), and 10 Sec(s)

Comments:

• The overclocking driver "NTIOLib_X64.sys" was found on your system. (MSI Afterburner or other MSI software)
• The overclocking driver "RTCore64.sys" was found on your system. (MSI Afterburner)
• The overclocking driver "IOCBios2.sys" was found on your system. (Intel Extreme Tuning Utility)
• BIOS info was not included. This can sometimes mean an outdated BIOS is being used.

The nvlddmkm.sys file is a NVIDIA graphics card driver. There are a few things you can do to fix this problem. First off, try a full uninstall using DDU in Safe Mode then re-install the driver (more information). Or try getting the latest version of the driver. Or try one of the 3 most recent drivers released by NVIDIA. Drivers can be found here: http://www.nvidia.com/ or you can allow Windows Update to download the driver for you, which might be a older/better version.

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[jclaumann]

So, I've been doing some reading on what could be causing the VIDEO_TDR_ERROR and I found a post on reddit explaining a certain "bug" with the memory power states of a GPU (source: here).
TL;DR
The GPUs have 3 states, P0, P1 and P2 going from "Maximum energy consumption" to "Minimum energy consumption". The problem in question MAY happen when the GPU goes from P0 state to P2.
The solution he proposed is to turn off the property that forces the GPU to enter P2 state, this basically makes the GPU always work on the highest clock and, assuming your problem is this state change, will serve as a workaround for your problem.

For this workaround you will want to download NVidia Profile Inspector (Basically this is the NVidia Control Panel but with EVERY option at your disposal, an "advanced mode"), you can get it here.
After downloading and unpacking you will run it, look for the classification "5 - Common" and turn OFF the option CUDA - Force P2 State.

I did it to my rig just to see if there would be any side effects and so far I got none (2 days with it turned off). Like I said before here I am no expert so there could be some negative side effect that I don't know of, hopefully some other user will comment on this and clarify if there is side effects.

 

[Scallywops]

I've pretty much tried everything on here, I went a month without any issues and then when I watching a video it decides to black screen again citing the same issue as before showing the same error as before. At a loss at this point. It doesn't seem to be something I can recreate...it just happens.

 

[BozoBBozo]

Long-time reader, first time poster. I registered just to offer what appears to be a solution for me.

Like @Scallywops the symptom was a black screen and GPU fans screaming, but the soft-power-down button on the case would always lead to a gentle shutdown. Often, this was in Microsoft Flight Simulator 2020, which is very hard on both GPU and CPU, but rarely it would happen outside a game.

Scallywops' research on behalf of us all in swapping out parts and trying other things was very helpful, so at a similar loss (but without the swapping out of parts - no part really seemed to be failing) I looked for configuration issues, but didn't find anything promising (XMP off, no over-clocking of GPU or CPU, etc.). Further, while I had this problem last year, it eventually stopped happening, but resurfaced in the past few weeks. GPU and CPU are NOT overheating; GPU temps top at about 62 degrees C.

So...what could have changed in the past few weeks, except...the weather?

Finally, I think I have found the problem and, for me, the solution:
THE POWER SUPPLY WAS OVERHEATING

My Seasonic Prime Gold 80+ 750w seemed to be working perfectly fine, and while I considered swapping it out (it's 3 years old), other people with this problem replaced theirs with no change in behavior.

Finally I paid attention Hybrid Mode on/off switch on the PSU, next to the power switch. Mine was currently set to Hybrid Mode ON, which I don't think was intentional - I probably accidentally pressed it while looking for the power switch. Getting out the Seasonic documentation, I found that the way that I had mounted it called for only the Normal mode to be used (in Hybrid mode the PSU fan should face the motherboard; my case has a bottom grill/outlet).

Changing the switch to Normal and...3 days later I get -0- crashes, despite numerous hours running MSFS, including some of the new resource-intensive jetliners.

I hope this helps someone.

 

[Karadjgne]

Hybrid is an economy setting. Normally it's set to default by most companies who use such on their psus. What it does is turn off the fan below a certain temperature threshold, and thats all. Gpus tend to have the same thing. With a gpu, temp is usually set at 60-65°C. Below that the fans don't spin, not until the gpu reaches the target temp, and then they kick in.

That has its good points and bad. It's good because the psu is passively cooled until target temp, so no fan noise if not doing anything power hungry. It's bad because the psu will turn on the fans at a high rate to cool itself below target, then shut the fan off. Ramps galore, which can get annoying.

Fan up simply means natural thermal convection will pull air in the back of the psu to replace the heated air that's now going up into the case. Not necessarily a good thing overall as the gpu sits right above the psu.

Personally I think Hybrid mode is more of a gimmick than serves any useful purpose in most cases, better to have a fan down normal psu with normal curves and normal sealed environment away from adding to case/gpu temps. Plus normal mode will also generally run a fan at a much lower rate consistently than Hybrids ramp ups off/ons.

 

[se7enX89X]

Been going through the same thing only it never happens when playing games. Only happens when the gpu is under light load like browsing the internet or watching videos on Youtube. I have also tried many potential fixes with no luck.

 

[Scallywops]

Been going through the same thing only it never happens when playing games. Only happens when the gpu is under light load like browsing the internet or watching videos on Youtube. I have also tried many potential fixes with no luck.

At this point I am having the same issue. No problems playing games for several hours, but I am on my desktop and it just restarts with the same error as before. Not been able to find a culprit at this point.