Issue with A-XMP instability due to incorrect memory slots
Issue with A-XMP instability due to incorrect memory slots
Hello, I recently assembled a new PC with the following components: AMD 5600x, MSI MAG B550 Tomahawk Max Wi-Fi, 2x16GB Corsair Vengeance Pro RGB SL 3600MHz, Sapphire Pulse RX 5600xt, and Corsair RM750 power supply. I’m facing issues activating A-XMP profiles on my motherboard to unlock full RAM speeds and low latency. Whenever I turn on the A-XMP setting in BIOS, the system will occasionally crash with a blue screen and display a colorful rainbow before shutting down. This behavior isn’t consistent—sometimes it happens after booting into Windows, other times not at all. Anyone know what could be causing this problem?
Technically that is an overclock. Your ram/memory controller are not fully stable at that speed which is why it is throwing errors. Try setting the XMP timings and voltage manually in BiOS. For whatever reason, that seems to work better on AMD systems than choosing the XMP option. You can also start at 3200mhz and then go up in speed from there to find the highest stable speed. If you don’t know your RAM timings, you can use hwinfo to see the specs of the sticks.
I refreshed the BIOS prior to setting up any kind of operating system during assembly.
You're currently using a 5600X with 3200GT/s memory and have been satisfied so far. It's unclear if switching to 3600 would noticeably change performance. Consider testing your memory sticks individually to check for instability or issues with the memory controller in the processor. Try running tests with one stick at a time and different DIMM slots. If problems persist, use tools like Memtest86 to identify memory errors. If the issue remains, it might be due to faulty memory. Running at standard speeds (around 2600MT/s) could help confirm if overclocking is the cause. It may also point to motherboard or CPU problems. A better approach would be swapping parts with a known working system to isolate the faulty component. However, not everyone has access to multiple computers for such tests.
I attempted to run each memory stick separately in various slots, then used cinebench to apply any load and monitor progress. Initially, the issue didn’t appear with a single stick. Once the suspected faulty one was inserted, the problem disappeared. After reconfiguring the sticks back to their original setup, the issue no longer occurs. It seems the problem has been resolved.
The evidence suggests a RAM module wasn’t properly installed. This can occur due to shaking, debris, or temperature changes in the system. The positive side is that your device should function normally for some time now after the replacement.