r/Amd•
Concillian

OCing Micron E-Die -- A.K.A. Sub-timings matter a lot for Zen2.

Benchmark

TLDR: Skip to table at bottom of post

So this is my adventure with a kit of Micron E-die that was ~$80 including tax. This is a new 2x8GB kit of Ballistix Sport LT, purchased directly from Crucial on July 26, and I spent much of my spare time since receiving it testing out different settings and timings.

Motherboard is MSI x570 Gaming Plus (cheap end of x570 for sure). CPU is a 3600x. Windows 10 1903. BIOS is most recent, but based on AGESA 1.0.0.3A. Most recent chipset drivers were installed.

For the purposes of finding memory differences and keeping the CPU from boosting differently on different runs, I am running at 4.00 GHZ all core for the gaming benchmark (this made run to run results MUCH more consistent.) AIDA tests were at stock CPU boosting.

I'm very happy with how this 2x8GB kit overclocks. Initally, I worked on DDR4-3600 testing and achieved 14-19-16-36 at 1.41v. Didn't have any real success above 3600 until I moved to 2T command rate.
In ~20 years of OCing, I've never run 2T command rate, but decided to try it, and glad I did.

DDR4-3800 settled in at 15-20-17-38 2T @ 1.40v

tRCD (read) does not scale with voltage at all. You can basically just scale it in the time domain to the new speed and and it's always the same number in time domain. As a result the sticks at XMP of 3000 may end up with lower tRCD, but I don't know if they will do as well with frequency/voltage?

Then I dialed in subtimings... Here are screenshots of each with Ryzen Master so you can see all timing and AIDA benchmarks

3600 -- https://imgur.com/VXz5Z4l

3800 -- https://imgur.com/AyH4FGc

Both have been validated 3600% coverage with HCI memtest, even though only the 3800 screenshot shows it. 3600 validated at 1.41v, but I put it up to 1.42 for extra margin. (Added 0.01v to the 3800 in my BIOS profile after this screenshot for the same purpose)

AIDA was showing a substantial improvement for 3800 despite the 2T command rate, so I wanted to see how it would work in gaming. I always set up new computers in a spare case as a testbench to play around with before making them my primary computer, so this has my 3rd string Radeon HD7850 paired with the 3600x. Not much to test that isn't going to have a GPU bottleneck. But Shadow of the Tomb Raider has an output that tells you what the FPS would be if CPU limited... so I used that. Settings were 1080p very high, but with HBAO and Motion Blur off.

Average of multiple runs rounded to nearest 0.5 FPS -- sigma ~2(MAX) ~1(AVG) <1(95%). I really wanted to tell the difference between 3600 tuned subs and 3800 tuned subs, so these are 10 runs each averaged. The delta between these is small, but consistent and repeatable. I haven't run a p-test, but I'd be really surprised if the difference was not statistically significant based on looking at the individual runs. Seems like a small, but consistent gain for the 3800.

MIN FPS removed due to lack of consistency / high sigma.

Reported values are "CPU GAME" results from SotR benchmark

Speed320032003600380036003800
Timing16-18-18-1TIF@190014-19-16-1T15-20-17-2Tsubtimingsubtiming
MAX FPS170.0171.0183.0182.0187.0189.0
AVG FPS125.0125.5132.5133.5139.5141.0
95%95.595.099.5100.5106.0107.0

Analyzing this:

  • DDR4-3200 is about the same at 1600 infinity fabric or 1900 (for SoTR... Obviously could be different for other games)
  • About +6% AVG FPS and +4% for 5% lows in SoTR going from 3200CL16 to 3600CL14.
  • 3800 2T with tuned subs is slightly faster than 3600 1T with tuned subs. So 2T command rate can be made up with IF speed and 200 MHz.
  • Subtimings are HUGE. 6-7% on AVG FPS and on 5% lows... Overall a (slightly) bigger gain than 3200C16-->3600C14
  • Overall gain from OCing memory in this title was about 12% (!) if CPU limited.
  • You do not need super expensive memory to get big gains from tweaking your memory.

Subtiming tuning is a really big deal, but not all that difficult if you get HCI memtest and memtesthelper to validate. Pretty much anyone should be able to squeeze something like 5% FPS on CPU limits just tuning the subs. Sub-timings I tuned included only the following:

  • tRC
  • tRFC
  • tWR
  • both of the xSC_L timings
  • tFAW

Leave plenty of margin on tRFC, it's known to be a bit of a slow killer to corrupting files if you don't leave margin (10-15ns or so.... ~15-25 cycles) Don't just bump up 1-2 cycles when it's not stable, bump ~15 or more.

Posted Aug 5, 2019, 3:21 PM UTC · edited

185151
ubms1024•

I recently learned, that tFAW and tRRD make such a huge difference in CS:GO and other Source Engine games.

I gained 40 FPS (~420 to ~460) on my R7 2700 in the benchmark map, just by adjusting them from the ridiculously high Auto settings (like 11-13 52) to 4-4 16 with my Samsung OEM C-Die memory.

17
glamdivitionen•

Thanks for sharing!

1
Insolent_Mint•

Good catch.

1
1sooooR7 1700x VEGA 64 LE | LENOVO E585 2500u•

What is your c-die oc? Would love to know as i have been eyeing in them since forever.

1
ubms1024•

My best 2 4GB C-Die sticks out of the 12 I binned do 3660Mhz CL16-(17/21)-17-37-69 daily (stable) at 1.46V with my B450-I Strix and R7 2700 (trash IMC). I could probably get the primaries even a bit lower (tRCDWR and tRP seemed to have a bit of buffer), tighten the tertiaries, and lower the SOC voltage but for me, the effort is not worth it at this moment.

​

EDIT: I get 550 FPS in the CS:GO benchmark map with 64tick, affinity tweak, Windows 1607 LTSB, and 4.0Ghz CPU OC ;) I'm looking forward to getting a Vega 56, already ordered it but shipping from Germany will take a while... I'm GPU bottlenecked at the lowest settings with my current R9 280 @1150/1400 -_-

1
1sooooR7 1700x VEGA 64 LE | LENOVO E585 2500u•

Damn, you are actually getting like 120 fps higher than me and i have a vega 64.

Provided i used a mix of low and high settings at 1440x1080 with a 1700x but still that is a huge improvement.

1
ubms1024•

Mind you, that's NOT just the RAM settings. I use the affinity tweak w/ ProcessLasso from drax (here), and I have to use a very old version of Windows 10 (1607 LTSB N) so the scheduler doesn't mess with it. I also do all benchmarks with 640x480 and lowest settings, anything higher wrecks my GPU. When I actually get my blower Vega 56 (got a great deal for 219€ on Mindfactory), I bet I could hit the 580-600 range, since often in certain parts of the benchmark (especially in smokes) I get 100% GPU utilization. (even at 640x480)

3
ubms1024•

At 1024x768 or higher it's pointless for me to do the benchmark, since my GPU gets tapped out, and I get like 400 fps tops at 1440x1080.

1
ubms1024•

https://ctrlv.cz/7oDh - screenshot of full settings

1
ASrIOTS•

This sounds pretty nice. I actually bought two of the same kit so I’m running a total of 32GB. I turned on the XMP profile on my Asus TUF x570and it registers the ram at 3200 which was the advertised non OC’d speed on the package.

My question is, what can I follow to learn how to OC my ram to 3600 and tighten up my timings. I sort of understand some of the stuff you said but the vast majority makes no sense to me. Just trying to squeeze out as much performance as I can on my new system. Also from what I understand the whole Infinity Fabric does better with certain speeds etc? You want the 1:1 ration right? Just trying to figure out how I know that I’m there and what I can do to achieve it!

Thanks for the write up! Really appreciate it

9
ConcillianOP•

If you want to OC your memory, you need 2 things:

  1. You need to familiarize yourself with your motherboard's method of clearing CMOS. It's pretty likely you'll go too far at some point and the computer won't boot. Because of this, you want to save any stable or at least bootable settings in an OC profile often, so when you need to clear CMOS, you can get back to where you were before.
  2. You need a way to validate memory. I used "HCI memtest" and "memtesthelper". Google will find the links easily. Unzip both to the same directory and run memtesthelper. When you run, blank out the amount of memory and it will automatically put in as much as is reasonable to test. You want as much memory to be free as possible in Windows prior to testing. I would usually have ~1.6GB used based on WIndows Task Manager before hitting go, but this was a clean install and removed onedrive and turned off the Windows virus/malware scanner, unplugged the network cable, etc...

To start, I set voltage to 1.45, then scaled latencies based on speed and added 2 (multiply by 3600 / 3200 then add 2).

test with memtest for stability. To start with I only go 200-400% coverage in memtest. If stable, reboot, save to your testing BIOS profile, drop tCL by 1. Repeat until you reach instability and then bump it back up by reloading your last stable profile. Validate that is really stable by doing 1200-3600% coverage (takes a while).

Now repeat in this order: tRCD (read), voltage (0.01v steps), tRP, try tRCD write = tRP, once all of these are done, set tRAS to tCL+tRCD (read)+2.

Validate all that is stable, then drop subtimings one at a time using the same method.

If you take baby steps and save BIOS profiles along the way, it's tough to mess up, but takes a lot of time. You can also try my timings +2 as a starting point to account for variation in memory kits. Obviously buffer more on some of the larger sub-timings like tRFC and tRC. The xSC_L timings defaulted to 5, so they'll likely only go to 4.

22
demonstar55•

XMP is OCing btw. Its just a factory preset.

9
Moscato359•

On AMD, 3200 is a valid warrantied speed, for both motherboard and cpu

I don't think xmp on ddr4 3200 is considered overclocking

0
ArbabenderRyzen 7 1700 / ASUS Crosshair VI Hero / Gigabyte R9 290X OC•

JEDEC certified DDR4-3200 MT/s has much, much looser timings than pretty much every DDR4-3200 rated XMP profile.

5
Moscato359•

Can you even buy Jedec certified 3200 mt/s?

1
LongFluffyDragon•

Memory OC is strange, because you are actually overclocking multiple components; the CPU IMC, and the RAM itself, not to mention the motherboard bearing the load.

1
Moscato359•

If cpu is rated for 3200 (zen2) motherboard is rated for 4000+(x570) ram is rated for 3200 by vendor via xmp

is it overclocking?

1
demonstar55•

The ICs in the memory kit are not gonna be rated for 3200, it's OCing.

If they were rated for 3200, you'd plug them in and get 3200 at JEDEC timings, you'll probably get 2133 or 2400, but not 3200 :P

-2
Moscato359•

So this comes down to the definition of what is overclocking, and what does that actually mean.

If AMD, Gigabyte, and Gskill will all warranty running at 3200, then who actually determined that it's not rated for 3200?

4
Flyingff82•

I really appreciate your work and the results. For myself I have the 2x16Gb 3000-15 kit and managed to use 3600 14-19-14-(trc forgotten) with "tight" subtimings. However I also own a 2x16Gb B-die kit which can use better timings and get even better results. At the moment i cannot post them because of work in another country. The big advantage for the e-dies over Samsung is definitely the small price tag.

8
ConcillianOP•

The main message here is that anyone with any memory can likely tune sub-timings and get decent performance uplift even at stock voltage and speed... as much FPS gain as overclocking memory & Infinity Fabric speed AND lowering primary latencies gave.

I'm sure b-die is better, but as you note, it's quite a bit more expensive, especially for the highest bin. But even for a middling bin like 3200cl14 b-die, there's still a big price difference.

8
headegg•

Do you have any resources that best explain the process of overclocking ram?

1
ConcillianOP•

integralfx published this guide on OCing DDR4:

https://github.com/integralfx/MemTestHelper/blob/master/DDR4%20OC%20Guide.md

Some of it is slightly dated, but it's a useful resource.

But as noted, sub-timing tuning is really as or more important than overclocking. Do research on the sub-timings listed in my post and by other commenters on this thread.

4
fawg141twga•

I cannot get my 2x16 kit to boot over 3600 no matter how I try.

Debating whether to keep them or just plug in my b die sticks that hit 3733 cl15 with barely any work

3
alienking321•

Have you tried enabling gear down?

1
fawg141twga•

I've messed around with everything. Got dram calculator working with the XMP file for the E-die so I'll try sometime this weekend, currently running my B-die sticks and I just wasn't in the mood to swap today.

1
larrygbishop•

What is FPS difference between same speed and timing but 1T vs 2T?

6
ImaginaryTragedy3900X | 2080Ti | 3600C14 | 7804x1440p•

My 3600 C14 timings are almost-but-not-quite stable. I get errors at about 110% coverage. And I'm not sure what sub-timings to tweak to get stable anymore. Running F4-4000C17D-16GTZR b-die @ 3600 14-15-15-30. I can post all the subtimings if needed. Just about sick of messing with it even though I'm so close.

5
LuminescentMoon•

Try more voltage.

6
ImaginaryTragedy3900X | 2080Ti | 3600C14 | 7804x1440p•

I'm up to 1.48-1.5v and still the same story. I've tried both versions of DRAM Calc 1.5/1.6 and get memory errors instantly when running their recommended timings. I've found some pretty good guides and explanations for some of the subtimings, which helped tune it a little further. I get errors far less often, but still get them.

Here are my unstable 3600C14 settings, and a pastebin of some other timings. I have the DRAM Calc timings there as reference (1.X-s=safe 1.X-f=fast). 3600C16 is what I'm currently running stable, and 3600C14 is what I'm working with.

And here is some information I've gather from some posts as well. Its what I've been using as a reference for some of the subtimings:

tRC = tRP + tRAS

tFAW = tRRDS x 4+2

tRAS = (tRCD+tCL)+2

tRRD = tRRDS+2

tFAW = (tRDDL*4)+2

tRFC/tRFC(ns)*180(ns)=(560/350)*180=288

3
capn233R5 1600•

RAS~=RCDRD+CAS+BurstLength

Burst length is more like 4, see here. Can count the clocks on the diagram if you want. Too low will cause it to be substituted, so maybe it is academic.

Your RTP is set to 12. It is possible the memory controller is altering some values already in order to reconcile different entries.

The other formulas are just made up more or less, they aren't like a row access operation and RAS window.

FAW can really be more or less anything as long as it is not less than RRDSx4 (since it is the fifth activation on different bank groups, so it can't occur before the first four).

I don't know what timing is meant by RRD = RRDS+2, unless RRDL perhaps? You have RRD Short and RRD Long, aka RRDS and RRDL for different bank groups and same bank groups respectively, the short is generally shorter hence the name. Lot of profiles in the calculator have 6 and 8, but that is just more coincidence and how the profiles were made. Going by the spec sheet for my Micron, it would be more like 4 and 8.

The real trick is that any individual timing does not exist in a vacuum, and so it can be possible that a certain timing value does not work in combination with some others, but may work if those others are loosened, and vice versa.

Anyway, what is the XMP voltage rating for 4000MT/s on your kit? Do you think you have enough airflow over the sticks for 1.5V?

5
just_blue•

I´m really interested in this and wonder a few things:

  • Why is the DRAM Calculator not taking this into account? It would set tRAS too low if your formula ist true.
  • If I set it (tRAS) lower and lower, it will start to get instable at a really low value: 26 is still fine (full set of timings that is 100% stable: CL 16 - RCDWR 9 - RCDRD 19 - RP 15 - RAS 26 - RC 58 @3800). So if the BIOS is overwriting it when it´s too low, why does it stop at some point? When I think about it - maybe it is doubling the value.
  • 1usmus says "Do not forget to follow the rule tRC = tRAS + tRP.", the same as the poster above. Does this have a technical background as well? Because this wouldn´t work for me, tRC below 58 is no good on my E-Dies @3800.

I will definitely do some performance measurements to find out it if a higher value of tRAS may increase performance. It´s just difficult to find a benchmark that is sensible and repeatable enough to see a difference.

1
OZ-13MS3900X | Crosshair VII | 3600cl14 | 2080ti•

ohhh nice, now I can calculate my own subtimings.

1
Darkomax2600X / GTX 1070 / 16GB 3533•

I have a few suspects : ProcODT (on die termination) seems a bit high, Zen 2 seems to work best at 40Ohms or less. Gear Down Mode can be required above a certain speed (depends entirely on each CPU, my 1600 was ok with it disabled, my 2600X isn't). tCKe 0 is really tight, 8 is a safe value (unless you disabled Power Down mode, then you can ignore this timing). Could also be overheating, then better case airflow, or direct cooling, or lower voltage can help. If you have a temp sensors, then B-die tends to lose stability over 50°C. Or could just be below average silicon lottery.

​

Unrelated but you can tighten tRDRDSCL and tWRWRSCL to 2 or 3. (do it afterward, you wouldn't want to introduce additional instability factors)

1
ImaginaryTragedy3900X | 2080Ti | 3600C14 | 7804x1440p•

I tried a few ProcODT settings from 30-50. I read up to 60 was safe. But it doesn't seem to help too much. As for the tCKE, it is set to Auto and ends up setting 0. Basically all the timings under tRCPAGE were set to auto. And I've tried tCKE 1-9 with no change in errors either (PowerDownMode on/off). With a full stress load they were hitting 45-47C. I have decent airflow in my case, not 100% direct at the DRAM but should be okay.

1
LuminescentMoon•

I don't find the calculator or those formulas very helpful. What I do is just leave every timing on auto and only adjust primaries + tRC and tRFC. All of the other secondary timings are not worth the time to tighten. I work on one timing at a time, tightening by one and then give them 1-3 passes only on memtest86's block move test.

Note that tRFC can't really be tested for stability with only a quick run of memtest86. You'll need to test for a week to guarantee stability.

Also, I've noticed that you're using 1T CR with GDM off. You can try 2T OR 1T with GDM on to see if it helps with stability.

-1
Soulsalt•

Might need to play with vSoC and VDDG voltages too, just stay within recomendations for each

1
[deleted]•

[removed]

1
[deleted]•

[removed]

1
Coley44AMD|R5 3600|32GB 3200CL14|X370 Pro Carbon|Hybrid SC2 1080Ti•

3600% overall is not sufficient passage for HCI Memtest, you'll find on the manual/FAQ of the site that across every CPU thread you want 400% coverage, or a total of 4800%. You want every single thread above 400% minimum for daily stability, but it's highly reccomended to use Memtest86 overnight too as I found my overnight 3600MHz profile spit out an error on pass 2.

tRP, tRCWR and tCL can all be the same timing, as my 3200CL14 profile is 14-17-14-14-32, your SCL timings can usually do 2, RRDs/L can likely both do 4 and in turn tFAW can do 16, your tCWL can be 1 to 2 timings below tCL as well. You might be able to get tRFC to about 280~ NS effective if you're lucky but Rev.E doesn't like it that much. Your subs can be tightened much more, so can your primary timings. I reccomend HCI testing at each set of tightented timings till 200% all threads then when you hit a milestone, test till 400% all thread and then save that profile, continue tightening up where possible.

3
ChannwaaAMD 3800x 4.4Ghz OC, RTX 2080 (1875 at 0.9v), 2x8GB 3800CL16•

He isn't using Samsung B die. The timing he achieve is great for his kit. But I do agree with his stress test for the ram. He needs to do it longer.

5
Coley44AMD|R5 3600|32GB 3200CL14|X370 Pro Carbon|Hybrid SC2 1080Ti•

I'm using Micron Rev.E, that profile I just mentioned is a Micron Rev.E 1.45v profile. Rev.E should do about 3600CL14-19-14-14-36, tRFC of 540, SCLs, tFAWs and tCWLs the same as previously mentioned, and 3600CL16-20-14-14-36 will also be easy to achieve at around 1.35-1.38v. I validated and used both those profiles prior to getting another 16GB, my 1600's IMC can't take anything past 3200MHz right now but it's more than enough for me currently. When I grab a 3700x/4700x(if there's a refresh) I'll jump up to 3600CL14 on all 32GB.

1
ChannwaaAMD 3800x 4.4Ghz OC, RTX 2080 (1875 at 0.9v), 2x8GB 3800CL16•

For 3200? Thought you was asking him to do it for the 3800 lol. Maybe, not all kits are made the same though.

1
ConcillianOP•
  1. The HCI Manual suggests 400%... not 400% each individual thread. It makes no sense to set some arbitrary amount per thread, as someone with a 4/4 CPU would end up testing far less overall coverage to be considered "stable" than someone with a 6/12 or 8/16 or 12/24 CPU. As the manual notes, you could test for a week and have an error. Everyone needs to find their sane limit. 3600% is still a lot of coverage... BUT...

  2. Every primary has seen 10000% coverage or more in total due to the methodology. Leaving the subs for last ensures that the primaries get tested multiple times at 3600+%.

  3. As you noted, subs have margin in them. This is not an accident. These are the least tested settings, and the most likely to test stable with HCI memtest, yet not quite be actually stable... which slowly corrupts the OS... Been there... no thanks. The margin on subs is by design.

  4. At the end of it, after all that testing, voltage is increased another +0.01 for even more margin. Theoretically this could cause instability during heavy usage for a long time due to rising temperature... only temps are not an issue, or I would have had stability issues when I tested 3600% at 1.45v, which I did to cover just that scenario.

I understand the concern, but my method is specifically designed to not run on the edge and leave plenty of margin for a 24/7 usage.

tRP cannot be the same as tCL at the voltage and speeds I have tested on my kit. I didn't want to run 1.45v 24/7, so I found tCL at 1.45, then lowered voltage, then found tRP and everything else, then bumped voltage +0.01 to gain more margin for stability. If you've found different, then great. Kits are different, and different people have different levels of risk tolerance.

5
Coley44AMD|R5 3600|32GB 3200CL14|X370 Pro Carbon|Hybrid SC2 1080Ti•

From the HCI manual

We have found that testing to 400% coverage will catch almost all intermittent errors, but rather than trying to hit that number exactly, we recommend testing overnight.

Followed by

How many instances of MemTest: If you have a multi-core or multiprocessor machine you can make the memory test more effective by running multiple copies of MemTest at the same time. Start at least as many copies of MemTest as you have cores and then divide the amount of RAM to test between them equally. 

Even Integral from the overclocking discord who made the tool you're using will tell you the exact same thing, 400% coverage on all 12/16/24/36 threads (depending on your CPU thread count).

3600% is nothing in terms of RAM coverage, any significant memory testing will have you overnight/past eight hours total. Memory testing does not work cumulatively since a multitude of things can affect it's stability, and how much of the memory it goes through counts for even more. A mere 2 to 2 and a half hours coverage is not enough to say it's usable daily without corrupting your windows slowly but surely. I've already had it happen to me on a 450%+ on all threads profile, once you've validate HCI stable move onto Memtest86. It saves a fuckton of headache when your system begins to chug due to errors.

3
daddy_fizz•

I've always just used HCI or Karhu test...is there specific Memtest86 tests you would recommend? Assuming you are using the newest 8.2 version

1
Im_A_Decoy3900X|B350|3733C16|Vega 64•

The % tested per thread is actually the total % tested since each is testing a different chunk of memory. Can't just run 20 threads to 20% and say you got 400% coverage. Only look at the per thread value as the consolidated number MemtestHelper spits out is arbitrary.

Same thing I told him.

1
ConcillianOP•

I feel like neither of you is clear on what you're explaining, and I don't really know what either of you are trying to say, you may even be agreeing, but not being totally clear, so thinking you disagree. I can't even tell.

20 threads to 20% each means each thread is given it's own little memory range of 5% of memory, and each single thread has tested this 5% section 4 times (hence 20%.) Thus total coverage or total memory tested is 400%... because every area of memory that was allocated has been tested 4 times.

Where there can be discrepancies is thread to thread differences. Like say thread 1 is 95% and thread 2 is 105% because they're never perfectly synced. That means the 5% section thread 1 was given has only been tested 19 times and the 5% section thread 2 was given has been tested 21.

What that doesn't mean is that thread 1 didn't get fully tested because it's only 95%. It doesn't mean that. There's nothing magic about getting 100% in each thread or 400% in each thread. The per thread % is actually not very relevant at all.

Edit: Was wrong. Memtest helper interface does dumb stuff with the total percentage.

1
Im_A_Decoy3900X|B350|3733C16|Vega 64•

I was confused at first because he was talking about MemtestHelper, where I've only used memtest in separate instances. When you run an instance of memtest, it runs on a single thread for the amount of memory you allocate to it. So if I run one thread and assign 2048 MB of RAM, it takes that 2 GB chunk and tests it over and over and over again with one full pass being denoted by 100%. It would take 8 of these threads (or instances of memtest) to test 16GB of memory, and once each instance has reached 400%, you know all of the memory has been tested 4 times over. If a thread never got to 100%, then it will never have tested its entire allocated memory pool.

What MemtestHelper seems to do is automatically create instances of memtest for you based on a number of specified threads and RAM allocated. If it is taking the % coverage from each memtest instance, then it doesn't make much sense to add all of those up into a total percentage.

The way you seem to be describing would imply that it's taking a percentage of a percentage (like 5% of memory tested 4 times is 20% coverage). I'm in no way convinced that it does this, especially from my time running my own separate instances of memtest

1
Im_A_Decoy3900X|B350|3733C16|Vega 64•

The hell did I just read? That's not how it works at all. You can't just do 400% per thread and say it adds up to 4800%. Each thread is testing a DIFFERENT portion of the memory. If you actually want to test to 4800% coverage. You have to test each thread to 4800%!

You think if I just open 96 threads of memtest and run each to 50% then I've got 4800% coverage? NO, that's ridiculous!

1
Coley44AMD|R5 3600|32GB 3200CL14|X370 Pro Carbon|Hybrid SC2 1080Ti•

That was a typo dude, calm the fuck down. To begin with, it's one instance per thread, meaning you do 12 threads max on a 12t CPU, anything past this and your testing throughput/how much memory you can even work through fucking plummets because your CPU can't keep up. And each instance is testing it's portion of memory to 400%, that's quite fucking literally how MemtestHelper and HCI functions jesus christ. On an R5 6C12T chip, you divvy your memory into those twelve threads and wait for each instance to cover 400% of each thread, this may spill past 48,000% coverage total or it may stop dead on if you configure the program to stop there. By the fucking way, 4800% on EACH THREAD WOULD BE 1 WEEK+ OF TESTING. I did overnight on 32GBs@3200CL14-17-14-14-32 and it only managed just under 740% on the lowest thread and did about 800% on one thread. It seems to bog down further you go. I don't think you're truly aware how HCI even works so I've no clue why you're so asinine in this comment.

Edit: Just to fucking verify, did you even click on the image he posted where HCI MemtestHelper clearly fucking says "overall" at it's top, under each counted thread's current progress?

0
Im_A_Decoy3900X|B350|3733C16|Vega 64•

It seems you're far more worked up than I ever was. Clearly you didn't even understand what I said there in the slightest. I made no mention of how long you should test for and absolutely no mention of memtesthelper either.

Basic math says that if you're only testing 1/12th of the memory to 400% for each thread, then the total memory tested is 400% across all threads. Not 4800%. And while I don't have a 96 thread chip it was a fucking analogy that holds up regardless.

-2
Coley44AMD|R5 3600|32GB 3200CL14|X370 Pro Carbon|Hybrid SC2 1080Ti•

Congratulations on not even understanding the basics of MemtestHelper used in the 3800MHz screencap, even after multiple explanations on how it works. By the way, at no point did I even say it was 48,000% of the RAM, but entirely just what the program reads as total coverage. I have no interest in talking to someone that doesn't even understand how the aforementioned program even works yet comes in guns blazing like they've got their smoking gun

1
magnafides3700X / GTX1070•

my overnight 3600MHz profile spit out an error on pass 2

Is that the profile from this thread or with tighter timings than that? I am currently running Memtest with those timings to test for stability. I really would like a safe 3600MHz overclock @ no more than 1.4V.

1
Coley44AMD|R5 3600|32GB 3200CL14|X370 Pro Carbon|Hybrid SC2 1080Ti•

Nah that profile had no issues, the aforementioned 3600CL16 profile, from the comment you replied to, was a mishmash of MSI's try it functionality and some trial and error tightening. That said, you do realize even RAM oc'ing is sillicon lottery? You need to verify both your RAM sticks are Memtest86 stable overnight yourself, this isn't a universal thing. I've just found that most people that copy the timings from that post haven't reported BSODs and or data corruption. You must test for yourself.

1
magnafides3700X / GTX1070•

I mean, my comment did say I am testing as we speak, so obviously I'm not just taking the numbers for granted.

As for the silicon lottery aspect, It seems that I have lost (comparatively) as some other timings that people have posted (including the one from that thread) are definitely not even close to stable for me -- like I can boot the OS and that is about it. It seems like a key driver is tRCDRD which looks to be particularly finicky with my sticks.

1
Coley44AMD|R5 3600|32GB 3200CL14|X370 Pro Carbon|Hybrid SC2 1080Ti•

Well worth trying 1.45v, just make sure you have direct airflow on/around the sticks(well positioned top case mounted fans that line up with the RAM sticks) as they can be temperature sensitive.

2
TheBlack_SwordsmanAMD | 3900x | 3733 Mhz 14-16-14-28 | x570 ASUS C8H | RTX 2080 Ti•

Very nice work, much appreciated for all your runs, that's a lot of runs!

How do your sub-timings compare to DRAM calculator?

3
ConcillianOP•

Calculator SAFE is basically what the BIOS would put automatically for the sub-timings, so my subs are significantly below what it says in the SAFE profile.

Calculator SAFE 3600 was also not even close to stable on the primaries. Either production has changed since the author tested for the SAFE settings or my set is a bit of a dud, or that assumes higher binned e-die (Ballistix Elite e-die maybe?). Regardless, I didn't find the calculator all that useful outside of being able to convert tRFD from ns to latency cycles. All settings except tCL were far too aggressive for my sticks.

2
magnafides3700X / GTX1070•

The algorithm for e-die (at least) has changed drastically between versions 1.5 and 1.6 of the calculator. 3600 Safe is fine for me from Calc v1.5, but the Safe values from v1.6.0.3 are extremely unstable.

3
TheBlack_SwordsmanAMD | 3900x | 3733 Mhz 14-16-14-28 | x570 ASUS C8H | RTX 2080 Ti•

Yeah, k think the calculator favors b-die ram.

1
fawg141twga•

I doesn't even give me any values for over 3400 on my e die sticks, it just says it isn't supported

1
TheBlack_SwordsmanAMD | 3900x | 3733 Mhz 14-16-14-28 | x570 ASUS C8H | RTX 2080 Ti•

Try method 2 and 3 then.

1
Im_A_Decoy3900X|B350|3733C16|Vega 64•

Works beautifully with my CJR kit, though I wouldn't mind a fast profile.

1
destiny2sk•

2T or geardown mode feels laggy to me on Ryzen regardless of better benching results.

Got my 3466cl19 micron working at 3500 1t cl16 and in games feels better than 3600gdm with lower latency.

3
Im_A_Decoy3900X|B350|3733C16|Vega 64•

Yeah games felt so much better when I added more RGB too.

1
destiny2sk•

well yeah RGB adds 10fps for sure 😃 .... running true 1:1:1 mem controller, IF, dram is the best for ryzen that's 1t gdm off

1
HCxStrelokAMD | 2600X | 32GB DDR4 3200CL16 | GTX 1080 | Asus X470 Strix F•

Have you considered testing other games? I tested R6S, GRW, TD2 and Destiny 2 3200XMP (CL16) vs 3433CL14 with tuned sub timings and didn't notice much. I have 32GB though so my OC potential isn't as good, but I might just go back to stock since I didn't notice any meaningful difference for the games I play. This is Zen+ though, so maybe it makes a bigger difference on Zen 2.

This might become more important later down the road, like in 3-4 years when GPUs are much more powerful. I know for my 3770K it didn't show much difference back when it came out with different ram speeds, but changing from 1600 to 2400 in 2016 with a 980Ti saw a 10% boost on minimum and like 3-4% averages.

3
ConcillianOP•

Can't test other games until I get this into my main system so I have a halfway decent graphics card so I have a chance of using settings that will see a CPU bottleneck. Like any other performance improvement that impacts the CPU side, If you are 100% GPU bottlenecked at the settings you play (most people in real-world scenarios are close to 100% GPU bottlenecked,) then you will not see any difference.

1
gettin_creative2700X | 16GB@3400CL14 | GTX 1070•

tRFC tweaks (even a mild setting like 360) bumped my memory transfer rates by 10%+ when i made changes and run memtest VS. the auto settings. Definitely a 'must change' if you're going to OC your memory

Edit: auto setting was like 600+

3
just_blue•

This doesn´t work for Micron E-Die, though. It depends on your chip, but at 3800MHz clock anything lower than 550 is very difficult / lucky.

2
gettin_creative2700X | 16GB@3400CL14 | GTX 1070•

oh. i don't know anything about micron e-die.

however, on my samsung b-die set and my micron b-die set, it worked very well

3
WarUltimaOuya - Tegra•

Same memory.
I am running Fclk 1833 with Ddr4 3666 16-17-17-36 @1.35v 4200% coverage passed.

Using Ryzen dram calculator e die 3666 safe timing and subtiming.

I am getting 65.8ns latency. This is the lowest I could get while keeping the vdimm at 1.35.

Tried some other settings but even at 3733 my latency goes up.

This is on MSI x570 Gaming Plus with 3600.

3
Mackodlacko•

I have 4x16GB Dual Rank Micron E-Die kit. 3200MHz CL16.

I haven't played too much with OCing it yet. I just manually set it to 3600MHz and copied the exact same timings from 3200MHz DOCP. I got 59900MB/s copy and 70.2ns latency.

I will be trying to hit 3600CL14 with tight subtimings. So far my FCLK wont boot if I set it to 1900MHz with stock voltage.

2
destiny2sk•

quad rank is awesome, almost 60000MB/s nice !

2
Im_A_Decoy3900X|B350|3733C16|Vega 64•

You'll definitely need some SoC voltage to run 1900 Fclk. That latency seems a little high for 3600C16. Is your Fclk coupled?

1
Kankipappa•

Very good, I've been trying to preach that exactly those subtimings seem to matter the most on Zen/Zen+. To my suprise, nothing has really changed in Zen2. Only the increased cache size just helps to gain on some degree, until the RAM bottleneck is finally visible.

In the end the primary timings do not even matter that much, if the subtimings are tweaked in to my experience. Yes you can squeeze additional performance on really tweaking the memory, but even stock ram with subtiming tweaks gives 2/3 of the total boost.

2
magnafides3700X / GTX1070•

Thanks for this, I will definitely try your 3600 timings, with perhaps a bit of a margin on the sub-timings as you suggested. I'm not looking for bleeding edge, just "good enough". As an aside, is there anywhere that we can find timings for the 3600MHz XMP of the Ballistix Elite sticks? I'd be interested to see how these timings compare to those.

2
ConcillianOP•

Found this article with a Thaiphoon Burner screenshot showing XMP for the Elite: http://www.relaxedtech.com/reviews/ballistix/elite-3600mhz-32gb-memory-kit/

1.35v 16-18-18-38. tRC on the Elite XMP is way lower than the Sport LT XMP.

1
acorns50728•

Appreciate the hard work. I am not sure if this finding is universal. I am running dual rank e-die at 3733 18-20-18-18 using standard motherboard auto timing for secondary and I get higher score in SOTR, about 9% better than your highest on average fps.

3 run average, 95%: 112, max: 202, avg: 152.

Edit: after closing bunch of stuff (eg steam), my avg jumped to 158fps.

2
it_was_a_wet_fart•

Im assuming that you have an identical system to OP? Otherwise your results can't be directly compared to there's as having a different graphics card would have a much bigger impact than memory tweaking.

1
acorns50728•

3700x and 1080ti using CPU GAME result.

1
zenstrive•

What's the XMP rating of the kit, 3200 CL16?

2
tarduq_1•

Yeah it is, I have the same kit.

1
FineCard•

Thanks for posting this. How much would the fps numbers change if the resolution is 1440p+?

1
ConcillianOP•

The benchmark ignores any GPU bottleneck and just posts what the CPU bottleneck WOULD BE. Keep in mind this was my 3rd string GPU (a Radeon HD7850). The actual FPS was insanely low (20s), which is why I had to use SoTR to benchmark, as it's the only benchmark that actually shows what the CPU limited performance would be without needing to put in like a 2080Ti. In most cases you'll choose settings that will put you in a GPU bottleneck most of the time and won't see actual FPS close to these. Actual FPS at 1440p won't show this kind of difference, the benchmark was chosen specifically to be sensitive to and highlight the difference between memory configurations.

So your theoretical CPU maximum gains should be similar %, but in real-world scenarios you're likely to be in a GPU bottleneck situation that will show much less improvement (maybe even zero difference if you are GPU limited 100% of the time.)

2
Im_A_Decoy3900X|B350|3733C16|Vega 64•

Forza Horizon 4 also shows the CPU performance separately.

1

You need to run Memtest86 if you want to test stability.

1
punktdot1•

Memtest86 isn't really for OC stability but to try and find out if there are defects on the RAM.

For OC stability I'd recommend Karhu and HCI.

4

Memtest86 is absolutely for "OC stability". It's for stability period, and it offers the most thorough testing routines you're gonna get, and it does so with much more access to the memory pool than you're going to get by running something from within Windows.

For OC stability I'd recommend Karhu and HCI.

And you'd be wrong.

2
punktdot1•

And you'd be wrong.

Dude, I've been OCing for probably longer than you are alive. Don't try to "educate" me when you have no clue.

Sorry for the harsh words, but stay humble and learn. No need for Memtest86 nowadays.

6

Dude, I've been OCing for probably longer than you are alive.

I can guarantee that's not the case. Memtest86 is still the best memory testing option there is, by far.

1
daddy_fizz•

I've always just used HCI or Karhu test...is there specific Memtest86 tests you would recommend? Assuming you are using the newest 8.2 version

1

Yes. Use all of them. The only one I'd recommend anyone skip if they're pressed for time is #13 (row hammer).

1
jforce321R5 3600 - RTX 2070 - 16GB Ram•

I have old ass lpx 3000 memory from the intel 6th gen days that from research is samsung die, but I have no clue which specific die since none of the usual programs can see the specific manufacturing code past "corsair". I've found I need to use geardown mode to get workable results on my kit at cl16 3466 stable.

1
KING_of_Trainers69GTX 1080 | R5 2600 | Ubuntu•

Thaiphoon Burner will tell you which ICs it uses.

1
jforce321R5 3600 - RTX 2070 - 16GB Ram•

I just said none of the usual programs will work that means even that program

0
KING_of_Trainers69GTX 1080 | R5 2600 | Ubuntu•

What does it say?

1
jforce321R5 3600 - RTX 2070 - 16GB Ram•

It literally just says Corsair if I look at the manufacturing ID they don't have any info on there but someone did help me find out that they were Samsung purely by looking at some really old reviews and some forum posts.

1
dziggR5 3600 (4,1 ghz @1,25v) - Red Devil Vega 56 - 3600mhz 16 GB RAM•

Sorry for a noob question, I have a T-force delta RGB 2x8 GB, Thaipoon said I have a micron, but didn't have info about what Rev it is, how do I know which version it has?

1
KING_of_Trainers69GTX 1080 | R5 2600 | Ubuntu•

The "Die Density/Count" section tells you which ICs it uses.

2
dziggR5 3600 (4,1 ghz @1,25v) - Red Devil Vega 56 - 3600mhz 16 GB RAM•

Mine just says : 8 Gb / 1 die Also I bought this as 3000mhz kit, but speed grade in thaiphoon is DDR4-2400R, is this right?

1
KING_of_Trainers69GTX 1080 | R5 2600 | Ubuntu•

Yes.

1