Question Random sleep mode crashes after upgrading to an Nvidia RTX 3060

Aug 3, 2023
3
0
10
Hi everyone,
I'll start off by writing my PC specs:
  • CPU: Intel Core i5-6400
  • Motherboard: ASRock Z170 Pro4 (using the latest BIOS version)
  • RAM: two sticks of DDR4 HyperX Fury 8 GB
  • GPU: Zotac GeForce RTX 3060 Twin Edge OC
  • SSD: Samsung 860 EVO 250 GB
  • HDD: Western Digital Caviar Blue 1 TB
  • PSU: Seasonic S12II-520 (520W 80+ bronze)
  • Monitor: Samsung C24F390 (Full HD, 24 inches)
  • 3 fans
My Windows version: Windows 10 Pro N - 22H2
Nvidia drivers version: 536.67

An important premise: I had an Nvidia GTX 970 (the Windforce version from Gigabyte) and sleep mode worked perfectly fine.

Here's the problem: I put the PC to sleep, I leave it alone for 5/10/15/60 minutes (I have tried different intervals of time) and when I try to wake it up using the keyboard or the mouse (they both work), the PC box turns on just fine, but nothing is shown on screen, it just stays black. After 15/30/60 seconds (yes, it varies), the PC restarts on its own (I never have to force a shutdown by pressing the power button etc.) and it presents to me the Windows login page - I login and I have lost all my stuff. This happens if I actually leave something open, like a browser tab or Steam homepage. The PC probably gets a BSOD but I just can't see it, the monitor stays off with the power light blinking.

If I check the Windows Event Viewer, I always find the infamous Event ID: 1001 Bugcheck 0x00000119 with Parameter 1: 0x0000000000000002.

One other important thing: If I just turn on my PC, login into Windows and put the PC to sleep, I am able to wake it up properly.

Now, there are different things I have already tried:
  • I have run MemTestx86 (4 pass, both the sticks installed) and everything was OK;
  • I have uninstalled the Nvidia drivers using DDU and reinstalled them. I've also tried to install an older version, 528.24. Nothing changed.
  • I have disabled Fast Startup, Hybrid Sleep (and I've also tried different combinations of them). Nothing changed.
  • I have cleared the CMOS. Nothing changed.
  • I have tried to use different ports for the keyboard and the mouse. Nothing changed.
I also might have done something else, but right now I don't remember... Anyway, the PC runs just fine, games don't crash, light usage gives no problems, the PC can stay on all day and I'm also using the GPU for StableDiffusion and AI stuff.

I'm starting to think that the PSU might be the problem (Zotac suggests a 600W PSU). I don't know, it might also be the motherboard... I do realize that the PC is pretty old and in fact I'm planning to replace everything in a few months, but I just can't understand how everything is crashing after sleep mode.

And... no, I would like to keep sleep mode, I don't want to disable it.

Do you have any tips/suggestions? Is it the PSU?
 
It might help to upload any minidumps (in C:\Windows\Minidump folder) to the cloud with a link to them here (be sure to make them public).

That said, the 0x119 bugcheck you report is a VIDEO_SCHEDULER_INTERNAL_ERROR. The argument 1 value of 1 you reported means that the driver reports an invalid fence ID. These are used as pointers in to buffers. This is likely to be either a driver error or a graphics card error.

I would suggest you download DDU and the three most recent versions of the graphics driver from the Nvidia website. Use DDU to uninstall the current driver and after ir reboots install the latest version of the driver. If it still fails, use DDU again and then install the next previous version of the driver. If that fails then use DDU again and install the two levels back driver version. If all three driver versions fail then the problem is almost certainly with the graphics card itself.
 
As expected, all five dumps are identical and all show 0x119 bugchecks. The value of argument 1 in the dumps however is 2, which means that the driver failed on submission of a command. That too could either be a driver issue or a card issue.

My advice remains the same as above, use DDU to try the most recent three versions of the driver. If they all BSOD then it's almost certainly a graphics card issue.