Help with getting RAM stable

Soldato
Joined
15 Feb 2009
Posts
4,298
Location
Bristol
Hi all,

I'm trying to get my Team Group Xtreem 16GB 4000MHz C18 stable.

Gigabyte Aorus Pro
Ryzen 2600

I know the MSI are supposed to have better VRMs but I'm currently trying to find a stable 3200MHz setting.

I did have it on 3333MHz 14-14-15-14 which seemed stable but some more MEMtests showed that it was not.

I used the 3200MHz SAFE settings straight out of the Ryzen DRAM Calculator, but getting BSOD at 1.35v.
1.36v and 1.37v no BSOD but errors in MEMtest.

Currently trying 1.38v, but I shouldn't need it this high for 3200MHz?

My CPU settings are currently all on auto as I don't do anything intensive so fine for my needs, can I leave this on auto, or do I need to go to manual if I ultimately want 3400-3600MHz? And would 3200C14 be better or 3400C15/3600C16 for Ryzen?

I'm on AGESA 1.0.0.4 at the moment, would updating to the latest version help with stability? Or should I just leave that alone?

Thanks for any help.
 
The issue will be the IMC on your Ryzen 2600.

I would suggest upgrading to the latest BIOS yes. It cant hurt.

With that CPU I wouldn't go over 3200MHz to be honest. Try and find stability at that speed.
 
Last edited:
Ah, ok. That's a shame. I MEMtested with 1.38v overnight but got 8 errors over the 7ish hours.
I went ahead and updated to the latest BIOS this morning. Just ran a test at 1.39v, got an error 14 minutes in. :(
Will try 1.4v now. Anything I could be doing wrong?
I have Core Performance Boost and Global C State Control on auto, and Cool 'n' Quiet enabled, but my CPU isn't overclocked, that should be ok left on?

At the moment my CPU Vcore and Vcore SOC is on auto, but in the BIOS, it's reading Vcore SOC at about 1.1v, so I shouldn't need to change this? I can't specify a value, just offset it.

Thanks.
 
Last edited:
Ah, ok. That's a shame. I MEMtested with 1.38v overnight but got 8 errors over the 7ish hours.
I went ahead and updated to the latest BIOS this morning. Just ran a test at 1.39v, got an error 14 minutes in. :(
Will try 1.4v now. Anything I could be doing wrong?
I have Core Performance Boost and Global C State Control on auto, and Cool 'n' Quiet enabled, but my CPU isn't overclocked, that should be ok left on?

At the moment my CPU Vcore and Vcore SOC is on auto, but in the BIOS, it's reading Vcore SOC at about 1.1v, so I shouldn't need to change this? I can't specify a value, just offset it.

Thanks.

Are you at 3200MHz?

It should only require 1.35v for the dram voltage @ 3200MHz.

Set your SOC voltage to 1.1v see if that helps.
 
Yeah 3200MHz. I ran a few passes of MEMtest at 1.4v, and it seems to be stable now. I'll run this overnight tonight to see if that kicks up anymore errors.
I checked in the Aorus SIV and Vcore SOC was reading between 1.104-1.116v.
DRAM voltage reading at 1.404-1.416v, so nothing funny happening there.
 
Yeah 3200MHz. I ran a few passes of MEMtest at 1.4v, and it seems to be stable now. I'll run this overnight tonight to see if that kicks up anymore errors.
I checked in the Aorus SIV and Vcore SOC was reading between 1.104-1.116v.
DRAM voltage reading at 1.404-1.416v, so nothing funny happening there.

No need to run it over night to be honest, I personally think that is excessive and unnecessary.

Download the Dram calculator and use the memtest functionality to test 400% coverage of the ram and about 80% of the ram that you have.
 
No need to run it over night to be honest, I personally think that is excessive and unnecessary.

Download the Dram calculator and use the memtest functionality to test 400% coverage of the ram and about 80% of the ram that you have.

Ok thanks. Yeah that's the program I use to test. I do it for all available memory.
I tried the FAST timings, but it didn't even post. I guess I'm stuck with 3200MHz, if I'm needing 1.4v to get it to even that.
Thanks for the help. Maybe when/if I ever upgrade the CPU I'll revisit trying to get higher speeds.
 
@Razor-BladE

Try lower SoC voltage, 0.9v (for 3200)
Also lower the RAM voltage to 1.365v
I have built two systems, one with the 4133MHz Xtreem and another with 8pack 3200 XMP, both are happy to run at the DRAM Calculator 3200 Fast settings, with exception of tRFC which needed setting to 307 (which just so happened to be the recommended in an older version of the calculator).
Leave the termination stuff etc all on auto, set Cmd2T to 1T and disable gear down.

I didn't have time to test the second system with a lower tRFC, but both systems were happy to run Karhu RAM Test for over 12 hours and over 20000%

Memtest86 is no good at finding OC memory errors to be honest.
Prime95 with large FFT 800k-800k
TM5 with 1usmus config
Karhu RAM Test (not free but will get an error quicker)

Though I've got some Micron Rev.E at the moment, 2x16GB dual rank, at 3400 with 0.95v SoC and 1.39v RAM, on my 2700X.

I wouldn't rule out the IMC on your 2600 yet...! The calculator suggests voltages too high for my chip. If I set SoC to 1.025v or 1.05v I get single errors after a few hours testing.
 
@Razor-BladE

Try lower SoC voltage, 0.9v (for 3200)
Also lower the RAM voltage to 1.365v

Thanks for the post Lad. I went into BIOS to test it and would you believe it, not only does my motherboard not allow for specified values, but it also doesn't even allow for a negative offset.
I only have a choice of Normal, Auto and offset up to +0.3. I tried it on Normal, but it was the same reading as Auto.

I guess that's that! :(
 
I had a quick Google and it would seem the Aorus Pro has negative voltage offset for CPU and SoC? Are you sure a toggle isn't appearing for - or + once choosing offset? Maybe you need a bios update.

If I were stuck with 1.1v SoC my 2700x wouldn't be happy to run 3400, or even 3200 on the IMC.
 
I had a quick Google and it would seem the Aorus Pro has negative voltage offset for CPU and SoC? Are you sure a toggle isn't appearing for - or + once choosing offset? Maybe you need a bios update.

If I were stuck with 1.1v SoC my 2700x wouldn't be happy to run 3400, or even 3200 on the IMC.

Can you link? I'm on the latest BIOS, and I just rechecked, there's no way to go to negative.
 
Back
Top Bottom