The XMP profile triggered my sadness but I resolved it. What led to this situation?
The XMP profile triggered my sadness but I resolved it. What led to this situation?
I realized the problem after figuring it out in the title. Several programs would stop unexpectedly without clear cause. I looked at other forums and found that running OCCT might help with power supply issues. Initially, the program crashed within a minute after a power test. I then checked CPU and memory usage, which showed over 60,000 and about 15,000 respectively. After restarting and disabling the XMP profile in BIOS, OCCT ran smoothly. I tried overclocking the CPU again but kept XMP enabled, and everything worked fine. The order of operations mattered—CPU had to run longer than memory. I’m curious about why turning XMP back on changed things, since I expected the same problem again. Hope this gives some insight to others.
First off, what is the XMP profile you're trying to enable, what CPU are you using, and what motherboard are you trying to use? There's a non-zero chance that you're just seeing retrain instability which is a thing on 11th Gen and newer Intel CPUs, where you can pass memory stress tests for 48 hours straight, reboot the system and you have an error within 10 minutes. This doesn't show up until you're usually at or near the limits of your CPU/motherboard/memory (4400+ on DDR4 with 11-13th gen, 6200+ on 12th gen depending on the board, and 7000+ on 13th gen depending on the board), but it is a thing nonetheless and the most annoying thing about working with modern Intel CPUs.
The BIOS profile for XMP is set as Profile 1 with the name XMP-DDR4-16-20-20-40-60-1.35V. The RAM speed is configured at 3200 MHz. The CPU model is Ryzen 9 3900X and the motherboard is B550M Aorus Elite. I'm running the tests again in OCCT, this time letting the default 30-minute test complete to observe the results.
This seems quite unusual. It probably stemmed from a BIOS glitch, preventing the system from properly applying memory voltage.
I reran all the tests and everything looks normal again. I still find it odd that it started this way, but I'm relieved it's probably just a BIOS problem. Thanks for your time—I really appreciate it!