Ryzen Owners Zen Garden

[INSTG8R]

I forgot I'm in this garden now very happy with my 3700X/Auros X570 Pro/Corsair Vengence Pro 3600 CL18 i've managed to get down to CL16 with little effort I do intend to get the equivalent Zen 3 This was just getting the base system setup

 

[AsRock]

Good thing I never bothered with XMP after a few tries of it not working. Manual settings are flawless though.

Yeah never worked for my 3900 either.

 

[biffzinker]

XMP has worked for me with 5 different brands of DDR4 on a couple of MSI boards with a Ryzen 3 1200, 5 2600X, 5 3600, and 7 3800X. I turn it off, and do my own adjustments.

 

[INSTG8R]

XMP has worked for me with 5 different brands of DDR4 on a couple of MSI boards with a Ryzen 3 1200, 5 2600X, 5 3600, and 7 3800X. I turn it off, and do my own adjustments.

My trick is to set the profile to get the voltage and subtimings but then manually input the major timings Bad angle but the right is the XMP and the left are my manual settings

 

[tabascosauz]

@Nordic does bumping DRAM voltage change anything? The most infuriating thing about Asus boards is that Asus sees fit to cripple whole swathes of their product line from budget all the way to upper midrange by choosing to report very few coherent sensors through their SuperI/O, so you never know what your DRAM voltage actually is. Whereas even though a Gigabyte board might overvolt DRAM voltage, at least it tells you roughly what V the board is seeing, while Asus straight up doesn't even report it in a transparent way to the user. Might have to play with the Vdram a little bit.

Other than that, it is CJR, so there shouldn't be any hidden surprises beyond what we already know. Like with Gigabyte, Asus still allows you to set DOCP and then customize all timings and voltages to your own liking. I like to do this as there are some boards I don't trust to properly identify their correct tertiaries during bootup, without XMP/DOCP telling them that the RAM isn't at 2133.

 

[Nordic]

Good thing I never bothered with XMP after a few tries of it not working. Manual settings are flawless though.

I have not tried setting the timings manually with the new sticks. I did with the old sticks. That is worth a try.

@Nordic does bumping DRAM voltage change anything? The most infuriating thing about Asus boards is that Asus sees fit to cripple whole swathes of their product line from budget all the way to upper midrange by choosing to report very few coherent sensors through their SuperI/O, so you never know what your DRAM voltage actually is. Whereas even though a Gigabyte board might overvolt DRAM voltage, at least it tells you roughly what V the board is seeing, while Asus straight up doesn't even report it in a transparent way to the user. Might have to play with the Vdram a little bit.

Other than that, it is CJR, so there shouldn't be any hidden surprises beyond what we already know. Like with Gigabyte, Asus still allows you to set DOCP and then customize all timings and voltages to your own liking. I like to do this as there are some boards I don't trust to properly identify their correct tertiaries during bootup, without XMP/DOCP telling them that the RAM isn't at 2133.

I have played with the voltage a bit. What is the maximum safe voltage for ddr4?

 

[tabascosauz]

I have not tried setting the timings manually with the new sticks. I did with the old sticks. That is worth a try.


I have played with the voltage a bit. What is the maximum safe voltage for ddr4?

Have good airflow? 1.45V for CJR daily use. I highly doubt you'll need to set it above 1.4V, though. Shouldn't be that far off.

 

[Nordic]

Have good airflow? 1.45V for CJR daily use. I highly doubt you'll need to set it above 1.4V, though. Shouldn't be that far off.

I have an open air case with a fan blowing towards the ram. I think that is good airflow.

 

[Xzibit]

Anyone have experience with the New AGESA v2 1.1.0.0 yet? Was just posted for my board.

To try or to wait until its final.

 

[Mussels]

*cries in 1.0.0.6*

 

[Toothless]

So, even with voltages cranked up I can't get past validating on 4.625 and benching on 4.6. Looks like I found my limit with the 3700x but man does it fly.

 

[Xzibit]

Updated to AGESA v2 1.1.0.0 bios (Beta) just to check out. About the only thing noticeable is just slight re-organizing of some MSI CPU advance options

At least this board is ready for Ryzen 5000 series now.

 

[Nordic]

Good thing I never bothered with XMP after a few tries of it not working. Manual settings are flawless though.

Have good airflow? 1.45V for CJR daily use. I highly doubt you'll need to set it above 1.4V, though. Shouldn't be that far off.

DOCP speeds and upping the voltage to 1.45v fails. Keeping the DOCP timings and 1.45v and going down to 3200mhz fails. Using the timings from ryzen dram calculator fails. By fail, I mean it won't even post. I don't even get to windows.

I was having better luck with my corsair memory. At least sometimes I could get it to boot at XMP speeds, but only sometimes. I have tried two different motherboards. I have tried two different sets of memory. My CPU must be the problem here.

Spoiler: Dram Info

 

[tabascosauz]

DOCP speeds and upping the voltage to 1.45v fails. Keeping the DOCP timings and 1.45v and going down to 3200mhz fails. Using the timings from ryzen dram calculator fails. By fail, I mean it won't even post. I don't even get to windows.

I was having better luck with my corsair memory. At least sometimes I could get it to boot at XMP speeds, but only sometimes. I have tried two different motherboards. I have tried two different sets of memory. My CPU must be the problem here.

Can you run Zentimings? Latest version shows procODT and minor voltages. https://zentimings.protonrom.com/

Aside from that there's not really anything else I can think of. These GTZNC kits are cutting edge CJR (DJR) and rated for just about as good as CJR G.skill come out of the box XMP (I think so far the CJR 3733 Tridents I've seen are all 17 tCL, could be wrong). And isn't this your second motherboard after the Pro4? It's just the CPU that's stayed all this time.

Do you know the batch code on the IHS of your 3900X (if you took a photo of it at any time)? Seven digits with 4 numbers and 3 letters, either xx19xxx or xx20xxx, on the second line of text, above the 13-digit serial number. I'm guessing it must be a Q3 or Q4 2019 manufacture.

If you only just bought the Tridents, I'd probably return them and try something else. Maybe it's a one-off, or maybe it's that SKU.

 

[TheLostSwede]

DOCP speeds and upping the voltage to 1.45v fails. Keeping the DOCP timings and 1.45v and going down to 3200mhz fails. Using the timings from ryzen dram calculator fails. By fail, I mean it won't even post. I don't even get to windows.

I was having better luck with my corsair memory. At least sometimes I could get it to boot at XMP speeds, but only sometimes. I have tried two different motherboards. I have tried two different sets of memory. My CPU must be the problem here.

Spoiler: Dram Info

First of all, I'd try CAS 16, not 14, as this is Hynix, not Samsung. Also trying increasing the tRFC a bit, as that tends to improve the system stability.
This is what the calculator suggests for my modules at 3600, which clearly aren't as highly binned as yours.

 

[tabascosauz]

@TheLostSwede is right, I completely missed it as I thought the original DRAM calc screenshot was for 3200 @ 14-17-17 which is mediocre but perfectly within the capabilities of CJR.

@Nordic CJR won't be doing 3600 @ 14. This is why I've been telling people for ages to stop trying to import their XMP into DRAM calc. More often than not over the course of DRAM calc's lifetime, when you put your own XMP in it'll outright run into an application fatal error or even worse, spit out nonsensical timings like these. In this case I can already see that RRDS/L/FAW and WTRS/L/WR are all over the place, neither loose enough for safe or tight enough for even remotely fast.

DRAM calc works just fine as a general recommendation for the important timings, when you fill out the boxes to the left and simply click on the safe or fast options, which makes the recommendations consistent and sensible. Any further tweaking to the timings you'll have to figure out on your own anyways.

 

[Nordic]

Can you run Zentimings? Latest version shows procODT and minor voltages. https://zentimings.protonrom.com/

This is on stock default auto settings.

And isn't this your second motherboard after the Pro4? It's just the CPU that's stayed all this time.

Do you know the batch code on the IHS of your 3900X (if you took a photo of it at any time)? Seven digits with 4 numbers and 3 letters, either xx19xxx or xx20xxx, on the second line of text, above the 13-digit serial number. I'm guessing it must be a Q3 or Q4 2019 manufacture.

Correct, I have tried two different motherboards and two different memory kits.
I do not know the batch code on my cpu. I am not inclined to take my cooler off right now.

First of all, I'd try CAS 16, not 14, as this is Hynix, not Samsung. Also trying increasing the tRFC a bit, as that tends to improve the system stability.
This is what the calculator suggests for my modules at 3600, which clearly aren't as highly binned as yours.

I did try running Cas 14 but I also tried higher timings too. I tried a variety of timings. I can give your timings a shot.

Nordic CJR won't be doing 3600 @ 14. This is why I've been telling people for ages to stop trying to import their XMP into DRAM calc. More often than not over the course of DRAM calc's lifetime, when you put your own XMP in it'll outright run into an application fatal error or even worse, spit out nonsensical timings like these. In this case I can already see that RRDS/L/FAW and WTRS/L/WR are all over the place, neither loose enough for safe or tight enough for even remotely fast.

DRAM calc works just fine as a general recommendation for the important timings, when you fill out the boxes to the left and simply click on the safe or fast options, which makes the recommendations consistent and sensible. Any further tweaking to the timings you'll have to figure out on your own anyways.

Dram calculator won't work unless I include all the information on the left. What information am I supposed to include if not for the XMP speeds?

 

[TheLostSwede]

Dram calculator won't work unless I include all the information on the left. What information am I supposed to include if not for the XMP speeds?

He's talking about importing the file from Thaiphoon burner.
Try with A0/B0 instead of manual.

 

[Nordic]

He's talking about importing the file from Thaiphoon burner.
Try with A0/B0 instead of manual.

What is the difference between importing the timings and entering the same values manually?

 

[TheLostSwede]

What is the difference between importing the timings and entering the same values manually?

Well, importing them, you use the data that Thaiphoon burner reads from the EEPROM on the RAM, using the built in settings uses an "average" supposedly working setting calculated by 1usmus. Neither is seemingly perfect. I can run my RAM at tighter timings than suggested, but this seems to be what the tool does at the end of the day, suggest a set of timings that should work. However, it's not flawless and as in your case, it seems like the timings it spits out are a bit off.

 

[tabascosauz]

@Nordic the "PCB revision" box is where you select different profiles based on a perception of the quality of your sticks. A3 is best, A0 is ehhhh, bad bin is the worst (though I don't think CJR has one). Manual is where you would import your XMP from Thaiphoon, or enter by hand. Though or CJR, even the A3 profile is really conservative and shouldn't be a challenge, especially for a 3600@16 rated kit. It looks like our sticks are quite similar, dual rank B1 CJR.

I use this for 3600 and 3733, only changing DRAM voltage and tRFC (471 for 3600). I've gone down to 451 @ 3600 and 468 @ 3733 without problems, but it doesn't bench or perform any differently so I just run 489. On my 4Gb E-die I'm at 350 and can probably flirt with B-die territory, but CJR stays relatively high at a hair under 500 tRFC.



I don't know if there's any merit to trying higher procODT, because I'm pretty sure midrange Asus always defaults to 60ohm for these dual-rank CJR during the training process when DOCP is on (your ATX X570 has a few extra PCB layers but otherwise both TUFs are very similar). Not sure what sort of instability you've been running into, so can't really tell you if upping vSOC and the VDDs will help you. I was running into some IF errors at 3733 because 1.10V SOC would actually droop to ~1.08V so I have to compensate by setting 1.11V in BIOS, but you're only at 3600.

Anecdotally, though, I struggled to get it to pass overnight HCI at 43.6ohms. So maybe for dual rank, Asus' auto-60 does have some value.

 

[Nordic]

Is there a way to see what kind of errors? It won't post so I can't see any codes. Amd doesn't seem to have the same diagnostic tools on their motherboards, so I can't see a boot code. Even the old beep codes do not seem to work

 

[GoldenX]

If you don't get beep codes, something very wrong is going on.

 

[tabascosauz]

Earning one half, consuming one eighth

Is there a way to see what kind of errors? It won't post so I can't see any codes. Amd doesn't seem to have the same diagnostic tools on their motherboards, so I can't see a boot code. Even the old beep codes do not seem to work

No not the debug LEDs, they're next to useless when you know you're already dealing with memory. I was referring to the "trouble" you mentioned earlier you were having when running XMP, whether it's a memory stability issue (that can be uncovered through HCI/TM5/Karhu etc) or a memory controller issue (intermittently freaks out or struggles to boot, interconnect issues in HWInfo, etc.).

 

[Space Lynx]

When I get my Ryzen 5600X, my goal is to OC the core 0 and core 1 the highest it will go and leave everything else at stock. Is this a good plan? I am going to do a small to medium voltage bump since I will have a 360mm radiator AIO by then, my plan is to OC to core 0 to 4.6 or 4.7 or 4.8 and leave rest of cores at stock. so only two things I will change in BIOS will be voltage bump and core 0 frequency

is this a good plan or no? most of the games I play are single core usage only, so I only need to focus on core 0 and core 1 correct?

@TheLostSwede