BoostTester VS corecycler

I'm talking about loads that generate the highest boost clocks. Something like https://github.com/jedi95/BoostTester

But if you want to find out your CPUs max single core boost, this tool is helpful. Pay attention to the effective clocks in HWInfo64.

However, I'd suggest running /u/Jedi95's BoostTester and seeing how many, if any, of your cores hit 4.4GHz: https://github.com/jedi95/BoostTester/releases

Here is an excellent tool for quickly checking your per core max boost clocks to determine which frequency override works best for your CPU (+75-125MHz for most Zen3 CPUs works best, higher values very often end up clock stretching and reducing performance unless you have a silicon lottery winner.): https://github.com/jedi95/BoostTester/releases

Best way I've found to see if each of your CPU cores are boosting where they should be is /u/Jedi95's boost tester: https://github.com/jedi95/BoostTester/releases

Download /r/Jedi95's boost tester, it has never failed me to get a Ryzen chip boosting as high as it can: https://github.com/jedi95/BoostTester/releases

Enable PBO + AutoOC with Ryzen Master, or (more ideally) set it up in your BIOS in the Precision Boost Overdrive section. Use Boost Tester to run a light workload that will see your CPU hit it's maximum boost frequency on each core. Try AutoOC at +75MHz or +150MHz at first, and test a few frequency override values to see which does best for your particular chip. Just setting this to 200MHz will often result in lower boost clocks, you have to hone in on which one works for your chip.

Go here and grab this program: https://github.com/jedi95/BoostTester/releases

This is a good program for immediately finding out where your boost maxes out on each core: https://github.com/jedi95/BoostTester/releases

getting lucky with the binning and undervolting as much as possible (+1 after last stable known value) (tested in multiple days with corecycler using Prime95 and y-cruncher)

Read the developer's statements from GitHub:

What I learned coming over from Intel is that in addition to stressing full loads on the CPU and memory systems for stability testing is that you also need to test bursty light loads as well. Corecycler uses Prime95 (default), Ycruncher, and Aida (you need to download) to test single core stability. I use OCCT & Prime95 to get a rough idea for a stable all core load, then use Corecycler with Ycruncher to test light loads.

Here's a template version of my Excel worksheet I used during my process. It's critical to tracking all your testing. https://we.tl/t-UHg9gnTNaGThe key is to ONLY test 1 core at a time with CoreCycler (https://github.com/sp00n/corecycler) until it has been validated for 12 hours. If it fails the Y-CRUNCHER test (y-cruncher error, hard reboot/freeze, BSOD) under the parameters shown in that sheet, you need to lower the CO setting on that core by 1-2 and test again until it passes for 12 hours.You want to also make sure to keep an eye on Windows Event Viewer to see if the core you are testing is producing any WHEA errors as well. That will alsocount as a FAILED validation run, and you'll need to lower it 1-2 and restart testing in Y-Cruncher again.Once it's passed for 12 hours, mark that core/line green on the sheet, 0 it out again in BIOS, and move onto the next one.Here's my CoreCycler config file. It's already setup to start at Core 0, 720m, y-cruncher, 2 threads, with all the correct testsselected. https://we.tl/t-gK3fc40BR1

You can test it extensively with corecycler ( https://github.com/sp00n/corecycler) with y-cruncher set as the stress tester.

Not all cores are equal. You could try Curve optimiser per core, test with Corecycler. Someone made an automated tool for it. Link