Ryzen 3600x temperature

[Zach_01]

Thank you man, really appreciate.
TBH now I'm perfect fine with my temps.

But now I have another question. I'm not an overclocker (quite opposite I'd say) but I want maximum from my rig even stock. So today I've read this post by Chrispy_ and suddenly I'm interested. Messing with RAM seems doable if you know what are you doing.
So this is my RAM
View attachment 142715

And this is DRAM Calculator (didn't find Hynix J-Die so I choose Hynix CJR) Safe values 3600.
View attachment 142716

Can I test them from Windows somehow or I must fill this endless BIOS pages?
View attachment 142717

Also CJR is not J-Die so can I trust those values?

Any advice is appreciate like always.

Before you tell calculator to produce values (Safe or fast), first you hit the purple button to read XMP.

You don’t have to change all settings, just the main ones. The first 5 that called “primary” in your UEFI. Best way is to disable XMP, manually set DRAM speed, voltage and primary timings.

 

[burebista]

Yay, basically that's how I want to do it but wasn't sure.
I just read today that better than hit that Read XMP button is to export XMP profile and import it in DRAM Calculator.

Thanks again man, you really-really helped me.

 

[Chrispy_]

I saw your PM; That Kingston kit is Hynix JJR which isn't in the calculator and it's newer but also reportedly not as good as CJR, so you may have to loosen sub-timings if the CJR timings spat out by the Ryzen DRAM calculator aren't stable (or just stick with a 3600 speed on loser timings and be happy that your Infinity Fabric is running at its full, AMD-supported speed)

If you want to understand timings in more detail, this is a good summary that covers almost everything I know:

What Are Memory Timings? CAS Latency, tRCD, tRP, & tRAS (Pt 1)

This content hopes to define memory timings and demystify the primary timings, including CAS (CL), tRAS, tRP, tRAS, and tRCD. As we define primary memory timings, we’ll also demonstrate how some memory ratios work (and how they sometimes can operate out of ratio), and how much tertiary and...

www.gamersnexus.net

16-18-20-20-36 may well work, in which case good luck trying the secondary timings and potentially if that's all stable and you want more, try the fast preset.

If you can't get your JJR kit stable on CJR timings, give 16-19-19-19-39 a shot.

 

[burebista]

Thank you Chrispy.
OK, for start this is how it looks now in AIDA64.


And this is what DRAM Calculator shows me with CJR selected and XMP imported via Thaiphoon.


What should I expect if I find some stable timing at 3600? Better latency? Read/write/copy? Nirvana?

 

[Chrispy_]

Thank you Chrispy.
OK, for start this is how it looks now in AIDA64.
View attachment 142808

And this is what DRAM Calculator shows me with CJR selected and XMP imported via Thaiphoon.
View attachment 142809

What should I expect if I find some stable timing at 3600? Better latency? Read/write/copy? Nirvana?

 

[Zach_01]

Thank you Chrispy.
OK, for start this is how it looks now in AIDA64.
View attachment 142808

And this is what DRAM Calculator shows me with CJR selected and XMP imported via Thaiphoon.
View attachment 142809

What should I expect if I find some stable timing at 3600? Better latency? Read/write/copy? Nirvana?

Same speed, lower timings improve (lower) latency the most and could improve (higher) slightly the bandwidth (read, write, copy).
Those numbers are pretty low and the latency high. Is your Infinity Fabric, Memory controller and RAM synchronized?

 

[Chrispy_]

If you manage to get it running at 3600 CL16 then you have three main benefits:

1) You'll have 12.5% more memory bandwidth for any applications where memory bandwidth was the bottleneck. Video editing loves bandwidth.
2) Your memory latency will be 12.5% lower, which will make a significant improvement to general performance; Anything that's not cached is usually bottlenecked by RAM latency.
3) The Infinity Fabric is 12.5% faster, I think the 3600X has two CCX with three active cores per CCX, and the CCX communicate with each other over the I.F. Even ignoring the RAM speed altogether, this a 12.% increase in the speed at which different parts of your CPU talk to each other, and this is by far the most important factor of setting RAM to 3600 on Zen2.

Minimum framerates in gaming are generally caused by internal bottlenecks where game engine instructions are running on multiple cores in different CCX. If something running on Core 1 in CCX1 needs to fetch data from an L2 cache on Core 4 in CCX2, the speed of the I.F. is a huge factor in the time this data fetch takes. In an ideal operating system, the scheduler would make sure that all game threads of a similar type that might share cache data are run on neighbouring cores of the same CCX. In reality it's completely random so your I.F. speed makes a significant difference to gaming performance.

It may only improve your average framerates by 2-4% but your minimum framerates should see a pretty significant boost.

 

[burebista]

@Zach_01 . Dunno what to say. I didn't touch BIOS other than setting XMP profile for memory.
Hwinfo says IF 1600, mem is 3200 so I guess they're synced.

@Chrispy_ Many thanks for explanations. Friday I have a day off so I have in plan to play with memory.

 

[moproblems99]

So I want to know if it's something wrong or those are usual temps for Ryzen on air cooling.

Normal. You might be able to get uefi settings in there to smooth it out some but that is pretty normal.

That's because I didn't stop/start HWInfo64 between testing. It's the same window for all. I wanted to see in realtime what's happening between changing offset.

OK, now Cinebench R20 2 runs/settings.
Stock: 3732/3730
-0.05V: 3684/3662
-0.1V: 3120/3107

So it looks like indeed CPU frequency is dropping.

Changing my LLC allowed me to drop volts and gain hz. If I tried to undervolt via offset, I lost clocks and performance.

 

[eSeTech]

Hi,

I've assembled gaming PC's for 10 years, and I found a defective heat sink, yes the metal piece can be defective so it’s not doing its job fine, also the CPU can be defective. You shall replace them if you don’t see any clues.

Cheers!

 

[burebista]

@moproblems99 Thanks man, but unfortunately I don't have LLC in BIOS so I decided to leave CPU alone, it works pretty well out of the box.
Now I'm focused on memory.

Speaking of that, it's embarrassing but I must say it. Yesterday evening before going to bed I've tried to bring memory at 3600.
Maybe I'm rusty, maybe I'm dumb or maybe I've overlooked something (hoping for the latter lol) but it doesn't work.
What I did. Clearing XMP profile, save-exit. Back to BIOS memory is now 2400, Vdimm 1.20V and default timings. Changed frequency to 3600, changed only primary timings (16-19-19-19-38), Vdimm 1.35V save-exit and...black screen, no boot.
After 3 tries MB loaded default and now I'm square one with 2400, 1.20V and all that jazz.

What I'm doing wrong? Bad timings? Should I mess with voltages too?

 

[jermando]

What's your RAM die type? You can try 1.40V

 

[burebista]

I have a picture attached a couple of posts ago.

 

[moproblems99]

I have a picture attached a couple of posts ago.

I have to go north of 1.4V for mine. You can also try to force 1.1v for soc.

Edit: LLC is load line calibration by the way. I would think you have it.

 

[Chrispy_]

Reports on Reddit/Slack/Forums seem to indicate that Hynix-JJR *should* work at 3600 16-19-19-19-39 but it's still overclocking so not guaranteed.

I assume you've also tried using the V2 profile and Manual Profile in the calculator? V1 is for premium grade RAM. V2 is for mainstream RAM, and Manual is for stubborn RAM that doesn't want to overclock.

I had an Asrock B450M that wouldn't overclock RAM using secondary timings on Auto - it was easy Samsung B-die, too - so the issue was definitely the board/BIOS because manually inputting secondaries got it stable again. I would suggest you try inputting the secondaries at least once to see if that helps.

Failing that, it may be that your RAM just isn't a good sample. As a last-ditch effort to run at 3600, use 3733 (Manual profile) with SAFE timings from the calculator for RAM that's actually still set at 3600 operation. If that doesn't work your RAM may simply be incapable of 3600

At 3600 18-18-20-20-40, you're getting the same memory latency (in nanoseconds) as 3200 CL16 as per the XMP settings. If you don't get 3600 timings tighter than that you probably need to give up on that kit.

 

[burebista]

Many thanks again man.
I've used Manual profile because I've imported Thaiphoon report into DRAM Calculator.
I even manually input Primary and Secondary timings in BIOS but with Vdimm 1.35V. No luck.

But I did a step forward. 3600 16-19-19-19-39 Vdimm 1.4V and boot into Windows. YAY!


AIDA Mem benchmark numbers are up and latency down. YAY!


Ran TestMem5 and 4 errors in 30 seconds then BSOD. Booo!
Just two more questions.
SoC voltage is Auto now with 1.072 value in BIOS. Should I raise it to 1.1V and maybe I'll pass TestMem5? If yes 1.1V is safe for long term?
1.4V is safe for daily use for memory?

 

[jermando]

Yes, 1.1V is safe for the SoC/NB part. 1.4-1.45V should be safe for the RAM, maybe with some additional cooling/decent airflow.

 

[Chrispy_]

I agree with Jermando. 1.45 should be okay for the RAM with a Noctua DH-15 moving a lot of air around the socket area.

C16 is really valuable at 3600. If you can't find a way to get it stable at 3600, try dropping to 3533 with the same timings. the I.F. won't be quite as fast but 3533 CL16 is still better than 3600 CL17 and much better than the 3200 you were running before.

 

[Zach_01]

I agree with both @jermando and @Chrispy_, for ZEN2 1.1V SOC voltage is considered normal value. Up to 1.25V (only if it is required, I doubt it is) is considered safe.
And 1.45V for ram with some air flow...

Other voltages that could affect DRAM and InfinityFabric when raising clocks to 1800MHz or higher are the cLDO VDDP and cLDO VDDG. These voltages are related to UMC (Mem Controller) and InfinityFabric. You can see them in RyzenMaster.

 

[burebista]

If you can't find a way to get it stable at 3600, try dropping to 3533 with the same timings.

Great idea man.
I wasted a couple of hours today messing with my RAM.
First 20 minutes were flawless. Raised Vdimm to 1.4V and frequency to 3533. Nothing else changed in BIOS.
TestMem5 with 1usmus config was nice with me.

Aida64 looks pretty good too.


That was encouraging to try for 3600. Two hours later I give up. Cannot reach 3600 with 16-19-19-39 Vdimm 1.42 and SoC 1.12V. I don't want to go higher than that on air for daily use.
Dunno what's holding me back but now I'm pretty happy with 3533 TBH.
So again, a BIG thank you for all who helped me.

 

[Zach_01]

Great idea man.
I wasted a couple of hours today messing with my RAM.
First 20 minutes were flawless. Raised Vdimm to 1.4V and frequency to 3533. Nothing else changed in BIOS.
TestMem5 with 1usmus config was nice with me.
View attachment 143012
Aida64 looks pretty good too.
View attachment 143013

That was encouraging to try for 3600. Two hours later I give up. Cannot reach 3600 with 16-19-19-39 Vdimm 1.42 and SoC 1.12V. I don't want to go higher than that on air for daily use.
Dunno what's holding me back but now I'm pretty happy with 3533 TBH.
So again, a BIG thank you for all who helped me.

Its an improvement anyway...

But how is the voltage now of cLDO VDDP and cLDO VDDG?
RyzenMaster tells...

 

[moproblems99]

Great idea man.
I wasted a couple of hours today messing with my RAM.
First 20 minutes were flawless. Raised Vdimm to 1.4V and frequency to 3533. Nothing else changed in BIOS.
TestMem5 with 1usmus config was nice with me.
View attachment 143012
Aida64 looks pretty good too.
View attachment 143013

That was encouraging to try for 3600. Two hours later I give up. Cannot reach 3600 with 16-19-19-39 Vdimm 1.42 and SoC 1.12V. I don't want to go higher than that on air for daily use.
Dunno what's holding me back but now I'm pretty happy with 3533 TBH.
So again, a BIG thank you for all who helped me.

Make sure you set if to 1767 as well.

 

[burebista]

But how is the voltage now of cLDO VDDP and cLDO VDDG?
RyzenMaster tells...

Like this

Make sure you set if to 1767 as well.

It's linked in BIOS with RAM clock. In load is the same as RAM but in idle is jumping up and down.
Should I put manually 1767?

 

[Zach_01]

Like this
View attachment 143018

Thats odd...

The readings are
VDDCR SOC: 1.0810V
CLDO VDDP: 1.0979V
CLDO VDDG: 1.0979V

This cant be right. Are all these on auto voltage now?
Im asking because cLDO VDDP/VDDG are powered by the SOC line, and since that is 1.081V then those 2 cant be feeded with 1.0979V...

Try this
VDDCR SOC: 1.12V
CLDO VDDP: 1.00V
CLDO VDDG: 1.05V

But check those readings with RyzenMaster again.
And the SOC voltage is in HWiNFO also, check there too.

It's linked in BIOS with RAM clock. In load is the same as RAM but in idle is jumping up and down.
Should I put manually 1767?

Its all right, they are all 3 in same speed as it is. And its normal for InfinityFabric to go up and down in idle.
If you like to keep it as stable as possible then you should set...
CPU Uncore/SOC OC mode: Enabled

 

[burebista]

This cant be right. Are all these on auto voltage now?
Im asking because cLDO VDDP/VDDG are powered by the SOC line, and since that is 1.081V then those 2 cant be feeded with 1.0979V...

Yep, all Auto now. Only Vdimm 1.40V and RAM 3533 are changed in BIOS.
And if I'll try your values will help me where?

And the SOC voltage is in HWiNFO also, check there too.

Yeah, I've identified it and renamed.

If you like to keep it as stable as possible then you should set...
CPU Uncore/SOC OC mode: Enabled

Yeah, I've tried this when I played safe and I first tried 3533 with manual SoC 1.1, Vdimm 1.40 and CPU Uncore/SOC OC mode: Enabled and look what I got.


Maximum Infinity Fabric at 1911 and MEM 1767.