Question Strange BSOD sequence?
Question Strange BSOD sequence?
PC Specifications
CPU: Ryzen 5 7600X
GPU: MSI RTX 4070 Ti Ventus OC
RAM: 32GB Kingston FURY Beast 5600mhz
Motherboard: Asus TUF Gaming B650-PLUS
Storage: 2 x Samsung 990 Pro M.2 [1TB & 2TB]
Power Supply: Corsair RM850x
CPU Cooler: Noctua NH-U12S
Case: Fractal Design Pop Air
Recently I've encountered a series of unusual BSODs.
First Stop Code: UNEXPECTED_STORE_EXCEPTION
While playing a strange UE4 Dino game, the first BSOD appeared. I executed sfc, ran Windows memory checks, examined the Event Viewer, but found nothing concrete to guide me.
Second Stop Code: REGISTRY_FILTER_DRIVER_EXCEPTION
During a session with Davinci Resolve, another BSOD occurred. At that moment, I was using an NVIDIA driver version 576.52. I tried switching to 572.52 and waited about two weeks before it stopped again.
Third Stop Code: UNEXPECTED_STORE_EXCEPTION
Recently, after updating to driver version 576.88, I encountered another BSOD while running multiple Chrome tabs and performing a malware scan. It happened shortly after I exited the BIOS.
What’s puzzling is that according to my description about the drivers, the issue could relate to either the drivers or the GPU. However, it seems the problem only appears when I disconnect the PC from power for ten seconds before it restarts into Windows.
I’ve completed extensive benchmarks and 3DMark tests, played games without issues, but now it’s back and I’m unsure if the GPU driver is the cause.
Share the .dmp files with us to review. The host uploaded them to a service similar to DropBox and shared a link in this discussion.
need the actual .dmp files to accurately identify the reason behind the bugchecks.
usually, you should include a list of parameters for the bugcheck.
(they often display the error code)
for the store exception, ensure your memory is functioning properly (run memtest86) and verify outdated device drivers compatible with Windows 7.
the debugger may also detect changes to Windows files, as some legacy programs alter memory locations that no longer match the new compression methods.
(results: UNEXPECTED_STORE_EXCEPTION bugcheck)
I completed 1 hour of OCCT CPU/memory tests without any problems. Then I ran a malware bytes scan on the entire PC three times, and none of those scans triggered BSODs or generated dump files during any of the previous BSODs. I checked the Event Viewer for a bugcheck as well, but found nothing. The BIOS version is 2413, all drivers are up to date, and the NVMe firmwares are current. All system parts are over a year old.
download and execute microsoft autoruns64.exe
search for outdated third-party drivers compatible with Windows 7 and 8 days
https://learn.microsoft.com/en-us/sysint...s/autoruns
find legacy drivers that integrate with Windows functions (currently restricted)
these are non-official, third-party drivers or tools
you may open cmd.exe with administrator privileges then run
dism.exe /online /cleanup-image /restorehealth
to fix altered Windows files, which will also delete license modifications
Based on these bugchecks, I'd start by examining the RAM first, as it appears to be a common issue across all three. I suggest removing the XMP/DOCP RAM overclock and testing the RAM at its original (SPD) speed to check for stability.
Additionally, note that according to AMD's CPU specifications, the maximum RAM clock speed they guarantee the processor can handle is 5200MHz. While most processors can run smoothly with speeds higher than this, these increased rates aren't assured. If the RAM remains stable at the SPD speed (around 4800MHz), consider overclocking it to 5200MHz and verify stability at that higher frequency.
I had expo turned off at 5200mhz, then it completed memory checks and OCCT stress tests (memory, power, CPU, etc.) which passed for over an hour. After that, I tried a few games and didn’t experience BSODs. I performed a full malware scan once; it didn’t show any issues on the second run. I reopened the Event Viewer and found no evidence of problems except error code 161 related to dump file creation. Additionally, I ran sfc multiple times, and both drives passed Samsung Magician tests—systems are fully healthy.
why do you have two versions of amdryzenmasterdriver installed? v 20 and v 27 in different directories but with the same driver name. This can lead to a loading conflict and cause the memory manager to load one at a time. Both drivers will adjust CPU voltages, so you should uninstall the older ones (or both) and reinstall the current version before retesting.
rtcore64.sys is another warning sign. It's simple to exploit and gives full access.