PBO issues on ASRock B650 PG Lightning

[Mayonnaise]

I'm currently using an ASRock B650 PG Lightning with a Ryzen 7 9800X3D, and so far I've set an undervolt (-30/-40mV per-core) and custom thermal limit (89C) and +200 boost, though I'm running it at the stock clock right now. No issues so far with the PBO power limits set to 'Auto' or 'Motherboard' in the bios, though the same can't be said for when I try to set custom values.

As soon as I try to set any custom values, be it the stock values for 120, 105, 65w TDP, or motherboard limits, Windows simply just takes forever to boot, and I can't even reach the login screen. To see if it was a problem with Windows, I then tried to boot into Debian Linux, which also took forever, but I was able to get into the desktop. When I did check the system readings using btop, the cpu under load seemed to be running at a maximum of no more than 600MHz.

Under normal operation (with PBO set to anything but manual, or turned off), no apparent issues with instability, temperatures, etc.

This seems to be some kind of firmware issue, I'm currently using version 3.16 which is the latest non-beta version. Recently I've seen news of burning issues with the 9800x3d in ASRock boards specifically, so this otherwise just weird bug is causing me some great concern. Has something similar happened with anyone else with an ASRock + 9800x3d combo?

 

[sethmatrix7]

You could try setting the BIOS to default and then tuning PBO.

 

[Mayonnaise]

You could try setting the BIOS to default and then tuning PBO.

I did reset the bios due to a different issue, the Resizable BAR option not showing up in the advanced PCIe settings section. To be fair it did fix whatever setting was causing problems with Re-bar, but the behaviour with custom PBO limits is still the same.

 

[Zach_01]

I'm currently using an ASRock B650 PG Lightning with a Ryzen 7 9800X3D, and so far I've set an undervolt (-30/-40mV per-core) and custom thermal limit (89C) and +200 boost, though I'm running it at the stock clock right now. No issues so far with the PBO power limits set to 'Auto' or 'Motherboard' in the bios, though the same can't be said for when I try to set custom values..

That is not very clear…
Do you use CurveOptimizer with -30 steps or a core voltage offset of -40mV?
Or both?

I’m asking because setting CurveOptimizer to negative with 30 magnitude is equal to -90~150mV on the V/F curve.

Also, PBO set to “Auto” is equal to Disabled.
PPT/TDC/EDC limit expansion occurs if you set PBO to “Enabled” or in Advanced mode for board or manual limits.

 

[Mayonnaise]

That is not very clear…
Do you use CurveOptimizer with -30 steps or a core voltage offset of -40mV?
Or both?

I’m asking because setting CurveOptimizer to negative with 30 magnitude is equal to -90~150mV on the V/F curve.

Also, PBO set to “Auto” is equal to Disabled.
PPT/TDC/EDC limit expansion occurs if you set PBO to “Enabled” or in Advanced mode for board or manual limits.

Yes, I'm using curve optimizer, settings show up in the Ryzen Master print I added.

Also, yes I just wanted to say that everything's normal when the PBO limits are set to whichever of these other options, and the issue only occurs specifically when I try to set custom values (even if they are the same as the default stock values).

 

[Zach_01]

As soon as I try to set any custom values, be it the stock values for 120, 105, 65w TDP, or motherboard limits,

I also don’t understand what does this means.

Better state what exactly are you setting on PPT/TDC/EDC for manual.

When TDP is to 120W then PPT is 170W for example

120W TDP = 170W PPT
105W TDP = 142W PPT
65W TDP = 88W PPT

…and TDC/EDC is another story

 

[Mayonnaise]

I also don’t understand what does this means.

Better state what exactly are you setting on PPT/TDC/EDC for manual.

When TDP is to 120W then PPT is 170W for example

120W TDP = 170W PPT
105W TDP = 142W PPT
65W TDP = 88W PPT

…and TDC/EDC is another story

That's exactly what I mean. Stock values for each TDP rating. In my case, when PBO is turned off, or set to 'Auto' limits, PPT = 162, TDC = 120A, and EDC = 180A.

The point is, even if I try to set these same values, which should work fine, as a custom setting, the same issue happens and the CPU runs at 600MHz.

 

[Zach_01]

That's exactly what I mean. Stock values for each TDP rating. In my case, when PBO is turned off, or set to 'Auto' limits, PPT = 162, TDC = 120A, and EDC = 180A.

The point is, even if I try to set these same values, which should work fine, as a custom setting, the same issue happens and the CPU runs at 600MHz.

That is weird indeed.

Have you tried setting manual PPT/TDC/EDC limits but with less magnitude on negative CurveOptimizer? …or no additional boost (+200MHz)?

 

[Mayonnaise]

That is weird indeed.

Have you tried setting manual PPT/TDC/EDC limits but with less magnitude on negative CurveOptimizer? …or no additional boost (+200MHz)?

Yes, I tried leaving all other settings as default/turned off to eliminate other variables.

Funnily enough, if i enable 'eco mode', or 105w mode as the ASRock bios calls in, in the OC Tweaker menu, there seems to be no problem, so maybe just a bug with PBO?

I tried updated to the 3.18.AS02 BIOS version, but the problem persists

 

[adilazimdegilx]

When you are setting manual limits do you set 120, 150 etc? You need to write 120000, 150000 instead.
Same thing happened to me with a Gigabyte B650 and took some time until I realize that is the problem and I'm stupid (It was taking forever to boot as well)
Ignore this if you were inputting correctly. Could be something else.

edit: I'm still stupid

 

[Mayonnaise]

When you are setting manual limits do you set 120, 150 etc? You need to write 12000, 15000 instead.
Same thing happened to me with a Gigabyte B650 and took some time until I realize that is the problem and I'm stupid (It was taking forever to boot as well)
Ignore this if you were inputting correctly. Could be something else.

Wow you were absolutely right. My dumb ass hadn't noticed the fields were in mW and mA, so I had to actually add three zeroes to the right.

I was used to my previous Asus board which had the fields be in normal Watts and Ampere, and I had seen ASRock prints somewhere of the values written like so, so the thought hadn't even crossed my mind. Well, at least it's not bugged, though I'm feeling bad for making my CPU for making it run on only 16W now lol

Edit: not even that, more like 1.6 watts, though it probably has a power floor or something because I'm impressed it even did boot.

 

[adilazimdegilx]

Wow you were absolutely right. My dumb ass hadn't noticed the fields were in mW and mA, so I had to actually add three zeroes to the right.

I was used to my previous Asus board which had the fields be in normal Watts and Ampere, and I had seen ASRock prints somewhere of the values written like so, so the thought hadn't even crossed my mind. Well, at least it's not bugged, though I'm feeling bad for making my CPU for making it run on only 16W now lol

Glad that I helped. And looks like I still cant write correct numbers (I missed 0 in my reply as well)

 

[Zach_01]

When you are setting manual limits do you set 120, 150 etc? You need to write 120000, 150000 instead.
Same thing happened to me with a Gigabyte B650 and took some time until I realize that is the problem and I'm stupid (It was taking forever to boot as well)
Ignore this if you were inputting correctly. Could be something else.

edit: I'm still stupid

Oh wow!
Why AsRock thinks you need such a precision on those settings? mW and mA?
First time hearing this… but good to know.