Nvlddmkm \Device\Video3 Error occurred on GPUID: 900

I just wanted to follow-up, after toggling the Debug option in the Nvidia Control Panel, I haven't been able to reproduce the frequent crashing after leaving my PC idle in-game for the last couple hours. I'd suggest giving that a try if you haven't yet. Just keep it in mind when testing future drivers to see if the issue has been resolved organically.

TL;DR: Why are you so toxic? Lowering the power limit fixed the problem for you and some others*. But apparently there are either multiple causes for the problem or multiple solutions. It seems that you are convinced that everyone is stupid except you. So it comes across at least in some answers.

Don't go after everyone who disagrees with you. It doesn't help anyone.

Looks more like you're mixing things up here:

"I never said it is caused by a physical hardware defect inside the gpu silicon or vram. I said it is caused by a power instability [...]"

Can you please show me, where I have insinuated that? Nobody has talked about a defect inside the silicone the besides you in your reply to me. And you even wrote in that same reply that a broken PSU or Motherbord could be the reason. Isn't that a hardware defect? Also you wrote multiple replies to other users where you explicitly taked about a hardware defect:

"the crash will happen with either 100% GPU or 100% VRAM load, [...]"

The problem also occurred when there was little to no load on the graphics card. When I am just in a Discord call with another person where we both have the camera on, the load averages around 7 - 15%. Sometimes there is a short peak at 40%, but that's about it. The problem happened probably even more often in idle than under load, because we are just chilling most of the time and not always gaming. In what way should it have something to do with the power supply of the card or be caused by it?

"you didnt seem to have tested the workaround, because you didnt say anything about it. [...]"

That is correct. Since all hardware (except the processor) has changed since the problem initially occurred. Therefore, I ruled out a hardware defect and did not try your solution.

* The only two replies that say the problem was fixed by mkxy's solution were posted by accounts that were created the same day as the reply and have also not been active since. I don't want to imply anything here, but it does come across a bit strange. After seeing your last reply to serfrost It wouldn't wonder me, if you are the one talking ****. The only two answers that agree with you are from accounts created on the day of the answer. That was always the only answer. Looking at the way you act and treat people here, I wouldn't be surprised if the accounts were created by you just to make it look like you're right...

Started having this issue with my GTX1080 after recent Windows Updates/Driver Update, not sure with which specific one.

• Changed cables.
• Changed GPU. (I had a spare for testing.)
• Normally use stock clocks, tried undervolting.
• Changed displays.
• Reinstalled affected games.
• Completely cleaned out the drivers and reinstalled.

In the end, this isn't hardware instability. This appears to be related to the driver or Windows. Turning off GPU Scheduling and/or using the Debug option under Nvidia seems to have bypassed the issue, but it isn't a solution. The solution would be for the vendors to correct the new issue.

If you're asking yourself "Why am I being told to undervolt/underclock?" and the reason this might help some users is that it'll simply make your card slower and less likely to encounter the problem. It isn't a solution, it's just a way to avoid the problem.

In the end, your card isn't unstable and there's been plenty of feedback here expressing plenty of examples against that.