Possibly some good news for Ryzen users...

[A Computer Guy]

If you have an ASRock X470 Master SLI/AC you may get improved memory compatibility with the P3.20 version BIOS/UEFI update including AGESA 0.0.7.2.

 

Running CMK16GX4M2A2400C16 (2 kits) 16-16-16-39-55-1T, 2400MHz @1.2v

 

Old P1.9 BIOS/UEFI with AGESA 1.0.0.6

I was not able to use the original timings when overclocked and occasionally memory retraining would kick-in again on boot every now and then.

20-20-20-48-68-1T, 2933MHz @1.35v, SOC@0.920v (oc stable, 4 sticks)

 

New P3.20 BIOS/UEFI with AGESA 0.0.7.2

I was able to use the original timings while overclocked and the memory retraining problem is now gone.

16-16-16-39-55-1T, 2933MHz @1.35v, SOC@0.920v (oc stable, 4 sticks)

 

Did anyone else notice any memory improvements with their Ryzen boards with AGESA 0.0.7.2 updates?

[Corsair Rick]

Hello A Computer Guy,

 

That's great to hear! I'll definitely keep that in mind and mention it when needed. Thanks!

[Gronar]

If you have an ASRock X470 Master SLI/AC you may get improved memory compatibility with the P3.20 version BIOS/UEFI update including AGESA 0.0.7.2.

 

Running CMK16GX4M2A2400C16 (2 kits) 16-16-16-39-55-1T, 2400MHz @1.2v

 

Old P1.9 BIOS/UEFI with AGESA 1.0.0.6

I was not able to use the original timings when overclocked and occasionally memory retraining would kick-in again on boot every now and then.

20-20-20-48-68-1T, 2933MHz @1.35v, SOC@0.920v (oc stable, 4 sticks)

 

New P3.20 BIOS/UEFI with AGESA 0.0.7.2

I was able to use the original timings while overclocked and the memory retraining problem is now gone.

16-16-16-39-55-1T, 2933MHz @1.35v, SOC@0.920v (oc stable, 4 sticks)

 

Did anyone else notice any memory improvements with their Ryzen boards with AGESA 0.0.7.2 updates?

 

I'm still waiting on Asus to post the BIOS that was announced on the day you posted this, 4/29. Still can't get mine stable at 3200 but can run at 3066,

[A Computer Guy]

I'm still waiting on Asus to post the BIOS that was announced on the day you posted this, 4/29. Still can't get mine stable at 3200 but can run at 3066,

 

I think you said in a different post you had all four slots filled?

 

Frequency becomes more limited when all four slots are filled from the load on the memory controller. It may be very difficult to reach DDR4-3200 in that case. For many the limit is DDR4-2933 when all four slots are filled.

[A Computer Guy]

If you have an ASRock X470 Master SLI/AC you may get improved memory compatibility with the P3.20 version BIOS/UEFI update including AGESA 0.0.7.2.

 

Running CMK16GX4M2A2400C16 (2 kits) 16-16-16-39-55-1T, 2400MHz @1.2v

 

Old P1.9 BIOS/UEFI with AGESA 1.0.0.6

I was not able to use the original timings when overclocked and occasionally memory retraining would kick-in again on boot every now and then.

20-20-20-48-68-1T, 2933MHz @1.35v, SOC@0.920v (oc stable, 4 sticks)

 

New P3.20 BIOS/UEFI with AGESA 0.0.7.2

I was able to use the original timings while overclocked and the memory retraining problem is now gone.

16-16-16-39-55-1T, 2933MHz @1.35v, SOC@0.920v (oc stable, 4 sticks)

 

Did anyone else notice any memory improvements with their Ryzen boards with AGESA 0.0.7.2 updates?

 

 

If anyone is interested here are instructions for building a simple spreadsheet to calculate memory timings.

 

Columns/Formulas:

 

Column A: "Old Freq."

Column B: "Description"

Column C: "Old Timing"

Column D: "Old NS" (format to 4 decimals)

- formula: "=(1/(A2/2)*C2)*1000"

Column E: "New Freq."

Column F: "Calc. Timing" (format to 4 decimals)

- formula: "=D2*(E2/2)/1000"

Column G: "New Timing" (format to zero decimals)

- formula: "=ROUND(F2, 0)"

Column H: "Try Timing"

Column I: "Try NS"

- formula: "=(1/(E2/2)*H2)*1000"

Column J: "Delta NS"

- formula: "=I2-D2"

 

Instructions:

- Fill out the columns A, B and C for frequency, description, and timings. (info from your memory specifications)

- The "Old NS" will fill in with timings in nanoseconds.

- You should be able to compare this to your memory specification nanosecond timings.

- Fill out the "New Freq." column with the desired frequency for your overclock.

- The "New Timing" column should approximate timings that you may be able to use at the higher frequency.

- From there you can try reducing the timings and see the the change in nanoseconds.

 

Sample:

 

-----|-------|-----|----------|------|----------|-----|-----|-----------
A    | B     | C   | D        | E    | F        | G   | H   | I
-----|-------|-----|----------|------|----------|-----|-----|-----------
2400 | CAS   |  16 |  13.3333 | 2933 |  19.5533 |  20 | 14  |   9.5465
2400 | RDC   |  16 |  13.3333 | 2933 |  19.5533 |  20 | 17  |  11.5922
2400 | RP    |  16 |  13.3333 | 2933 |  19.5533 |  20 | 17  |  11.5922
2400 | RAS   |  39 |  32.5000 | 2933 |  47.6613 |  48 | 39  |  26.5939
2400 | RC    |  55 |  45.8333 | 2933 |  67.2146 |  67 | 55  |  37.5043
2400 | tRFC1 | 420 | 350.0000 | 2933 | 513.2750 | 513 | 420 | 286.3962

Edited May 24, 2019 by A Computer Guy

[GWNewman1]

I think you said in a different post you had all four slots filled?

 

Frequency becomes more limited when all four slots are filled from the load on the memory controller. It may be very difficult to reach DDR4-3200 in that case. For many the limit is DDR4-2933 when all four slots are filled.

 

Ran into this with my 2700x on my Strix X470 - it was godawful picky on running 32gb 3200 c14 kits with 4x8gb. I went through 3 of 4 kits before I wound up replacing it with a Crosshair VII and it worked like a charm with my Vengeance Pro kit. The Strix would fail memtest left and right with Windows being sketchy under load. RMA'd it back to Asus.

[Baio]

Asus CrossHair Hero VII WiFi and 2700x: with the latest BIOS 2304 I can run my G.Skill @3600 CL16 (target speed) for the first time.

 

Baio

[A Computer Guy]

Well some bad news.

 

If you have an ASRock X470 Master SLI/AC you may get worse memory overclock with the P3.24 version BIOS/UEFI update including AGESA 1.0.0.1.

 

This BIOS/UEFI update completely destroyed my overclock.

 

was on 16-16-16-39-55-1T, 2933MHz @1.35v, SOC@0.920v (oc stable, 4 sticks)

back to 20-20-20-48-68-1T and returned memory training problems even at this setting.

 

Beware.

Edited June 14, 2019 by A Computer Guy

[Gronar]

Well some bad news.

 

If you have an ASRock X470 Master SLI/AC you may get worse memory overclock with the P3.24 version BIOS/UEFI update including AGESA 1.0.0.1.

 

This BIOS/UEFI update completely destroyed my overclock.

 

was on 16-16-16-39-55-1T, 2933MHz @1.35v, SOC@0.920v (oc stable, 4 sticks)

back to 20-20-20-48-68-1T and returned memory training problems even at this setting.

 

Beware.

 

Pretty much what happened to me too after getting the BIOS update I wanted. I could run the 4 sticks at 3000 before that, now I'm reduced to 2800. Going to be replacing this TUF board soon I hope.

[A Computer Guy]

Pretty much what happened to me too after getting the BIOS update I wanted. I could run the 4 sticks at 3000 before that, now I'm reduced to 2800. Going to be replacing this TUF board soon I hope.

 

I'm hoping the updates that come out soon for the 3000 series will help but not banking on it to improve 2000 series. I'm thinking of going back to 2 sticks to see how the situation has changed there.

 

Saw a youtube video explaining how daisy chain memory configuration impacts performance and overclocking potential so the situation is really just the worst case scenario with 4 sticks. Basically a performance vs. capacity situation.

[Gronar]

I'm hoping the updates that come out soon for the 3000 series will help but not banking on it to improve 2000 series. I'm thinking of going back to 2 sticks to see how the situation has changed there.

 

Saw a youtube video explaining how daisy chain memory configuration impacts performance and overclocking potential so the situation is really just the worst case scenario with 4 sticks. Basically a performance vs. capacity situation.

 

I can run two sticks at 3400 with no issues at all, haven't tried to push it further than that yet. Right now though I've gone to quantity over speed, running the full 32GB.

[A Computer Guy]

I can run two sticks at 3400 with no issues at all, haven't tried to push it further than that yet. Right now though I've gone to quantity over speed, running the full 32GB.

 

I got a CMW32GX4M2C3200C16 (ver 4.32, 2 sticks, dual rank, 32GB) kit working at 3200. Will post results in the next few days.

[A Computer Guy]

So it seems I found a nice middle ground with CMW32GX4M2C3200C16 where I have 32GB (2 sticks, dual rank) that runs at DDR4-3200 with a Ryzen 5 2600.

 

If I underclock it to DDR4-2933 the XMP timings entered manually work with no problem.

 

If I match the clock to DDR4-3200 this is where things got difficult as initially it wouldn't post 99% of the time.

 

I figured out when I was attempting to apply the settings from DRAM Calculator for Ryzen 1.5.1 to the BIOS/UEFI there was some additional technique involved that I had not been doing before when dealing with my Vengeance LPX sticks where I had significantly limited success.

 

Trying to input and apply all the settings all a once from DRAM Calculator into the ASRock BIOS/UEFI was not working and I found splitting up the saves allowed me to finally post at the higher frequency.

For example:

1) Set to DDR4-2133 with AUTO timings, save, reboot

2) Set procODT, RTT, and CAD_BUS options, save, reboot (this is what finally allowed me to post above DDR4-3200)

3) Set voltages for DRAM and SOC, save, reboot (for ASRock be sure to use the option "SOC OVERCLOCK VID" not that SOC offset option!)

4) Increase frequency, save, reboot

5) Set timings, save, reboot

6) Test and adjust

 

To prepare for entering timings I first prepared a worksheet from the SPD information with the memory timings in nanoseconds. I would use the nanosecond timings with the debug profile option in DRAM Calculator to calculate a safe JEDEC like profile for my target frequency.

 

Next this information is used to create another worksheet to calculate all timings that may work at the higher XMP frequency and their translation into nanoseconds. I would use these timings in nanoseconds with the debug profile option in DRAM Calculator to calculate a safe XMP profile for my target frequency.

 

With the worksheets and DRAM Calculator profiles I reconciled what timings to use and test with and additional settings.

 

To make a long story short here are the timings that worked for me.

DDR4-3200
18 - tCL   (from XMP 16+2)
18 - tRCD  (from XMP)
18 - tRP   (from XMP)
36 - tRAS  (from XMP)
58 - tRC   (from XMP 54+4)
 6 - tRRDS (from XMP)
 9 - tRRDL (from XMP)
36 - tFAW  (from XMP)
 4 - tWTRS
12 - tWTRL
12 - tWR
 6 - tRDRDSCL
 6 - tWRWRSCL
560 - tRFC  (calculated from SPD data) 
416 - tRFC2 (calculated from SPD data)
256 - tRFC4 (calculated from SPD data)
18 - tCWL
10 - tRTP
 6 - tRDWR
 3 - tWRRD
 1 - tWRWRSC
 7 - tWRWRSD
 7 - tWRWRDD
 1 - tRDRDSC
 5 - tRDRDSD
 5 - tRDRDDD
 8 - tCKE

DRAM = 1.35v
SOC = 1.012v (SOC OVERCLOCK VID = 54)
Gear Down Mode = Enabled
Power Down Mode = Disabled
BGS = Disabled
BGS-ALT = Enabled
ProcODT = 60 ohms
RTT_NOM = RZQ/7(34)
RTT_WR = RZQ/3(80)
RTT_PARK = RZQ/1(240)
CAD_BUS = All 24 ohms

 

The XMP values that refused to work were tCL at 16 and tRC at 54 and they needed adjustment to post.

 

I was able to calculate the tRFC values based on the SPD data. The BIOS/UEFI kept wanting to use 312 on AUTO but that simply would not work.

 

DRAM Calculator suggested 16 for tCL, tRCD, tRP, and 307-312 for tRFC however this just would not work.

 

According to SPD this kit is Samsung b-die however I suspect probably not the best quality b-die that does CL14 that you constantly hear about.

 

ASRock's ability to change the SOC voltage was a bit out of the way. You have to find an option called "SOC OVERCLOCK VID" and enter a hexadecimal value to change the voltage. I came across a German youtube video that provided the VID values. (probably due to BIOS/UEFI updates the VID values may be different) On my system the value "54"=1.016v, increase the value to lower the voltage, decrease the value to increase the voltage. There is a SOC offset option however don't use that. I found in using that the BIOS/UEFI pushed my SOC over 1.2v unexpectedly.

 

I hope this is helpful to those that want to use 32GB (2 sticks, dual rank) configuration at DDR4-3200 with Ryzen. (same settings work for DDR4-3266)

 

DDR4-2933 to DDR4-3200 makes a big difference. I couldn't get DDR4-3333 working without some awful timings, not worth it. (perhaps workable with better motherboard & cpu)

 

(edited post for more completeness)

Edited July 2, 2019 by A Computer Guy

[Gronar]

Awesome info dude! My crypto mining machine has an ASRock board in it and I'm seriously considering going back to one for this 2600X gaming rig when the X570's are released.

[A Computer Guy]

I had a breakthrough. Event though the SPD indicated Samsung b-die DRAM Calculator's "Samsung OEM" profile more closely matches the actual timings of this ram module.

 

After using those numbers I finally have nearly the original XMP timings locked in at DDR4-3200 and it's seems stable (4 passes of memtest86)

 

(correction: 7/1/2019 - I was mistaken I accidentally selected DDR4-3066 in the BIOS/UEFI instead of DDR4-3266 without realizing it initially so these settings are actually for DDR4-3066)

 

DDR4-3066
16 - tCL   (from XMP)
18 - tRCD  (from XMP)
18 - tRP   (from XMP)
36 - tRAS  (from XMP)
56 - tRC   (from XMP 54+2)
 6 - tRRDS (from XMP)
 9 - tRRDL (from XMP)
34 - tFAW  (from XMP 36-2)
 4 - tWTRS
12 - tWTRL
24 - tWR
 5 - tRDRDSCL
 5 - tWRWRSCL
480 - tRFC  (calculated from SPD data) 
16 - tCWL
12 - tRTP
 6 - tRDWR
 3 - tWRRD
 1 - tWRWRSC
 7 - tWRWRSD
 7 - tWRWRDD
 1 - tRDRDSC
 5 - tRDRDSD
 5 - tRDRDDD
 8 - tCKE
DRAM = 1.35v
SOC = 1.012v (SOC OVERCLOCK VID = 54)
Gear Down Mode = Enabled
Power Down Mode = Enabled
BGS & BGS-ALT = AUTO
ProcODT = 60 ohms
RTT_NOM = RZQ/7(34)
RTT_WR = RZQ/3(80)
RTT_PARK = RZQ/1(240)
CAD_BUS = All 24 ohms

Edited July 2, 2019 by A Computer Guy

[Gronar]

Well here's some good news A Computer Guy: BIOS update for my board last night, I'm now running all 4 of my Dominator Plat RGB with DOCP active, 3133MHz and appears to be stable. 3200 hard locked the machine when I ran a game. That's the best speed I've seen though, better than the previous 3000 I was getting.

[Gronar]

Spoke too soon. Ran stable all day just web browsing. Played Destiny a while and the game kept crashing, then the system. Backed off the speed to 2800 and stable while gaming again.

[A Computer Guy]

Spoke too soon. Ran stable all day just web browsing. Played Destiny a while and the game kept crashing, then the system. Backed off the speed to 2800 and stable while gaming again.

 

Have you seen this article? It really helped me last time around.

"AMD Ryzen Memory Tweaking & Overclocking Guide"

https://www.techpowerup.com/review/amd-ryzen-memory-tweaking-overclocking-guide/

 

Also something I noticed last time when troubleshooting Ryzen Timing Checker doesn't seem to work quite right anymore perhaps because of the newer BIOS/UEFI updates.

For example the timings seem correct but ProcODT, RTT, and CAD_BUS options don't match what I set in the BIOS/UEFI.

Edited June 26, 2019 by A Computer Guy

[Gronar]

Thanks for the link, did some research there and spent some time with DRAM calculator for Ryzen after pulling all the RAM info with Typhoon. Currently I've used all the settings the calculator gave me and slowly pushed it up to 3000 and things are running good so far, no blue screens or lock ups. I'll probably push it even further over the weekend to see just how far I can go and keep it running stable.

[Gronar]

Thanks for the link, did some research there and spent some time with DRAM calculator for Ryzen after pulling all the RAM info with Typhoon. Currently I've used all the settings the calculator gave me and slowly pushed it up to 3000 and things are running good so far, no blue screens or lock ups. I'll probably push it even further over the weekend to see just how far I can go and keep it running stable.

 

Ran the system a whole day at 3066 and it was stable even through a marathon gaming session last night so this morning I pushed it up to 3133. Tested with playing a game and had no problems. Will keep it at this speed for today to confirm stability then push it to 3200 tomorrow.

[A Computer Guy]

So far here are the best timings I managed to get with my RGB memory kit.

 

This got me a score of 113% on UserBenchmark.com.

 

The best score I got was 114% at 3266 however after another BIOS update to P3.30 that frequency became unstable so I had to back down to 3200.

 

Compared to many other users this seems to be near the top end score for this memory kit at 3200.

https://ram.userbenchmark.com/SpeedTest/587593/Corsair-CMW32GX4M2C3200C16-2x16GB

 

Hopefully this will be helpful to other Ryzen users with this memory kit trying to get the best out of it.

 

(with Ryzen 5 2600)
CMW32GX4M2C3200C16 (ver 4.32)
DDR4-3200
18 - tCL   (from XMP 16+2)
17 - tRCD  (from XMP 18-1)
17 - tRP   (from XMP 18-1)
36 - tRAS  (from XMP)
58 - tRC   (from XMP 54+4)
 6 - tRRDS (from XMP)
 9 - tRRDL (from XMP)
34 - tFAW  (from XMP 36-2)
 4 - tWTRS
12 - tWTRL
12 - tWR
 4 - tRDRDSCL
 4 - tWRWRSCL
512 - tRFC  (down from 560) 
380 - tRFC2 (down from 416) 
234 - tRFC4 (down from 256) 
18 - tCWL
10 - tRTP
 6 - tRDWR
 3 - tWRRD
 1 - tWRWRSC
 7 - tWRWRSD
 7 - tWRWRDD
 1 - tRDRDSC
 5 - tRDRDSD
 5 - tRDRDDD
 8 - tCKE

DRAM = 1.35v
SOC = 1.012v (SOC OVERCLOCK VID = 54)
Gear Down Mode = Enabled
Power Down Mode = Disabled
BGS = Disabled
BGS-ALT = Enabled
ProcODT = 60 ohms
RTT_NOM = RZQ/7(34)
RTT_WR = RZQ/3(80)
RTT_PARK = RZQ/1(240)
CAD_BUS = All 24 ohms

 

(updated 7/12/2019)

Up to 116% https://www.userbenchmark.com/UserRun/18346006

 

(at the time of this post I was using Ryzen 5 2600)

Edited October 30, 2019 by A Computer Guy

[A Computer Guy]

New timings that should work for with a Ryzen 7 3800x.

 

Currently testing these timings....working w/ BIOS/UEFI P3.30.

 

CMW32GX4M2C3200C16 (ver 4.32)
DDR4-3200
18 - tCL   (from XMP 16+2)
17 - tRCD  (from XMP 18-1)
17 - tRP   (from XMP 18-1)
36 - tRAS  (from XMP)
58 - tRC   (from XMP 54+4)
 6 - tRRDS (from XMP)
 9 - tRRDL (from XMP)
34 - tFAW  (from XMP 36-2)
 4 - tWTRS
12 - tWTRL
12 - tWR
 4 - tRDRDSCL
 4 - tWRWRSCL
512 - tRFC  (down from 560) 
380 - tRFC2 (down from 416) 
234 - tRFC4 (down from 256) 
18 - tCWL
10 - tRTP
 6 - tRDWR
 3 - tWRRD
 1 - tWRWRSC
 7 - tWRWRSD
 7 - tWRWRDD
 1 - tRDRDSC
 5 - tRDRDSD
 5 - tRDRDDD
 8 - tCKE

DRAM = 1.35v
SOC = 1.012v (SOC OVERCLOCK VID = 54, did work with AUTO as well)
SOC now located in Advanced/CBS/NBIO/XFR
Gear Down Mode = Enabled
Power Down Mode = Disabled
BGS = Disabled
BGS-ALT = Enabled
ProcODT = 60 ohms
RTT_NOM = RZQ/7(34)
RTT_WR = RZQ/3(80)
RTT_PARK = RZQ/1(240)
CAD_BUS = All 24 ohms

 

tCL still won't budge, can't seem to knock it down to 16

tRC still won't budge, can't seem to knock it down to 54

 

(Score with this memory was better with Ryzen 5 2600, this score with Ryzen 7 3800x is lower)

Up to 93.7% https://www.userbenchmark.com/UserRun/18560160

Edited July 27, 2019 by A Computer Guy

[A Computer Guy]

New ASRock BIOS/UEFI version P3.40 w/ AGESA 1.0.0.3AB showed some improvement.

New timings that should work for with a Ryzen 7 3800x.

 

CMW32GX4M2C3200C16 (ver 4.32)
DDR4-3200
16 - tCL   (from XMP 16)
17 - tRCD  (from XMP 18-1)
17 - tRP   (from XMP 18-1)
36 - tRAS  (from XMP)
58 - tRC   (from XMP 54+4)
 6 - tRRDS (from XMP)
 9 - tRRDL (from XMP)
34 - tFAW  (from XMP 36-2)
 4 - tWTRS
12 - tWTRL
12 - tWR
 4 - tRDRDSCL
 4 - tWRWRSCL
512 - tRFC  (down from 560) 
380 - tRFC2 (down from 416) 
234 - tRFC4 (down from 256) 
16 - tCWL
10 - tRTP
 6 - tRDWR
 3 - tWRRD
 1 - tWRWRSC
 7 - tWRWRSD
 7 - tWRWRDD
 1 - tRDRDSC
 5 - tRDRDSD
 5 - tRDRDDD
 8 - tCKE

DRAM = 1.35v
SOC = 1.016v (SOC OVERCLOCK VID = 54, did work with AUTO as well)
SOC now located in Advanced/CBS/NBIO/XFR
Gear Down Mode = Enabled
Power Down Mode = Disabled
BGS = ??? could not find setting with new BIOS/UEFI
BGS-ALT = ??? could not find setting with new BIOS/UEFI
ProcODT = 60 ohms
RTT_NOM = RZQ/7(34)
RTT_WR = RZQ/3(80)
RTT_PARK = RZQ/1(240)
CAD_BUS = All 24 ohms

 

tCL has been fixed but tRC still won't budge, can't seem to knock it down to the original XMP value 54.

[A Computer Guy]

Had a surprise with ASRock BIOS/UEFI version P3.40 w/ AGESA 1.0.0.3AB.

 

I was able to bump up from 3200 to 3600 (couldn't do that before) so there seems to be an improvement. UserBenchmark went up from 93.7% to over 100%

 

(...still working on trimming the timings below...will edit when finalized...)

(...updated 7/29/2019...)

 

CMW32GX4M2C3200C16 (ver 4.32)
DDR4-3600
18 - tCL
19 - tRCD
19 - tRP
42 - tRAS
68 - tRC
 6 - tRRDS
 9 - tRRDL
32 - tFAW
 4 - tWTRS
12 - tWTRL
12 - tWR
 4 - tRDRDSCL
 4 - tWRWRSCL
560 - tRFC
??? - tRFC2
??? - tRFC4
18 - tCWL
 6 - tRTP
 8 - tRDWR
 3 - tWRRD
 1 - tWRWRSC
 7 - tWRWRSD
 6 - tWRWRDD
 1 - tRDRDSC
 5 - tRDRDSD
 4 - tRDRDDD
 0 - tCKE

DRAM = 1.35v
SOC = 1.1v (with AUTO)
SOC now located in Advanced/CBS/NBIO/XFR
Gear Down Mode = Enabled
Power Down Mode = Disabled
BGS = ??? could not find setting with new BIOS/UEFI
BGS-ALT = ??? could not find setting with new BIOS/UEFI
ProcODT = 60 ohms
RTT_NOM = Disabled
RTT_WR = RZQ/3(80)
RTT_PARK = RZQ/1(240)
CAD_BUS = All 24 ohms

 

The new Dram Calculator 1.6.0 doesn't seem to work in my scenario. It won't calculate DDR4-3600 settings says "not supported".

 

Up to 104% https://www.userbenchmark.com/UserRun/18880711

Edited July 31, 2019 by A Computer Guy

[A Computer Guy]

Using AIDA64 going from my previous DDR4-3200 to DDR4-3600

read improvement +5,580

write improvement +3,391

copy improvement +5,386

latency from 77ns down to 71ns

 

I don't have any data to compare against. If someone else out there has a 3800x and this memory kit do you get similar results?