X370 Killer BIOS 2.3 + DDR 2999 issues

I have the X370 Killer, Ryzen 1600X, and Team Group's Vulcan 3000 RAM.  The issue I keep running across is I cannot get my RAM to run any higher than DDR 2400.  If I use the XMP profile or set it manually with the 1.35 voltage I get 5 boot attempts then defaulted to 2133.

By chance has anyone successfully managed to get this or similar Hynix based RAM to pass 2400 stable or should I look at getting different RAM?

Thanks

My Corsair Vengeance worked at 2933 from day one. The only settings I've changed were:

OC Tweaker:
Dram Frequency: DDR4 2933

Advanced\CPU Configuration:
C6 Mode: Disabled

Advanced\AMD CBS\Zen Common Options:
Global C-state Control: Disabled

Security:
Secure Boot Disabled

Most of these settings are for my OC profile from when I tested my CPU to see where I stood in the lottery.

Even without any of the chanyes I just selected 2933 from the DRAM drop down and it worked.



Edited by AlbinoRhino - 26 May 2017 at 9:08pm

Mike K wrote: I was also able to lower all my memory voltages back to recommended, with a tiny push to SOC voltage from .08 to .10 to get everything stable at 16-16-16-34 timings.

without any malice (and indeed it did chuckle to myself)

but your one of the few guys to state a 25% increase to be 'tiny'
would 25% increase in your tax bill still be tiny ?

in context though 1.0 volts is still a small voltage for the SOC

i just chuckled at the phrase tiny

Ryzen does not support the memory "divider" for a memory speed of 3000.

Do you see a memory speed of 3000 in the manual memory speed list in the UEFI/BIOS? DDR4 3000 is not listed in the memory specifications as a possible memory OC.

The Memory Support list for your board should have an entry similar to this from my ASRock X370 board:

Each RAM whose frequency is 3000 will downgrade to 2933 with X370 Killer SLI/ac

The closest you can get is 2933.

Xaltar wrote: <span style=": rgb43, 43, 43;">ProcODT</span>?manually set to 53.3 ohm on my Taichi seems to have improved stability and allowed me to get 3466 to work on my 3600 kit. I will test further but when I saved changes in the UEFI and rebooted the system booted right up, no pre training or cycling... That is the first time I have seen that happen so thanks to whoever mentioned?<span style=": rgb43, 43, 43;">ProcODT</span>?first, I am not sure if it was this thread or another that put me onto it but so far I think it may have sorted some of my issues? We are learning all this stuff right along with you guys so thank you all for sharing?

Yeah, I went into overclocking this system with the mindset of how it was done on the previous platform ( I never seriously worked with an Intel based system so I'm not sure how its options compare to what I am familiar with )

I quickly realized everything I knew was now out the window

ProcODT is still sort of a mystery to me, from what I have been able to dig up is the higher OHM settings require more cooling ( As an amateur electrician it makes sense - Higher OHM's mean more resistance which would be more heat generated ) But when it comes to overclocking there is just so little information to be found about how exactly this setting changes things, what it changes, and why specific settings can make memory work better or worse...

I have had to scale back my Overclock personally because after updating to the newest 2.50 Agesa 1.0.0.6 (From BIOS 2.20) my motherboard (X370 K4) went from running a stable 4.0 with my memory being able to use the XMP profile, to only able to hit 3.875 CPU and Memory at 2666.

I have not had a ton of time to keep tweaking it but as you said I only could get my memory off of default timings by setting ProcODT to 53.3 as well (I had to bump it up from the setting of 40 that had worked previously)

Well anyway, Glad to hear your getting better performance from your system.
Let me know if you come across any other tidbits of juicy info or personal experiences.