F5F Stay Refreshed Hardware Desktop Has multiple error screens appearing repeatedly?

Has multiple error screens appearing repeatedly?

Has multiple error screens appearing repeatedly?

Z
zLeoZiin
Senior Member
503
09-19-2020, 08:47 PM
#1
I’ll keep it brief while sharing all the specifics. My setup uses an AM4 motherboard with the B550 chipset, AMD Ryzen 5900X processor, and a variety of components including an AORUS ELITE AX V2 graphics card, Corsair LPX Vengeance DDR4 RAM, and NVMe drives from Corsair, Kingston, and Toshiba. The system runs Windows 10 Pro 22H2. Everything seemed normal until a recurring freezing issue started after the spinning mouse circle—often during web browsing or when launching unexpected programs. Once it froze, the whole PC would shut down completely, then restart after about a minute. Initially it happened occasionally, but more frequently over time. At some point, BSODs appeared sporadically, then became more common about three to four months ago. I’ve tried removing and reinstalling Windows several times, clearing CMOS, updating BIOS, swapping RAM, and running memory tests with tools like Memtest86 and Windows Diagnostics. Even after replacing the HDD and NVMe drives, the problem persisted. The crashes were most common when Windows booted up—during the BIOS menu, the welcome screen, or right after startup. Sometimes they triggered during software installations or when opening programs. I’ve collected dump files from two periods: one before removing the 250GB NVMe drive and another after reinstalling Windows on the 500GB NVMe. These logs are attached for reference. Despite these efforts, I’m still unsure what’s causing it and am considering a repair shop as a last resort.
Z
zLeoZiin
09-19-2020, 08:47 PM #1

I’ll keep it brief while sharing all the specifics. My setup uses an AM4 motherboard with the B550 chipset, AMD Ryzen 5900X processor, and a variety of components including an AORUS ELITE AX V2 graphics card, Corsair LPX Vengeance DDR4 RAM, and NVMe drives from Corsair, Kingston, and Toshiba. The system runs Windows 10 Pro 22H2. Everything seemed normal until a recurring freezing issue started after the spinning mouse circle—often during web browsing or when launching unexpected programs. Once it froze, the whole PC would shut down completely, then restart after about a minute. Initially it happened occasionally, but more frequently over time. At some point, BSODs appeared sporadically, then became more common about three to four months ago. I’ve tried removing and reinstalling Windows several times, clearing CMOS, updating BIOS, swapping RAM, and running memory tests with tools like Memtest86 and Windows Diagnostics. Even after replacing the HDD and NVMe drives, the problem persisted. The crashes were most common when Windows booted up—during the BIOS menu, the welcome screen, or right after startup. Sometimes they triggered during software installations or when opening programs. I’ve collected dump files from two periods: one before removing the 250GB NVMe drive and another after reinstalling Windows on the 500GB NVMe. These logs are attached for reference. Despite these efforts, I’m still unsure what’s causing it and am considering a repair shop as a last resort.

T
Tuetme
Senior Member
418
09-28-2020, 04:06 PM
#2
It seems memory traces in the dump files are involved. RAM isn't always required, but it's typically the main focus. Windows moves low-priority RAM data to the page file and retrieves it when needed, making storage appear like memory. The memory controller is built into the CPU, and a failure here would make it seem like memory is missing. Storage-related issues usually show up in about half of the dumps as storage or storage drivers, which isn't present here, so storage is unlikely the cause. You've tried different drives; if any are overclocked or under-voltaged, remove them. Also, disable automatic overclocking features like Precision Boost Overdrive (PBO). To check RAM, run the machine normally with one stick at a time, using the second slot for the CPU socket. If only one stick causes crashes, the problem is likely in the CPU. Memory testers often miss faulty RAM, especially with DDR4 and newer types, so this method is more reliable.
T
Tuetme
09-28-2020, 04:06 PM #2

It seems memory traces in the dump files are involved. RAM isn't always required, but it's typically the main focus. Windows moves low-priority RAM data to the page file and retrieves it when needed, making storage appear like memory. The memory controller is built into the CPU, and a failure here would make it seem like memory is missing. Storage-related issues usually show up in about half of the dumps as storage or storage drivers, which isn't present here, so storage is unlikely the cause. You've tried different drives; if any are overclocked or under-voltaged, remove them. Also, disable automatic overclocking features like Precision Boost Overdrive (PBO). To check RAM, run the machine normally with one stick at a time, using the second slot for the CPU socket. If only one stick causes crashes, the problem is likely in the CPU. Memory testers often miss faulty RAM, especially with DDR4 and newer types, so this method is more reliable.

R
Randmfrogman
Member
116
09-30-2020, 09:21 AM
#3
Heya, thanks for looking into it. I'm also leaning more and more towards it being RAM but it's just all over the place so I can't conclude it. Nothing is OC'd on the PC except the XMP being on from the PC's assembly to the first Windows reinstallation about 2 months ago. Now it's currently off and there's still sporadic BSODs. But the GPU MIGHT be pre-OC'd which I can't confirm since all the sellers of this specific one just had "OC" in its description. I already both swapped the sticks to different DIMM slots and used them separately one at a time in the A2 channel, there were still BSODs. I can check this method out again later. Right now I was trying to do a Sysnative file collection and it BSOD with PAGE_FAULT_IN_NONPAGED_AREA, so after backing up my stuff for worst case scenarios I'll do some more Memtests and see if anything comes up this time. Other than that, what I'd like to is have an additional RAM set to try the system with but I don't have one available so if every error is pointing straight to the RAM I might as well just RMA it and hope for the best they're the actual culprit.
R
Randmfrogman
09-30-2020, 09:21 AM #3

Heya, thanks for looking into it. I'm also leaning more and more towards it being RAM but it's just all over the place so I can't conclude it. Nothing is OC'd on the PC except the XMP being on from the PC's assembly to the first Windows reinstallation about 2 months ago. Now it's currently off and there's still sporadic BSODs. But the GPU MIGHT be pre-OC'd which I can't confirm since all the sellers of this specific one just had "OC" in its description. I already both swapped the sticks to different DIMM slots and used them separately one at a time in the A2 channel, there were still BSODs. I can check this method out again later. Right now I was trying to do a Sysnative file collection and it BSOD with PAGE_FAULT_IN_NONPAGED_AREA, so after backing up my stuff for worst case scenarios I'll do some more Memtests and see if anything comes up this time. Other than that, what I'd like to is have an additional RAM set to try the system with but I don't have one available so if every error is pointing straight to the RAM I might as well just RMA it and hope for the best they're the actual culprit.