• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

What is your max infinity fabric on ryzen 5000? September 2021 edition

What is your max stable ram speed/infinity fabric?

  • 3666/1833 or lower

    Votes: 29 16.9%
  • 3733/1866

    Votes: 32 18.6%
  • 3800/1900

    Votes: 62 36.0%
  • 3866/1933

    Votes: 7 4.1%
  • 3933/1966

    Votes: 5 2.9%
  • 4000/2000

    Votes: 25 14.5%
  • 4066/2033

    Votes: 2 1.2%
  • 4133/2066

    Votes: 3 1.7%
  • 4200/2100 or above

    Votes: 7 4.1%

  • Total voters
    172
Decided to start tinkering a bit with RAM speeds on my main rig yesterday, after running it at straight DOCP settings since building it. ASRock B550 Phantom Gaming ITX-AX, 2x16GB G.Skill FlareX (dual rank B-die, B1 PCB, 3200c14), 5800X.

I don't know crap about RAM OCing, so for now I've
a) tried 1usmus' DRAM calc, which failed to POST even at 3600 safe (not really that strange given that it doesn't actually support Zen3 or B550), and
b) set everything to auto except the RAM and IF speed to see how high I could go.

The latter experiment was reasonably successful, though of course the timings are utter garbage - that's the next step, trying to get my head around which timings to tweak and which numbers are bad/acceptable/good. Hit 3800/1900 @ 1.2V, 4000/2000 @ 1.35V. 4066/2033 seemed to POST successfully once (got into the BIOS), but mostly just reset to safe settings by itself. 4000/2000 booted into Windows with no issues, did not show any WHEA errors, and was stable through a quick run of the Fire Strike CPU test, which is reasonably memory intensive. Didn't bother trying higher DRAM voltages, and it seems like people are recommending auto SoC voltage for Zen3, instead adjusting LLC? That's what I did, auto voltages (except DRAM) and level 3 SoC LLC.
Obviously haven't run any benchmarks yet as there's no point at these garbage timings, but at least I know my RAM and IF can both run faster than 3200 - though I don't know if they can do so at reasonable latencies and voltages. Just to reiterate: everything below except MCLK and FCLK is auto.

View attachment 222561
Edit: damn, looking at how much I paid for this kit vs. how cheap I can get a DDR4-4000c17/c18 kit today makes me a bit sad. Nearly 33% less!
If you wanna stay at 1.35V try the following: 18 18 18 18 36 54, tRFC 320, tCWL 18 tWR 18, tRTP 9, tRRDS 4, tRRDL 6, tFAW 16, twtrs 4, twtrl 12, scl 4, set vddp volt to 900, addrcmddrvstr 20. You may need a bit more volt on ram, maybe 1.38V.

If you want to unleashe more performance try 1.4-1.45V ramvolt, disable gdm, set 2T, 17 17 17 17 34 51 tRFC 304, tCWL 16, WR 16, tRTP 8.
 
If you wanna stay at 1.35V try the following: 18 18 18 18 36 54, tRFC 320, tCWL 18 tWR 18, tRTP 9, tRRDS 4, tRRDL 6, tFAW 16, twtrs 4, twtrl 12, scl 4, set vddp volt to 900, addrcmddrvstr 20. You may need a bit more volt on ram, maybe 1.38V.

If you want to unleashe more performance try 1.4-1.45V ramvolt, disable gdm, set 2T, 17 17 17 17 34 51 tRFC 304, tCWL 16, WR 16, tRTP 8.
Thanks, I might give that a try :)

If you wanna stay at 1.35V try the following: 18 18 18 18 36 54, tRFC 320, tCWL 18 tWR 18, tRTP 9, tRRDS 4, tRRDL 6, tFAW 16, twtrs 4, twtrl 12, scl 4, set vddp volt to 900, addrcmddrvstr 20. You may need a bit more volt on ram, maybe 1.38V.

If you want to unleashe more performance try 1.4-1.45V ramvolt, disable gdm, set 2T, 17 17 17 17 34 51 tRFC 304, tCWL 16, WR 16, tRTP 8.
Well, that was simple enough.
ZenTimings_Screenshot_27255975,9058631.png
 
My Zen timings, definitely interested in what the community thinks about improving these settings. TY :toast:
zentimings5950x1.jpg
 
Did a quick performance test, and the bump from DOCP 3200c14/1600 to 4000c18/2000 netted me a ~800 point/6.8% increase in the Time Spy CPU benchmark (for reference, the 4000c28 run yesterday delivered the same performance or a very tiny regression). Not bad for a couple of minutes of tweaking!
 
Thanks, I might give that a try :)


Well, that was simple enough.
View attachment 222627
Forgot that gdm makes rtp even. Try tWR 16, tRTP 8 :)

Did a quick performance test, and the bump from DOCP 3200c14/1600 to 4000c18/2000 netted me a ~800 point/6.8% increase in the Time Spy CPU benchmark (for reference, the 4000c28 run yesterday delivered the same performance or a very tiny regression). Not bad for a couple of minutes of tweaking!
Try the cl17 suggestion, I bet you can get another 2% there :)

My Zen timings, definitely interested in what the community thinks about improving these settings. TY :toast:
View attachment 222628
Set ram volt to 1.45V, try 14 14 14 14 28 42, trrds 4, trrdl 6, tfaw 16, twr 12, trtp 6, tRFC 256, twtrs 4, twtrl 8, tcwl 14, scls 4, rest auto.

If you can run 3800/1900 we can go further :)
 
Forgot that gdm makes rtp even. Try tWR 16, tRTP 8 :)


Try the cl17 suggestion, I bet you can get another 2% there :)


Set ram volt to 1.45V, try 14 14 14 14 28 42, trrds 4, trrdl 6, tfaw 16, twr 12, trtp 6, tRFC 256, twtrs 4, twtrl 8, tcwl 14, scls 4, rest auto.

If you can run 3800/1900 we can go further :)
Does GDM make CL even as well? CL17 was set to 18 on boot. Otherwise it booted fine at 1.38V. +100 points on TS CPU, so no major change there. Edit: or, well, it's another 1.1%, so not nothing I guess :)

ZenTimings_Screenshot_27256025,9021319.png
 
Last edited:
Does GDM make CL even as well? CL17 was set to 18 on boot. Otherwise it booted fine at 1.38V. +100 points on TS CPU, so no major change there. Edit: or, well, it's another 1.1%, so not nothing I guess :)

View attachment 222635
Yeah, gdm makes cl, cwl, wr and rtp even. Try 2T and turn off gdm, it is slightly faster but can possibly be a bit more unstable.
 
I like how you lot all have your favourite timings, like TRFC under a thousand :P

1635369678460.png



Just that reminder that not everyone has samsung B-die, and these different timings and voltages can easily lead to fruit loops
 
I like how you lot all have your favourite timings, like TRFC under a thousand :p

Just that reminder that not everyone has samsung B-die, and these different timings and voltages can easily lead to fruit loops

Not having B-die doesn't mean there's no room for improvement......they can't do the same primaries and secondaries but lots of ICs can cut down on tRC, tRFC, tRTP etc. for a very real improvement. Not even MJR should have to be saddled with 550ns tRFC...unless you got impossibly unlucky with silicon quality or freak compatibility issues.

Reous tRFC list v21.png
 
I like how you lot all have your favourite timings, like TRFC under a thousand :p

View attachment 222648


Just that reminder that not everyone has samsung B-die, and these different timings and voltages can easily lead to fruit loops
Is that a 2*32GB kit? I'm frankly impressed that it runs at 3800 at all. I consciously went for one of the few DR B-die 2*16GB kits I could find at a reasonable price, choosing a low spec (3200c14) for that rather than gambling on some other die at something like 3600. Apparently it worked out well for me!
 
Is that a 2*32GB kit? I'm frankly impressed that it runs at 3800 at all. I consciously went for one of the few DR B-die 2*16GB kits I could find at a reasonable price, choosing a low spec (3200c14) for that rather than gambling on some other die at something like 3600. Apparently it worked out well for me!

Sounds like it turned out well!

I'm going to give these settings a try this evening. I have the same RAM as you, but in a 4*8GB kit.
 
Is that a 2*32GB kit? I'm frankly impressed that it runs at 3800 at all. I consciously went for one of the few DR B-die 2*16GB kits I could find at a reasonable price, choosing a low spec (3200c14) for that rather than gambling on some other die at something like 3600. Apparently it worked out well for me!

Have you got around to testing yet? Might be worth it to run a quick sfc /scannow and DISM /Online /Cleanup-Image /CheckHealth before you start, get a clean slate assuming CO is stable.
 
I do not like to be in the bleeding edge.
8WAoR7Y.png
 
I like that chart! Looks like it could come in handy..
 
I like that chart! Looks like it could come in handy..

The Reous tRFC chart is a great resource. Just take it as a general range recommendation to start for tRFC. Obviously it doesn't go low enough for B-die, but at that point you don't need the chart :laugh:
 
I cant go beyond 1866, but i dont know if my RAM is the issue.
I can't go above 1600, but my 4 dual rank sticks of Samsung C-die are certainly my issue.
 
Is that a 2*32GB kit? I'm frankly impressed that it runs at 3800 at all. I consciously went for one of the few DR B-die 2*16GB kits I could find at a reasonable price, choosing a low spec (3200c14) for that rather than gambling on some other die at something like 3600. Apparently it worked out well for me!
Yeah, 2x32GB

It runs 4000 fine as well, it's my IF that cant keep up
 
I like how you lot all have your favourite timings, like TRFC under a thousand :p

View attachment 222648


Just that reminder that not everyone has samsung B-die, and these different timings and voltages can easily lead to fruit loops
Didn't you have Hynix DJR? An avg DJR kit can do 460 at 4000 or 429 at 3733. Depending on bin, anything from 400 to 480 at 3733 should be doable :)
 
Didn't you have Hynix DJR? An avg DJR kit can do 460 at 4000 or 429 at 3733. Depending on bin, anything from 400 to 480 at 3733 should be doable :)

2x32GB can't be DJR? :confused: Can't get 32GB density out of a 8Gb IC. MJR is 16Gb.
 
Didn't you have Hynix DJR? An avg DJR kit can do 460 at 4000 or 429 at 3733. Depending on bin, anything from 400 to 480 at 3733 should be doable :)
2x32GB MJR (i have to run thaiphoon any time someone asks, i can never remember)
 
2x32GB can't be DJR? :confused: Can't get 32GB density out of a 8Gb IC. MJR is 16Gb.
Ah, sorry, didn't remember specs of DJR ;) Most experienced on B-die and rev E.
 
2x32GB MJR (i have to run thaiphoon any time someone asks, i can never remember)
So according to the table it should do ~665 tRFC?
 
2x32GB MJR (i have to run thaiphoon any time someone asks, i can never remember)
Ah, okay, the anywhere from 640 to 690 should be doable on 3800. Lowering from over 1000 can give high gains. The major difference between Samsung B-die and all other ram is the ability to run low tRFC, which is the timing that usually impacts gamingperformance the most. B-die can also run tRCDRD and tRC lower, but not by a huge amount and they don't impact gaming that much.

This is how much tRFC do to gaming:
1635403133812.png

The bottom Tridentkit runs tRFC at 560, the 2 others 416. Lowering tRFC by 144 increases fps by 5.8%/19.5% min. Going from 16 18 18 36 to 14 14 14 34 only increase fps by 2.7%, but affects mins quite much.

My rev E could run tRFC at 528 at 3733 (good bin), my B-die can do 254. In certain games this could give performancegains of almost 10%, but the rev E compensated somewhat since it could run tRP, tWTRS and tWTRL lower than B-die. Actual performancedifference is around 5-6% when max-tuned.

I do not like to be in the bleeding edge.
8WAoR7Y.png
Is that your highest stable/bootable IF? Micron rev E or B ram? tWR equal to tCL and tRTP half of tWR should work and improve performance :) tRFC 560 might be doable, maybe lower, my rev E can do 522 at 3733.
 
Have you got around to testing yet? Might be worth it to run a quick sfc /scannow and DISM /Online /Cleanup-Image /CheckHealth before you start, get a clean slate assuming CO is stable.
Any recommendations for stability testing? sfc /scannow returned two corrupted files (both links to the Onedrive app, which ... okay?), all fixed. Nothing from DISM. Haven't used the PC much since I tuned things yesterday, but it did fine through some online gaming (Rocket League, in my experience can show memory instability as network errors/latency variation/connectivity issues when playing), plus it woke up from sleep this morning record fast. Still at zero WHEA errors, and everything seems to work fine.

Also, question: I set my vSOC to 1.2V, it's reading as 1,169V stable/peak with drops to 1,156V in HWinfo64. Am I right in thinking this is safe long term? And should I still try stepping it down some?

Yeah, gdm makes cl, cwl, wr and rtp even. Try 2T and turn off gdm, it is slightly faster but can possibly be a bit more unstable.
Welp, that did something. 12172 TS CPU score, that's another +300 points! Currently up 10.7% from my baseline score (10991). Not bad! No WHEA errors, but obviously need stability testing. Should I aim for lowering my tRFC towards the timings from the table (~280)?
 
Any recommendations for stability testing? sfc /scannow returned two corrupted files (both links to the Onedrive app, which ... okay?), all fixed. Nothing from DISM. Haven't used the PC much since I tuned things yesterday, but it did fine through some online gaming (Rocket League, in my experience can show memory instability as network errors/latency variation/connectivity issues when playing), plus it woke up from sleep this morning record fast. Still at zero WHEA errors, and everything seems to work fine.

Also, question: I set my vSOC to 1.2V, it's reading as 1,169V stable/peak with drops to 1,156V in HWinfo64. Am I right in thinking this is safe long term? And should I still try stepping it down some?
Download TestMem5 and run it with the usmus config for 20 rounds. Karhu also works, but costs about 10usd. Too low tRFC can sometimes lead to file corruption, but yours isn`t that low.
 
Back
Top