With my kit going from DDR4-3200 to DDR4-3400 it wasn't worth it with the looser timings I couldn't seem to trim down, but to my surprise (on the older BIOS) it did allow DDR4-3600 and that fit better with the scaled up timings I had to use anyway. Why do you run WinRAR benchmark that takes about 30 seconds to complete when you have 1 second resolution. You don't actually expect DDR4-3200 compared to DDR4-2400 to give you a 3.3% boost on overall system performance when your previous benchmark showed that the gain in pure memory bandwidth is around 10-15% and the latency boost is around 3%. I also have a kit of 4.32 ram (different model, size, and dual rank) and found it didn't like tRC timings (and some lower tRFC) out of the box and were a bit problematic to get working. I needed to reconfigure ProcODT, RTT, and SOC to push over DDR4-3200 successfully.

It's a theory that may seems reasonable but I cannot confirm for sure in any way and would be interesting to understand the difference. I am wondering if anyone has this exact RAM/memory and if they have a Ryzen system, what speed they are able to get? In fact... Now on my same board with Ryzen 5 2600X I get 3200 14 14 14 34 timings stable. On MSI boards in the BIOS, they have a list of frequency and timings you can TRY and that one also works. So I can run that or 16 18 18 36 no problem. CAS 14 settings is faster a bit but so far only in RAM benchmarks. Not in anything else.I don't know if it matters about BIOS version or motherboard manufacturer but I was planning on considering a Ryzen build. Part of our exhaustive testing process includes performance and compatibility testing on nearly every motherboard on the market – and a few that aren’t. If you want to benchmark RAM, it seems like you understand that you need benchmarks that are RAM constrained and compression is part of it, though that's largely CPU bound not RAM bound. In terms of WinRAR specifically, this benchmark offers nothing because your resolution is so poor you can only separate dual cores from quad cores from hex cores, you can't distinguish hex cores with DDR4-2400 from hex cores with DDR4-3200. On top of that, WinRAR is more dependent on the disk so using an M.2 PCIe 3.0 x4 drive should be distinguishable from a SATA-III SSD, is distinguishable from a HDD. You could make the WinRAR benchmark more meaningful by using a bigger data set -- if 1.3GB takes 30 seconds then 15GB should take about 346 seconds and now you can resolve to within 1/346 = 0.29%. Well below what anyone really cares about.

Glad to report that the system did POST and everything seems to be working smoothly. Did some mem testing for around 10 minutes and it didnt crash, so I guess the pc is usable for now. I will stress test and benchmark tomorrow, too tired now.

In particular this is a good way to get what your motherboard decides to use by default for termination, cad bus, and misc values. This provides a base point where you know what values already work. Details about the extent of our regulation by the Financial Conduct Authority are available from us on request. I used the import feature from Thaiphoon because I noticed that even though I put in the correct specifications in all the main fields like rank, number of modules, frequency etc the timings still changed when I used the imported file in DRAM calculator. I left Samsung b-die instead of Samsung OEM, as you suggested, because that would give me invalid numbers. Then I heard about what you said about tRFC and I set the alternative setting (432) as well as the tWRRD (3).