Honestly I would not obsess over JEDEC settings. Aim for a decent 2x16GB Crucial kit, preferably DDR4-3600. Don't enable XMP since it can do odd things, such as affect vSoC, VDDP, and VDDG in undesirable ways. Better to try to emulate the XMP profile by hand or just use Ryzen Memory Calculator. You're building a high-end rig, and it's best to treat it like one. Plus Micron e-die kits from Crucial are pretty cheap.
Crucial has been working very well for me personally with custom timings as well. I especially didn't mention manual timings though, as It's quite a bit of manual labour to enable these, it requires mem-testing for stability and most importantly requires redoing every time you update the BIOS.
From my experience there are a number of (even quite computer savvy people) that simply don't want to deal with this.
I've seen people do it for the first time and not only are they often scared, they usually make mistakes or fail to test stability correctly and end up reverting it.
These are just some mistakes i've had to debug remotely for those who've tried:
- They insert some input data for the calculator incorrectly - If it's the die type, rank, mobo, it's usually easy to catch, but sometimes just one profile is stable (e.g. V2) and it's not trivial to understand.
- They insert the calculator data into the BIOS incorrectly - There are a lot of fields after all and depending on the mobo producer, it's not always trivial to find/understand what goes where.
- For instance MSI has 4 "TRFc" fields or one-for-all, not "TRFc" and "TRFc alt".
- Some fields have underscores in the names that don't line up with DRAM calc.
- It is trivial for me and you, but very frightening for someone who tries it for the first time (and rightfully so, playing a monkey with BIOS settings is a quick way to a disaster).
- They fail to up to test for stability ("oh it boots and runs my game, who needs memtest!") or up the Volts.
- Later, when the system is mildly unstable (e.g crashing once every couple of days) they attribute it for god knows what else.
From my experience people don't want to be aware of all these intricate details (sub-timings and tertial timings, mem-die types, etc) nor do they wany to waste hours tuning these (and it will definitely take hours if it's your first foray into memory-OC land).
At least the majority of my friends certainly don't want to deal with that. Even the ones working in IT that have had gaming rigs for years. Well unless I do it for them, of course
I can also understand their reluctance. Free memtests can take hours to run and quick ones (like karhu
) cost. Also some custom timings, even in SAFE preset require 1.39V - 1.40V on E-die. It's a significant increase from the listed 1.35V on the box. Even though it's mostly safe, you can't blame people for being careful. Overall it's a lot of work for small gains, that the memory makers should really do themselves in the first place (by creating a non-sucky OC standard like AMP 2.0). After all, why could't it all "just work"?
All of this leads me bact to my initial point:
Custom timings are nice and give the best performance by far, but are time consuming and somewhat error prone to set up and validate (unless you have experience).
XMP @ 3600 is stable (99% of time) on memory-kits listed in the mobo compatibility list. It's also quick to set up and gives you most of the benefits (like decent FCLK)