F5F Stay Refreshed Hardware Desktop Seeking assistance with Corsair Vengeance RGB Pro overclocking?

Seeking assistance with Corsair Vengeance RGB Pro overclocking?

Seeking assistance with Corsair Vengeance RGB Pro overclocking?

Pages (2): Previous 1 2
J
javiberni
Member
85
12-08-2021, 05:04 PM
#11
This argument isn't helping much. I've changed the voltage to 1.4 and tried both clock speeds—3400 and 3600. I left the voltage on auto and didn't set it manually, but my system would reset after a few reboots. The only difference was that using 3400 on auto stopped the system from starting at all, forcing a CMOS reset. I could share a screenshot of Thaiphoon Burner if you'd like, but your device doesn't launch anymore. It's really frustrating right now.
J
javiberni
12-08-2021, 05:04 PM #11

This argument isn't helping much. I've changed the voltage to 1.4 and tried both clock speeds—3400 and 3600. I left the voltage on auto and didn't set it manually, but my system would reset after a few reboots. The only difference was that using 3400 on auto stopped the system from starting at all, forcing a CMOS reset. I could share a screenshot of Thaiphoon Burner if you'd like, but your device doesn't launch anymore. It's really frustrating right now.

E
EnderStellan
Junior Member
26
12-09-2021, 12:47 AM
#12
The Ryzen memory controller in even the third generation is quite problematic. If you're seeing 3200 MHz, that's a decent result, but the issue lies in the controller itself—it won't last. It resets after reboots because the RAM training failed and it falls back to default settings. On the first generation, I had to boost the SoC and DRAM voltage to reach 3200 MHz, though it never stayed stable.
E
EnderStellan
12-09-2021, 12:47 AM #12

The Ryzen memory controller in even the third generation is quite problematic. If you're seeing 3200 MHz, that's a decent result, but the issue lies in the controller itself—it won't last. It resets after reboots because the RAM training failed and it falls back to default settings. On the first generation, I had to boost the SoC and DRAM voltage to reach 3200 MHz, though it never stayed stable.

J
justfyre
Junior Member
37
12-09-2021, 04:40 AM
#13
there's no chance it's b-die, and knowing corsair's crappy tolerance on a bin getting them to boot at stock is already a minor win. don't bother if you are running 4 sticks. Try 16-19-19-39 and pick an everyday voltage you can tolerate (1.45v? just a recommendation) and go as high as you can on the frequency, then it's trial and error time 1.65v won't kill ur ram but i absolutely would not run it everyday even if u can keep temps under 50C load
J
justfyre
12-09-2021, 04:40 AM #13

there's no chance it's b-die, and knowing corsair's crappy tolerance on a bin getting them to boot at stock is already a minor win. don't bother if you are running 4 sticks. Try 16-19-19-39 and pick an everyday voltage you can tolerate (1.45v? just a recommendation) and go as high as you can on the frequency, then it's trial and error time 1.65v won't kill ur ram but i absolutely would not run it everyday even if u can keep temps under 50C load

T
thehappy84
Senior Member
594
12-09-2021, 07:07 AM
#14
It's actually a B-die situation. Research on Version 4.32 shows several forums confirm this. It might work with both higher voltage and looser timing, but I’d start with Gear Down off and try the 17-17-17-35 2T setting to see if it hits 3600mhz at 1.40v or below. Some B-Die kits handle this oddly with good latency. Just don’t ask me why—I know from experience it’s a known pattern.
T
thehappy84
12-09-2021, 07:07 AM #14

It's actually a B-die situation. Research on Version 4.32 shows several forums confirm this. It might work with both higher voltage and looser timing, but I’d start with Gear Down off and try the 17-17-17-35 2T setting to see if it hits 3600mhz at 1.40v or below. Some B-Die kits handle this oddly with good latency. Just don’t ask me why—I know from experience it’s a known pattern.

Pages (2): Previous 1 2