UPDATE: I will continue to update this post with relevant learnings if I have them and updated results if I'm still tuning. I answered almost every question the first day, but I can't keep up with answering your questions, especially about your individual cases. Please help each other.
I come from many generations of Intel builds. Over the decades, the experience of overclocking Intel roughly translated to pouring voltage into core and maybe some into uncore while raising the multiplier until you hit a ceiling. Overclocking Zen 3 has been a completely different experience, with boost and PBO doing smart things that you want your OC efforts to support and optimize rather than replace.
I've spent many hours over the past four days overclocking both my 5900X and 5600X rigs, and I've learned a lot on the way. I figured I should share some important information with the community.
I included a background section for newbies that many of you might want to skip.
BACKGROUND
Your CPU will algorithmically boost the frequency of its cores depending on workload. For single threaded workloads, it will boost one core, and for multithreaded workloads, it will boost multiple cores. The frequency at which your core(s) will boost is governed by internal limits, such as power, current, voltage, temperature, and likely other factors, but the important thing to understand is that, holding limits constant, your CPU can boost one core to a higher frequency than it can boost multiple cores. This should make common sense to you.
PBO raises the current and power limits that govern your CPU's boost algorithm. You can raise your PBO settings as high as you'd like, but PBO has a hard limit of allowing 105W TDP CPUs to draw ~220W and 65W TDP CPUs to draw ~130W. PBO does not raise your CPU's max boost frequency, which is 4.8GHz stock for the 5900X and 4.65GHz stock for the 5600X, both of which are typically achievable only when the CPUs are boosting 1-2 cores. Practically speaking, enabling and maxing out PBO translates to your CPU boosting clocks during multithreaded workloads until your CPU is drawing ~220W / ~130W.
Auto OC raises the maximum stock boost clock by an offset, up to +200MHz, that you set. For example, a +200MHz offset will raise the stock 4.65GHz boost limit of a 5600X to 4.85GHz. Auto OC does not guarantee your CPU will be able to reach the boost clock under load. All it does is allow the CPU to try, but the CPU boosting algorithm will still take into account all the factors as usual to determine boost.
PBO 2.0 w/ Curve Optimizer: Undervolting is a way of overclocking CPUs and GPUs that have an internal table that maps voltage to operating frequency. Basically, a 50mV undervolt tells a CPU that instead of operating at, say, 2GHz at 1V, operate at 2GHz at 0.95V instead, and whatever frequency is mapped to 1V is now >2GHz. When a Zen 3 CPU is undervolted, this means that the same power limits that govern its boost algorithm all map to higher operating frequencies.
Curve optimizer basically allows you to undervolt each core independently.
GUIDE STARTS HERE
The steps for using Curve Optimizer to OC are:
-
Curve Optimizer is part of PBO 2.0, so enable PBO and set it to your platform's limits.
-
Under PBO, leave the scalar at Auto. Auto performed the best for me, but if you want to try to tweak this, I'll mention when you should do this.
-
In Curve Optimizer, start with an all core undervolt of -5. Iterate between STABILITY TESTING (HIGHLY TRICKY. SEE BELOW.) and lowering this by -5 each time until you find the lowest stable value.
-
Now you know the undervolt limit of at least one of your cores. You can now go into per core undervolting to find which cores you can bring down further using the same iterative method above.
-
You're done. Now's the time to test a custom scalar value if you really wish to.
You will find that undervolting nets significant gains in both single and multithreaded performance. The more you can undervolt, the greater the gains.
AN IMPORTANT COMPLICATION: UNDERVOTING & AUTOOC
The relationship between undervolting stability and your AutoOC setting is critical. Broadly speaking, the more aggressive you undervolt, the more gains you get, but the higher you set your AutoOC offset, the less aggressive you can stably undervolt. This should make sense to you because your cores require more voltage to attempt the higher boost ceiling you specified. Practically speaking, you will likely find that your once stable undervolt setting is now unstable if you raise AutoOC from +0 to +200MHz.
Let's illustrate this relationship using an example. Say you set your AutoOC offset to +200MHz for a CPU with a 4.8GHz boost limit because you want it to boost to 5GHz. However, you find that the best stable undervolt you can achieve now results in a single core boost speed that barely blips to 4.95GHz. At this point, you should lower your AutoOC offset in order to undervolt further so that your undervolt boost can actually achieve what your offset specifies.
On the flip side, say you have a +0 offset, but your stable undervolt has your single core boost pretty much glued to its limit of 4.8GHz. In this situation, you should increase your AutoOC offset and back off on your undervolting until your offset is again equal to the what your undervolt boost can achieve.
EVEN MORE IMPORTANT: STABILITY TESTING
Your Curve Optimized undervolt will not be stable in low power workloads long before it will show any stability issues in any high power workloads, including every single benchmarking tool you use, including Cinebench and Prime95. An unstable undervolt will result in your PC sometimes randomly freezing, restarting, or BSODing when you're not doing much beyond browsing File Explorer or similar tasks.
Finding a low power workload for stability testing undervolting was the primary challenge of this entire process. The best one I found is the Windows 10 Automatic Repair and Diagnosis workload that can happen pre-boot. You can manually trigger this workload by restarting your PC after it posts but before Windows boots two consecutive times. The third boot will automatically start this workload after post.
This workload completing successfully means it will put you into a menu with a Restart option that you can click on to successfully restart your computer. An unstable undervolt can result in a myriad of different things going wrong, including:
-
The PC suddenly reboots by itself before you reach the menu screen.
-
A BSOD at any point in the workload.
-
Making it to the menu and choosing to restart the PC, but then your PC freezes before restarting.
Once you have successfully triggered the Automatic Repair process, your next boot will be normal. However, if you reset your PC during this next normal boot before Windows successfully loads, it will trigger Automatic Repair in your subsequent boot again.
To test stability, I recommend 10x consecutive successful passes of this workload. This involves using the Automatic Repair workload to restart your computer, resetting your computer in the next boot to trigger the workload again, and repeating. I hope your PC has a reset button next to the power switch, because that comes in handy here.
UPDATE
This stability test works most consistently for finding the limits of your top 2-3 cores in terms of priority. You will notice that after finding these limits, you can undervolt your other cores significantly lower while still passing this test. I haven't yet found a reliable, consistent, and reproducible workload to test these other cores beyond just using your PC and waiting for a random restart or WHEA/other BSOD. Others have mentioned their own jury rigged tests in the comments that you can try.
Finally, low power stability testing is in addition to normal high load stability testing via the usual benchmarks. In fact, if you are failing those, then your OC efforts are in an even worse state than those who only fail low load stability.
MY RESULTS
My final results for my 5900X are:
Core 0: -18
Core 1: -5
Core 2: -18
Core 3: -18
Core 4: -18
Core 5: -18
Core 6: -18
Core 7: -18
Core 8: -18
Core 9: -18
Core 10: -18
Core 11: -18
Scalar: Auto
AutoOC offset: +25 MHz (4.95GHz stock boost limit for unknown reasons, so 4.975GHz with offset)
Cinebench R23 results: https://i.imgur.com/BQNcdbk.png
Takeaways:
-
My all core undervolt wasn't stable beyond -5. As you can see, I eventually realized that it was my Core 1 bottlenecking that.
-
My core 1 happens to be my highest priority core. This means my single threaded score is not nearly as impressive as I'd like. Silicon lottery at play here.
-
I only really bothered individually optimizing Core 1, 2, 0, and 5, as those are my highest priority cores. I always tested cores 3 and 4 together and found stability with them at -20. I tested all my second CCD's cores (cores 6-11) in one batch; there may be some optimizations there, but I couldn't be bothered.
-
While my highest priority core could only support a -5 undervolt, my other cores can be undervolted quite significantly, resulting in a pretty impressive multicore benchmark score, IMO.
My final results for my 5600X are:
Core 0: -8
Core 1: -8
Core 2: -4
Core 3: -8
Core 4: -8
Core 5: -4
Scalar: Auto
AutoOC offset: +200 MHz
Cinebench R23 results: https://i.imgur.com/88JXBOh.png
Takeaways:
-
SC boost was glued to 4.85 GHz, which is the maximum allowed.
-
More interestingly, MC all core boost was at 4.6-4.65 GHz, which is basically the stock single core boost of the chip. Pretty impressive.
Videos
Hello
I've always hated overclocking. I'm the kinda guy who likes to play on his computer, not with his computer. I think this is because of bad experiences overclocking FX 8350 and 6700K, I had unbelievable stability issues on those chips. Running prime95 all night just to have the system crash on me 10 mins after concluding my overclock was "stable".
Anyway, I'd like to share my experience "overclocking" my 5900X, and maybe ask for advice from those more experienced than myself.
I started with everything on default settings and I was getting mediocre results. r20 603 single core and 7800 multicore. Those scores were unacceptable to me. I then started to play around with the settings.
Disabling the Asus 'Fmax' option in the PBO settings raised MC by 600 points to 8400, pretty good. Then activating PBO really did almost nothing on auto settings. So I started reading about it and tuning. I ended up setting PPT, TDC, EDC to 185, 125, 170 respectively, accoridng to https://albertherd.com/2020/12/13/my-experience-with-precision-boost-overdrive-2-on-a-5900x/
I set the scalar multiplier to 10X and max boost to 200MHz.
Finally I set the curve optimizer to -10 all core, and behold, I get around 620 SC annd 8700 MC. This is still a bit shy from the advertised 631 SC, so I decided to decrease the curve optimizer in increments of 5 until Cinebench crashes, and then increase it by 5. I decreased it until I reached -30 and my motherboard wouldn't let my decrease it further. I get scores of 629 SC and 8830 MC. Pretty good I think, but maybe it could be better? I've seen people get better results, but I haven't been able to hit higher numbers with other settings.
Max temp during cinebench was 75 degrees, on prime95 I hit max temp 91 on blend.
I believe my settings are stable, I've been running prime95 on blend for about 30 mins so far as of writing this.
I would like to ask if I made some mistake along the way? Should I have done something different? Are my scores any good?
My specs:
5900X
Corsair H115i platinum
Asus TUF x570 Gaming plus wifi
On cinebench my processor hits a sustained clock of 4600 on MC and 4950-4975 on SC, although I have seen it boosting all the way up to 5150 momentarily on one core.
Thanks for all comments and advice!
After applying my co my pc will restart randomly after a couple hours. When running cinebench 23 it does the test completely fine no crashes is there a way i can pin point what core is making it crash? Or am i better off just trying a all core co of -28 or lower?
I did -5 in all my cores and it was stable, then tried to do -15 on all with the occt test to see which cores where the problem, but it shows no issues and as soon as i open any game it crashes. I have a gigabyte b450 motherboard and i am trying to get my temps lower because while gaming it goes up to 85C. Any ideas of what to do? This is my first time doing anything like this.
I've been toying with my new 5900x chip, and have been reading up on the new PBO2 and curve optimizer tool. I'm a bit confused because two of the key settings (I think) seem to be contradictory, being the curve optimizer offset (from 0 to negative 30) or the manual OC boost limit (from 0 to +200 mhz). If I set the boost limit to +200, I'm unable to use a lower (more negative) offset and my pc will crash, I'm assuming due to the lower voltage. Which, in theory, is better to maximize? Would it be more beneficial to set a lower boost (say +100) and a lower curve offset (say -15) versus a higher boost (say +150) and a higher offset (say -5)? I guess my question is, how do I find the balance and / or what is the balance I should be aiming for in PBO2?
So somehow I got a 5900X, and being the enthusiast I am I'm trying to see what kinda of clocks I can get out of this thing.
Now I know how it goes with all core clocks on these. Full load clocks are lower but boost clocks are higher, benifiting games.
But I feel like I'm not getting the results with PBO, or more specifically the Curve Optimizer.
Here are my current settings
PBO Limits = 500/500/500 PBO Scalar = 10X Max CPU boost override = 200Mhz
Curve optimization per core all negative Core1 14 circle Core2 20 Core3 14 star Core4 20 Core5 20 Core5 20 Core7 20 Core8 20 Core9 20 Core10 8 circle Core11 15 Core12 8 star
These values were found by starting high and dropping untill stable on each core individually. Circle and star indicate the best cores as per ryzen master, these also happen the be the ones who's curve I can't change much.
Results at these settings are as follows (note these are with normal background tasks running).
Peak clocks on some cores 5024 5099 5024 others range from 4990 to 4876.
Sustained clocks on Cinebench R20 MC = 4524 @ 82C
R20 SC score = 625, MC = 8705
What do people think? Am I using the curve optimizer wrong? Are there additional settings I should be using to improve results? Maybe my silicon is mediocre?
Hey everyone I finally finished my video guide on how to use PBO2 + Curve Optimizer.
Link is: https://youtu.be/dU5qLJqTSAc
If you want to skip yet another explanation of PBO2 and curve and just get to the meat you can go to 11:02: https://youtu.be/dU5qLJqTSAc?t=662
A few things that I did that I haven't seen much discussion of is comparing two configurations (One with Boost/AutoOC high and one with a bigger curve) and I also show how changing power limits affects your performance/temps and clock speeds.
This is a GREAT video. Explains how to use WHEA to find the bad core, and shows how PPT TDC and EDC can be fine-tuned. Also info on Curve Optimizer.
This is way better than the 'guides' that have been posted over the last few months.
Hands down, I think this might be the best PBO2 / Curve Optimizer Guide to date! Just a small heads up: the current OCCT Beta can also show CPU errors per core, so you dont need to slam into a system crash to find the limits.