Considering Undervolting the CPU prior to overclocking RAM?
Considering Undervolting the CPU prior to overclocking RAM?
Hello,
XMP profile is causing instability in my system, so I’m considering adjusting voltage, frequency, and timings manually. However, I’ve heard that when planning overclocking both RAM and CPU, it’s best to first overclock the CPU—ensuring RAM is set to its default speed beforehand—and only then proceed with RAM overclocking once stability is confirmed. I’m unsure if this applies if I only want to lower the CPU voltage to reduce idle temperature. Should I begin by undervolting the CPU, or wait until the CPU is stable before moving on to RAM?
My system details:
CPU: AMD Ryzen 5 3600X
RAM: 2x8GB Corsair Vengeance LPX 3200MHz
Motherboard: Gigabyte B450 Aorus Elite (rev 1.0, BIOS F52)
GPU: EVGA GeForce RTX 2060
SSD: Samsung EVO 970 Plus 250GB
HDD: Western Digital Blue 2TB 5400 RPM
PSU: Corsair TX650M
Yes, you perform that to avoid risking RAM instability during CPU tuning tests. Reduce the factors involved.
Additionally, DRAM Calculator for Ryzen v1.7.3 is available for downloading.
It assists in optimizing memory timing for AMD Ryzen systems and enhances CCX efficiency.
1usmus has introduced ClockTuner, a tool designed to boost performance for AMD Ryzen 3000 CPUs and improve overall efficiency.
wccftech.com
I've noticed that adjusting the DRAM voltage manually makes my XMP profile more stable. It might be related to my motherboard, but it's worth testing if you're focused on getting XMP settings functioning properly. To go further, the DRAM Calculator is a useful resource for figuring out timings and voltages needed to optimize performance.
Despite offering the most accurate details possible, DRAM Calculator failed to provide suitable RAM timings for both FAST and SAFE modes. In fact, in the SAFE setting it returned even worse timings than what my RAM is set up for when overclocked. However, I discovered a forum discussion where another user faced the same problem and found a solution. The issue stemmed from an incorrect tRC timing value in the XMP profile, which prevented it from working. Adjusting that value resolved the matter, and Memtest86 ran successfully afterward.