BSOD due to memory corruption
BSOD due to memory corruption
No modifications were applied to the system. The latest update involved a BIOS change from version 7D70v1E to 7D70v1G1 (skipping one version without prior problems). Following the update, the system ran smoothly after a restart and XMP 1 was enabled again. After more than six hours on the blue screen, I powered it off and restarted it in the morning. This time it worked, but it displayed a blue screen before any apps launched. I waited 15 minutes without restarting and then manually booted it. It showed the "Blue Screen" message briefly, then restarted itself instantly. Instead of asking for recovery mode, I chose to restart again, entered BIOS, turned off XMP, saved settings, and it posted successfully. After re-enabling XMP 1 and saving changes, it restarted after a 142.5-second BIOS cycle. The "New CPU installed" notice appeared briefly, likely due to the BIOS update rather than hardware changes. I suspect the memory context restore was set to auto, possibly because of timing issues from the update. The failure log indicated "MEMORY_CORRUPTION_ONE_BIT" and a memory dump is available. The machine’s specs match: 96GB Corsair Vengeance 6000MT/s CL30 2x48 drives, plus additional SSDs. It was built in November/December of the previous year.
That's an impressive tier build! It would be great if Origin could update the RAM support. Otherwise, consider running it at 5600MHz with AM5 and turning off MCR—some issues popped up on my system similar to what others reported. Ryzen Master didn’t launch there either.
Debugging from a single dump file may not be reliable. Are you sure there are minidumps in C:\Windows\Minidump? This appears to show memory usage. Memory isn't always RAM, but it's often what people think. Windows moves low-priority RAM data into the page file and retrieves it when needed, making storage seem like memory (and memory can mimic storage). The memory controller is part of the CPU, so a failure here will just display memory content. If there are any overclocking or undervolting issues, remove them—this includes the EXPO setting. AMD officially supports 5200MT/s with that CPU model. To verify RAM health, run the machine normally with one stick at a time. If only one stick causes crashes, the faulty stick is the problem.
A single minidump was generated. Earlier I experienced a BSOD due to a defective Nvidia Broadcast driver. After running a full MemTest86, the system reported zero errors. Since fixing the driver problem, I haven’t seen any BSODs until today after updating the BIOS and using the XMP profile continuously. It’s unclear whether overclocking, memory context restoration, or an unstable BIOS version with overlock are causing the issue. The only recent change was the BIOS update, which happened just before posting this thread (second time I powered on since the BIOS change). I haven’t performed a blue screen yet. Minidump link: https://ufile.io/gjmsdoba Previous BSOD (with MemTest86 results): Edited May 26, 2024 by Robertjr114
I went all-in last Black Friday, your setup is pretty close and should save you a lot of money though, right? So far turning off MCR seems to work, but I’m stuck dealing with slow startup times. I’m hoping for better stability in future updates. Right now I’m still running at 6000MT/s / XMP without any issues when MCR is off.