Digital Viper-X-
[H]F Junkie
- Joined
- Dec 9, 2000
- Messages
- 14,260
What does the curve optimizer actually do?
It changes voltage by between 3 and 5 millivolts per step, depending on load. For example, if you set a core to be negative 10 in curve optimizer, it will reduce the voltage by 50mV at idle and 30mV under load.What does the curve optimizer actually do?
Do you use Amd stock Pbo are asus pbo or Pbo 2 ? trying to see the best place to tune atPBO will give you better overall results in the real world. For synthetics all core might yield higher MC results.
I started on - 5 and the computer crashes first minute what am i doing wrong ?It changes voltage by between 3 and 5 millivolts per step, depending on load. For example, if you set a core to be negative 10 in curve optimizer, it will reduce the voltage by 50mV at idle and 30mV under load.
This reduces heat generated if power consumption is capped in PBO and leads to a bit higher clocks. If power usage isn't capped the cores clock much higher until the PB (not PBO) algorithm tells it to stop based on temperatures, silicon quality, and power usage.
So generally, lower heat, less power used, and higher clocks. All good stuff. It's just a bit of a pain in the butt as if you go too low you'll see WHEA errors and reboots, and you want to set your best/second-best and remaining cores to different values.
It changes voltage by between 3 and 5 millivolts per step, depending on load. For example, if you set a core to be negative 10 in curve optimizer, it will reduce the voltage by 50mV at idle and 30mV under load.
This reduces heat generated if power consumption is capped in PBO and leads to a bit higher clocks. If power usage isn't capped the cores clock much higher until the PB (not PBO) algorithm tells it to stop based on temperatures, silicon quality, and power usage.
So generally, lower heat, less power used, and higher clocks. All good stuff. It's just a bit of a pain in the butt as if you go too low you'll see WHEA errors and reboots, and you want to set your best/second-best and remaining cores to different values.
I use PBO2 in the OC menu of MSI Tomahawk.Do you use Amd stock Pbo are asus pbo or Pbo 2 ? trying to see the best place to tune at
At least on MSI you want to NOT use the PBO menu under AMD Overclocking.Yes, set voltage to auto then use CO to individually undervolt each core.
If your CPU crashes at -5 then you might just have poor silicon. It's a gamble. But make sure you're using AGESA 1.2.0.0, it's much more stable.
Generally you want to use the PBO menu under "AMD Overclocking".
1.2 is out. I swear I was checking for it everyday. The site shows release date as of January 26, 2021. LOL.... Give it a go (if you haven't already), I might upgrade my kids PCs on the weekend.Did they release the tomahawk 1.2 bios? Been waiting for it.
thanks man im try when I get home , I updated to AMD AM4 AGESA V2 PI 1.2.0.0 this morning but never tried the curve optimizer this morning , i was on a older bios when i tried. is -5 the lowest setting ? should i try individual cores , I did all coreYes, set voltage to auto then use CO to individually undervolt each core.
If your CPU crashes at -5 then you might just have poor silicon. It's a gamble. But make sure you're using AGESA 1.2.0.0, it's much more stable.
Generally you want to use the PBO menu under "AMD Overclocking".
thanks manI use PBO2 in the OC menu of MSI Tomahawk.
After spending so much time optimizing the living crap out of my PC I am extremely weary of trying out the new bios lol.1.2 is out. I swear I was checking for it everyday. The site shows release date as of January 26, 2021. LOL.... Give it a go (if you haven't already), I might upgrade my kids PCs on the weekend.
Individual cores are better since you can avoid WHEA errors through it. My second best core doesn’t run w/ anything below -10 whereas all other cores are right now functional at -25. Fingers crossed since I still need to wait 3-4 days for that idle WHEA error. Does someone know best way to test for idle WHEA errors other than waiting days lol.thanks man im try when I get home , I updated to AMD AM4 AGESA V2 PI 1.2.0.0 this morning but never tried the curve optimizer this morning , i was on a older bios when i tried. is -5 the lowest setting ? should i try individual cores , I did all core
ahhaha.... I don't blame youAfter spending so much time optimizing the living crap out of my PC I am extremely weary of trying out the new bios lol.
All core is good to start out with to find where to start. If you say do -5 and it's stable, but -10 isnt then start with all cores at -5 and then tweak individually. It's a laborious process and hopefully CTR 2.1 with auto core optimizer will help with that.thanks man im try when I get home , I updated to AMD AM4 AGESA V2 PI 1.2.0.0 this morning but never tried the curve optimizer this morning , i was on a older bios when i tried. is -5 the lowest setting ? should i try individual cores , I did all core
I updated mine to 1.2.0 and my previously stable ram configuration now hangs windows shortly after boot. Need to start over from scratch it seems...:’ and I haven’t gotten to it yet.After spending so much time optimizing the living crap out of my PC I am extremely weary of trying out the new bios lol.
11039 | 620 |
You might be onto something.I have only heard problems with 1.2.0.0 bios on most motherboards. Glad I didn’t indulge thus far. Will wait for the next one. No need to break what’s working.
I have only heard problems with 1.2.0.0 bios on most motherboards. Glad I didn’t indulge thus far. Will wait for the next one. No need to break what’s working.
That’s my understanding as well.I don’t think effective clocks are correct representation of actually what the processor clocks are at a point in time. I just use the top one to monitor my processor clocks.
Ive heard that you have to look at effective , perf is only when you proc hits for a sec , but i think it doesn't work correctlyOK, question, in HWinfo, it shows Effective clock and (perf), which one shows actual clock speed?
Effective clock for me I think has never broken 5ghz, usually 4.8-4.9 is the highest It will go, where as PERF has hit 5.15 on my "best cores"
When running a 1-2 core workload, the effective clocks match what Ryzen master shows, and perf shows a higher number. I am confused
(red = perf)
(yellow = effective)
View attachment 326923
I think the internet has mixed feelings about it. Some people swear by it but others think it's easier to just use PBO. Maybe when 2.1 comes out and it can do auto core tuning.What do you guys think about this program ClockTuner 2.0 for Ryzen (CTR) Guide , The writer of the program seems really knowledgeable , seems like its a program to make gains without taking you out of Amd specifications , " you can change perimeters to overclock if want to
https://www.guru3d.com/articles-pages/clocktuner-2-for-ryzen-(ctr)-guide,1.html
The updated bios (asus hero WiFi 3204) seems to have added another menu for memory settings and voltage. Some of the settings in the main extreme tweaker section don’t seem to work anymore.I updated mine to 1.2.0 and my previously stable ram configuration now hangs windows shortly after boot. Need to start over from scratch it seems...:’ and I haven’t gotten to it yet.
if i had the pbo2 settings dialed in id feel the sameI think the internet has mixed feelings about it. Some people swear by it but others think it's easier to just use PBO. Maybe when 2.1 comes out and it can do auto core tuning.
https://www.reddit.com/r/Amd/comments/ld2qec/chips_and_cheese_ctr_a_review_and_a_warning/
I tried it but I wasn't too confident in it and I felt like I had tweaked my PBO2 settings pretty heavily that I wanted to stay with it.
I personally think the good and bad core is all bullshit. You need to see the core that is throwing a WHEA error and give it more voltage to stabilize (which intuitively also makes sense).
It’s in this thread. And yes if core is not stable you give it more voltage (a lower negative offset). Someone posted about the core ASIC ID in the event viewer. For me it was easy as core ASIC ID was 0.That is what I was thinking, so the core that throws a WHEA error you would give it less negative offset right hence the -10 versus -25 on the rest. How did you identify which core was causing the WHEA error?