Question Weird series of BSODs ?

DeltaCape

Prominent
Mar 21, 2024
34
3
535
PC Specs
CPU: Ryzen 5 7600X
GPU: MSI RTX 4070 Ti Ventus OC
RAM: 32GB Kingston FURY Beast 5600mhz
Mobo: Asus TUF Gaming B650-PLUS
SSDs: 2 x Samsung 990 Pro M.2 [1TB & 2TB]
PSU: Corsair RM850x
CPU Cooler: Noctua NH-U12S
Chassis: Fractal Design Pop Air

So I'm having the weirdest series of BSODS lately.

1st STOP CODE: UNEXPECTED_STORE_EXCEPTION

I was playing a weird UE4 Dino game and that's when the first BSOD occurred I ran sfc, windows memory checks, checked for errors in event viewer and I couldn't find anything that would point me in any direction.

2nd STOP CODE: REGISTRY_FILTER_DRIVER_EXCEPTION

This time I was learning davinci resolve and suddnely another BSOD, at this time I was on nvidia driver version 576.52 I went ahead and went down to 572.52 and then they just stopped for about 2 weeks or so.

3rd STOP CODE: UNEXPECTED_STORE_EXCEPTION

Few days ago I updated to 576.88 and today I had several chrome tabs and I was running a malware bytes scan and about few minutes into, there it goes again another BSOD.

What makes it strange is that based on what I said about the drivers you might think it's something to do with the drivers or the gpu right? But what makes me unsure is the fact that everytime it bsods it throws me into bios and my main 2tb drive that windows is on doesn't show up in bios and if I save and exit from bios it boots me back into bios, only after do I disconnect the pc from power for 10 seconds and then it boots back into windows.

I'm really scratching my head with this one because I've ran extensive occt and 3dmark benchmarks and played games and it seemed stable but now it's back and I'm not so certain that it's the gpu driver.
 
Last edited by a moderator:
You should pass on the .dmp files for us to look through. Host said .dmp files onto a site akin to DropBox and then pass on a link in this thread.

32GB Kingston FURY Beast 5600mhz
The sweet spot for AMD's AM5 platform is DDR5-6000MHz, dual channel with tight latencies.

Asus TUF Gaming B650-PLUS
What BIOS version are you on for your motherboard?

SSDs: 2 x Samsung 990 Pro M.2 [1TB & 2TB]
Use Samsung's Magician app and see if your drives have firmware updates pending.

Corsair RM850x
How old is the PSU in your build?

Few days ago I updated to 576.88 and today I had several chrome tabs and I was running a malware bytes scan and about few minutes into, there it goes again another BSOD.
Go into BIOS, disable the iGPU. Then use DDU to remove all GPU drivers(intel, AMD and Nvidia) in Safe Mode. Then manually install driver version 566.36 in an elevated command, i.e, Right click installer>Run as Administrator, and see if that alleviates the issue.
 
need the actual .dmp files to make a good guess as to the cause of the bugchecks.

generally, you should provide the list of parameters for the bugcheck also.
(often they will show the error code)

for the store exception you would want to make sure your memory is running without any errors (run memtest86) and check for old device drivers that were written for windows 7. The debugger can also check for modified windows files (some old windows 7 program would modify the windows files and access memory locations that would not be valid with the new memory compression that windows uses. (results UNEXPECTED_STORE_EXCEPTION bugcheck)
 
I ran 1hr occt cpu / memory tests without issues, then a malware bytes scan of the entire pc 3 times and that again didn't trigger the bsod and no dump files were created on any of the bsods previously mentioned. I looked at event viewer for a bugcheck too none to be found.

BIOS version is 2413 all drivers up to date along with nvme firmwares.

All system components are a little over a year old.
 
download and run microsoft autoruns64.exe
look for old 3rd party drivers (from windows 7 and 8 days)
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

look for old drivers that hook into windows functions. (not allowed now)
these will be non microsoft provided drivers (3rd party, driver/tools)

you can run cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth
to repair modified windows files, this will also remove license hacks
 
Given these bugchecks I'd look first at RAM, it's the common denominator in all three. I'd would recommend removing the XMP/DOCP RAM overclock and run the RAM at its native (SPD) speed, see whether it's stable there.

Also be aware that from the CPU specs, the maximum RAM clock speed that AMD guarantee the processor will work with is 5200MHz. Most processors will happily run with RAM faster than this, but these higher speeds are not guaranteed. If it's stable at the SPD speed (4800MHz?) then overclock it to 5200MHz and see whether it's stable there.
 
download and run microsoft autoruns64.exe
look for old 3rd party drivers (from windows 7 and 8 days)
https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns

look for old drivers that hook into windows functions. (not allowed now)
these will be non microsoft provided drivers (3rd party, driver/tools)

you can run cmd.exe as an admin then run
dism.exe /online /cleanup-image /restorehealth
to repair modified windows files, this will also remove license hacks
I had expo enabled at 5200mhz disabled it ran memory checks and occt stress tests (memory, power, cpu etc) which it passed for 1hr+ then I tested a few games didn't bsod then I ran malwarebytes full scan once didn't bsod second time it did bsod then it bsod'd twice in cyberpunk. I did a deep dive into event viewer again and there isn't a single trace of what could be wrong except the error code 161 due to the failure of creating the dump file. Also ran sfc several times nothing and both drives according to extensive samsung magician tests and winodws are completely healthy.
I8jT7Op.png
 
I had expo enabled at 5200mhz disabled it ran memory checks and occt stress tests (memory, power, cpu etc) which it passed for 1hr+ then I tested a few games didn't bsod then I ran malwarebytes full scan once didn't bsod second time it did bsod then it bsod'd twice in cyberpunk. I did a deep dive into event viewer again and there isn't a single trace of what could be wrong except the error code 161 due to the failure of creating the dump file. Also ran sfc several times nothing and both drives according to extensive samsung magician tests and winodws are completely healthy.
I8jT7Op.png
why do you have 2 different versions of amdryzenmasterdriver installed? v 20 and v 27 different directories but the same driver name. (this will cause a loading conflict and windows memory manager will load one at an offset. Both drivers will take turns tweaking voltages to the cpu. you should uninstall the oldest one (or both, and reinstall the current version) then retest.
 
why do you have 2 different versions of amdryzenmasterdriver installed? v 20 and v 27 different directories but the same driver name. (this will cause a loading conflict and windows memory manager will load one at an offset. Both drivers will take turns tweaking voltages to the cpu. you should uninstall the oldest one (or both, and reinstall the current version) then retest.
Yeah I was wondering the same exact thing, I completely nuked ryzen master about a month ago and reinstalled it to try and ensure no conflicts on update occurred.
 
So I completely removed ryzen master re ran all stress tests all stable but then I launched games again cyberpunk after 3 mins bsod, r6 siege 15 mins bsod, malwarebytes full scan first pass no problem second scan bsod aswell. KMODE_EXCEPTION_NOT_HANDLED
 
The 161 log error can be caused by bad RAM. You have 32GB installed, is that 2 x 16GB? If so then I'd be tempted to remove one stick for a few days and see whether the BSODs stop. Swap sticks after a few days and run on just the other one. You'll soon see whether one stick is flaky.
 
So I completely removed ryzen master re ran all stress tests all stable but then I launched games again cyberpunk after 3 mins bsod, r6 siege 15 mins bsod, malwarebytes full scan first pass no problem second scan bsod aswell. KMODE_EXCEPTION_NOT_HANDLED
you should look at parameter 1 of the bugcheck code. (parameter 1 = the error code)
see if it is
0xC0000005 = STATUS_ACCESS_VIOLATION

or provide the minidump.