There's one fundamental error I've made and that's with the timings on this board. I wrote this article elsewhere so I'm going to copy it verbatim (it is part of a Memory tuning series I'm working on and this was a prelude if you will).
Note: It was my intention to start a series on the various parameters added to AGESA 22.214.171.124 for the purposes of performance tuning. In the process of gathering my material I noticed a fundamental error which is apparently repeated often across the internet. So this installment is explaining one of the errors before delving into the original intent.
With the latest BIOS releases which include AMD’s AGESA 126.96.36.199 we’ve seen 26 parameters added for overall memory compatibility and stability support, documented in AMD’s Community Update #4: Let’s Talk DRAM! One parameter we’re going to take a look at is tRC; this is row cycle time, or the number of clock cycles required for a memory row to complete a full operational cycle. This specific parameter caught my attention; after looking at older CPU-Z and AIDA64 Extreme outputs, I noticed the same timings for my memory 14-14-14-34-82 (CAS-tRCD-tRP-tRAS-tRC respectively). These values are wrong for my specific memory as it does not match the information stored in SPD, which should be 14-14-14-34-48 (also verified with Thaiphoon Burner). I clearly made an input error which I want to address first.
Before I explain my error (and one I’ve seen in many screenshots of other systems on the internet), I’ll describe the hardware used; I am using my trusty Asus Crosshair VI Hero motherboard, AMD Ryzen R7 1800X, and a G.Skill TridentZ RGB quad kit (F4-3200C14Q-32GTZR). The settings (parameters) used in this article should be available on most X370 motherboards with an AGESA 188.8.131.52 updated BIOS. As always, going beyond the stock DDR4 frequencies (2133MHz) and above JEDEC standards (2667MHz) is considered overclocking, regardless of the advertised speeds! As such, the possibilities of system instabilities with resulting BSODs etc do exist and you do so at your own risk.
Now on to fixing my error, and hopefully showing you in the process how not to make the same mistake. In the heat of the moment (being excited and all to build my first Ryzen system), I overlooked some of the timings used and went straight down the row and entered 14-14-14-34-48, which would end up being wrong. The corrected way it should look in the BIOS for my memory:
Going down the row on this BIOS would put the tRP to 34, and the tRAS to 48. The error was skipping the Write Delay entry which should’ve been 14T as shown in the picture above! You can see how easily this entry can be missed if not paying close attention.
Now why did my CPU-Z/AIDA64 outputs show 14-14-14-34-82? In most cases the row cycle time (tRC) is the sum of tRP and tRAS, in my case (with the error) it would be (34+48).
Now CPU-Z information shows the correct information under the memory tab:
The moral of the story: take your time and make sure you know the correct timings for your memory, but also make sure you understand or know which values are correct per BIOS. To make matters even more confusing, the same values may be described differently (if at all!), for instance “tRC” is also shown as ‘tCS” but in this case they are the same thing. A good example: take a look at the CPU-Z validation link below, the Crosshair VI Hero BIOS screenshot, and the CPU-Z screenshot and compare the descriptors for the same values!
Even between BIOS revisions for the same motherboard, I’ve seen different descriptions/headers often as a result of hurried coding during BIOS assembly. Anyway, with this out of the way, stay tuned for a proper guide on memory tuning and overclocking
CPU-Z validation: https://valid.x86.fr/9u2uw3
I'm actually not even close to being done with this one. The case is still going to be modded to finish the theme, and of course, the GPUs will see something a little newer once waterblocks are available.
Try as I may, I cannot get my board to hold the correct timings. My tRC should be 54 but keeps boot looping the system and settling at 74. Even with the correct timings in all the correct places. Very strange. I keep tinkering with it each day to see if I can get it to stick. No luck so far. Still 1000x better to work with than my last board.
I submitted Oscar-Mike for the 2017 AMD #AMDRTContest QuakeCon Sweepstakes Official Rules and got the following back today:
Original submission video: Whiskey-Foxtrot on Twitter: "My Favorite @AMDRyzen rig Oscar-Mike @AMDGaming #AMDRTContest #QuakeCon...