Recent content by squidbats

RMAing cards has fixed it for some but in my experience of researching it by far the least. Mostly seems to be RAM or RAM slots failing on the hardware side of things, for me it was my entire motherboard. Replacing it with a board with better VRMs has completely fixed my problem, but it took my...

After stress testing my 3060 for 7 hours in another machine with a 1660S in the machine that was crashing my motherboard VRM eventually failed, replacing the motherboard and using my 3060 I have had no crashes on the most recent drivers, I guess this error is so generic all sorts of hardware...

Im currently swapping my 3060 to another system and putting the other systems 1660 in to see if the error follows the card before I RMA.

Be interested to know how people have their cards mounted, I started getting really frequent crashing, even on the old drivers. Decided to thoroughly clean my RAM slots and my PCIE slots and turn my PC case on its side as my default mounting has the gpu mounted horizontally, this mean my GPU was...

So after over a week of no crashing, I stupidly let windows update, now I get crashes almost immediately in games, sometimes TPM crashes sometimes the usual nvlddmkm crashes, DDUing old driver didnt fix it, Im now rolling back the windows update to see if that helps. This is such a ridiculous...

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

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...

On the newer drivers I have the exact same error as yours but in games, nvlddmkm.sys black screen \Device\Video3 Error occurred on GPUID: 100. Mine only started after I updated from 516.94 (I meant 94 not 93 as thats the game ready driver) to more recent drivers. So the next few drivers after...

So after rolling back to 516.93 mine is far more stable, so perhaps those people were just not DDUing properly. One really odd thing I had 3 crashes that were almost identical after downgrading, but they gave a different error in event viewer to do with ntkrnlmp.exe, which turned out to be...

So after reading the reddit posts for the most recent driver release there are 100s of people with the same problem, a worrying number of them have found after updating to the most recent drivers rolling back no longer fixes the issue leading to speculation that the drivers have somehow...

Yeah, I also get the same voltage spike just before the crash as well. my minidump also says its a DPC_WATCHDOG_VIOLATION at IRQL of DISPATCH_LEVEL or above, which is common in other types of driver errors. Quite a few people had identical problems caused by HW monitoring apps and RGB software...

Hey there, I joined to say I have the exact same problem, been a few weeks of following different threads everywhere, and it seems like most of the current fixes that have worked for some have made their way here. I have black screen crashes every few hours in games, usually DX12, on 528.02...