Forcing Ripjaws V 2x8 GB 3200 to work at full speed in Prime B350-Plus from Asus

RBuczynski

Reputable
Apr 4, 2016
64
2
4,565
Hello.
As the title says - today I've got my hands on freshly AMD bundle, which contains:
Ryzen 5 2400G with non-stock cooler (might as well chance fortis3 from silentiumPC to something more powerful)
2x8 GB DDR4 G.Skill Ripjaws V 3200MHz (16-18-18-38@1.35V)
Asus Prime B350 Plus
GF GTX 750 2GB (I know it's bottlenecking, but without buying 4K screen I don't see a reason to spend ton of money for non-bottle card like 1060Ti 6GB)

Anyway - trouble is simple. I cannot force these rams to work at full speed (3200 they say, it will be fun they say). Bios detects them at 2133 (so slow, God damn it!), but any attempts to push it to 3200 gives boot and no post. I've tried to set it auto via DOCP (it even detects, that it can work as fast as 3200, just need a boost to voltage to 1.35V), but after saving and restart, only black screen appears and I need to reset UEFI to get my pc back to operational form.

I've know, that 2x8 GB ARE NOT listed in latest QVL. But, for some reason - duo or quad form of IDENTICAL (almost?) rams (also G.Skill Ripjaws V 3200 with part number exactly the same, as mine (mine is F4-3200C16D-16VKB, they've listed F4-3200C16D-8GVKB and some other, named F4-3200C14Q-32GFX, which is quad of 8GB each) seems to work.

Is there anything I could do, beside updating the UEFI/BIOS (which I'm gonna do right now, from the version dated back to Sep. 17)?
 
Solution
What timings should I relax? Only the main (main - for/five most basic timings), all of them by 1
I would start by looking at what jedec speeds CPUid gives (with associated timings and voltages) and see if you can get better than 2133 at first. Aim for 2666 as a minimum, and 2933 as ideal. 3200 might not be achievable with Ryzen.



I'm tired of this s..t now).

Welcome to the club. 😀
I've noticed, that there's one option (tCCD_l), which is in XMP for 2133 MHz, but NOT for 3200.
What's more - I cannot change it manually (there's no option in updated uefi/bios).
I'll try to set more relaxed (everything was on auto) timings, when I'll be fresh (bed is calling me badly).
What timings should I relax? Only the main (main - for/five most basic timings), all of them by 1, try something different?
I've also found a clue, that it might be the case to increase slightly some other voltage (soc I think, but not sure - don't want to look anymore today, I've got enough of this for one day, and still have to install crap called Win10 :| ).

Onboard GFX is 99% surely disabled (as mentioned before - I'll check it when I get up, I'm tired of this s..t now).
 
What timings should I relax? Only the main (main - for/five most basic timings), all of them by 1
I would start by looking at what jedec speeds CPUid gives (with associated timings and voltages) and see if you can get better than 2133 at first. Aim for 2666 as a minimum, and 2933 as ideal. 3200 might not be achievable with Ryzen.



I'm tired of this s..t now).

Welcome to the club. 😀
 
Solution
Jedec says only about 2133 and 3200. Nothing in between. I've decided to set AI Overclock Tuner to DOCP mode, but memory freq to 2666 with timings set to 3200. Also - increased voltage to 1.35V.
But - I still cannot change any other timings from DDR4 different than CAS#, trcdrd, trcdwr, RAS# pre tmime and RAS# act time (respectively 16-18-18-18-38).
2666 posted, I'm trying to push it to the limit baby.
 
OMG. Either they I've REALLY do something with this microcode, or I was so tired last night, that I didn't even discovered it.
Sor some reason, setting all the way from 2133 to 3200 at once was fail.
BUT - setting it one to one, starting from 2666 freq, with saving and exit...worked. Stopped succesfully at 3200 MHz (it posted so far, without system I don't know how to test it different that mem(e)test).
So it was a tempest in a teacup (if that's how you call your idioms, not sure 😀) for getting s..t ram, that is NOT actually shit at all.
I'll test is harder once I put win10 to use and we will see, if it stays that way (hopefully so).

Thank You kindly Sir for helping.