Question BSODs when PC is idle/doing nothing/light tasks, but doesn't BSOD when under load ?

[imasuperguy]

Ive been dealing with BSODs the past year and recently theyve been getting worse.. I've gone through reddit forums where others have found success in undervolting. The common denominator seems to be either RGB software or AMD CPUs. I managed to temporarily fix my problem with increasing the voltage on my CPU by 0.05 but that only worked for about a week before the issue returned. Going through my MiniDumps it seemed the it was LightingService.exe that was the cause but after deleting that it had become OVRService, I even have one with Brave being the problem. Other issues im facing are Chrome tabs randomly crashing and constant BSODs with the following codes:

MEMORY MANAGEMENT
IRQL NOT LESS OR EQUAL
PAGE FAULT IN NON PAGED AREA
SYSTEM SERVICE EXCEPTION
KMOD EXCEPTION NOT HANDLED
KERNEL SECURITY CHECK FAILURE
BAD POOL HEADER
DPC WATCHDOG VIOLATION

and sooo many more that I haven't even recorded yet, these are just off the top of my head. It is a daily occurrence with these yet they never happen when im playing Games, they only happen when im using Chrome or leave my PC on doing nothing.

Ive used DDU to wipe drivers and reinstall, ive uninstalled and reinstalled CPU drivers, update motherboard BIOS, run memory tests and everything seems fine. Right after installing the CPU drivers my PC actually BSOD but that was after the install was complete and wasn't during, the drivers were also installed in safemode.

My PC refuses to boot when undervolted as well, and ive watched plenty of tutorials and im sure im not doing anything wrong. This has me thinking its either a Motherboard or CPU issue or perhaps Windows itself but I could also see it possibly being a PSU issue?

Specs:
Mobo: Asus ROG B450-F
CPU: Ryzen 3600X
Gigabyte RTX 3070 Ti
RAM: 2 x 8GB Corsair Vengence RGB DDR4
Storage: Windows boots off an NVMe SSD, and I also have an HDD.

Minidump files (5 of them)

 

[ubuysa]

Hello and welcome to the forum!

Those five dumps taken together look very much like bad RAM, so before looking at anything else we need to test your RAM...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

 

[johnbl]

I see various problems with your build:

I would start by removing aura LightingService.exe
looked like a cleanup routine did a double remove of a memory address
(note you could update the bios and update the asus drivers and the asus lightingservice.exe and attempt to fix the problem)

note:
BIOS Release Date 08/29/2024
but various asus drivers are old, looks like the bios was updated but the various motherboard drivers were not updated. go to the motherboard vendor and update the motherboard drivers.

other problems/issues:
very old driver:
WinRing0x64.sys Wed May 1 19:19:47 2013 (often used for hacking)
vmulti.sys Fri Nov 2 00:42:34 2018
MsIo64.sys Sun Feb 11 23:57:50 2018 (old driver that is a hack target)

inpoutx64.sys Fri Oct 17 16:01:16 2008 (old driver)
GLCKIO2.sys Mon Apr 22 06:44:46 2019

old overclock driver:
AMDRyzenMasterDriver.sys Sun Dec 15 21:10:07 2019
this driver should be updated when the bios is updated.

best guess would be that the asus lighting is the cause of the bugcheck I looked at.
most of the other problems will be fixed by updating the motherboard drivers to match the installed version of the bios. my guess is that the asus software talks to the gclckio2.sys and it deallocates some memory twice (bug) then the system later at idle time does a cleanup and this causes the bugcheck when the system goes idle.

 

[imasuperguy]

I see various problems with your build:

I would start by removing aura LightingService.exe
looked like a cleanup routine did a double remove of a memory address
(note you could update the bios and update the asus drivers and the asus lightingservice.exe and attempt to fix the problem)

note:
BIOS Release Date 08/29/2024
but various asus drivers are old, looks like the bios was updated but the various motherboard drivers were not updated. go to the motherboard vendor and update the motherboard drivers.

other problems/issues:
very old driver:
WinRing0x64.sys Wed May 1 19:19:47 2013 (often used for hacking)
vmulti.sys Fri Nov 2 00:42:34 2018
MsIo64.sys Sun Feb 11 23:57:50 2018 (old driver that is a hack target)

inpoutx64.sys Fri Oct 17 16:01:16 2008 (old driver)
GLCKIO2.sys Mon Apr 22 06:44:46 2019

old overclock driver:
AMDRyzenMasterDriver.sys Sun Dec 15 21:10:07 2019
this driver should be updated when the bios is updated.

best guess would be that the asus lighting is the cause of the bugcheck I looked at.
most of the other problems will be fixed by updating the motherboard drivers to match the installed version of the bios. my guess is that the asus software talks to the gclckio2.sys and it deallocates some memory twice (bug) then the system later at idle time does a cleanup and this causes the bugcheck when the system goes idle.

Ive gone ahead and uninstalled my chipset drivers and reinstalled them, I also uninstalled asus AURA sync and removed the lightning service through CMD (as after uninstalling the service still remained on my PC; though i already had it disabled). One thing this got me able to do was to actually launch up and use Davinci Resolve for a few minutes as it would usually crash/BSOD when attempting to access files on my D drive. Nothing came about it so I went ahead and tried installing a game on Steam, mid install the PC BSOD again.

Minidump (just one as it just happened)

As for those outdated drivers, other than installing new chipset drivers and updating the BIOS how would I go about updating them? The only drivers available on my B450f are chipset, LAN, VGA, Audio, SATA and something called Armoury Crate. I also uninstalled AMD Ryzen Master since I didn't use it, but you did say that it should've been updated when I updated the BIOS so im not sure what to do from here.

 

[imasuperguy]

Hello and welcome to the forum!

Those five dumps taken together look very much like bad RAM, so before looking at anything else we need to test your RAM...

1. Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
2. Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
3. If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.

Let us know how that goes.

I ran memtest86 and didn't get any errors (though I didn't do the amount of passes you suggested, only 2 as I didn't have the time to run it so much), I also ran OCCTs ram tester and that passed the first time, but PC would BSOD the following tests (but i dont think it was due to the RAM test since it is a windows application meaning windows would BSOD while/after the test). Memtest would require my PC to be unusable for a whole day if I wanted to run so many tests, so I made a warranty claim with Corsair given their "Limited Lifetime Warranty"; still waiting on a response though.

 

[ubuysa]

You only have 16GB so two runs of Memtest86 shouldn't take all day. Even so, troubleshooting is often time consuming.

You could instead remove one stick and run for a day or two on each stick on its own.

 

[imasuperguy]

You only have 16GB so two runs of Memtest86 shouldn't take all day. Even so, troubleshooting is often time consuming.

You could instead remove one stick and run for a day or two on each stick on its own.

Should mention I tried that already along with unplugging my D drive and still got BSODs. I doubt both of my RAM sticks have gone bad, leading me to believe it could be a CPU, Motherboard or driver issue.

 

[johnbl]

the new bugcheck was a due to a hung cpu core.
this can not be debugged with a minidump, you would have to provide a kernel dump so I could see what was running on all cores.
the file would be memory.dmp

note: this could be caused by plug and play attempting to install a driver but failing to install a driver on one core while a service on another core is attempting to use the driver.

provide the kernel dump if you have it.
cpu 7, 5 and 2 were active
fyi:
several of your windows core files have been modified.
now also droidcamvideo.sys has also been modified
old drivers that are used for hacking are still installed.
You might consider just doing a clean install from a known good copy of windows.