Ryzen P-States info & ASRock Mainboard updates

Thanks for that.

I already attributed it to the 116Mhz BCLK. Either something glitched out (internal CLK maybe, but that usually causes a crash) causing that reading or he has a different board than he says he has since the X370 Killer SLi/ac does not have an external BCLK.

It's the Killer SLI without AC. It didn't happen again, however system usage was different. Then again, must be a fluke reading.
Ungari: At stock settings HWInfo will log the highest clock for each core. When each core will hit XFR it will show up like that( all cores at 3.75GHz at stock R7 1700). That's the maximum frequency tab.
I was just hoping XFR was possible at non-stock frequencies. That would have been nice.
Since I've got nothing to loose, I'll keep at it.

XFR should only boost a single core.
Also, it's shutoff whenever OC State is automatically engaged by changes to clock/P-States.
BTW I have a Killer/SLI ac.
There is a way to activate XFR in OC if you are interested, but it is risky without a voltage cushion overhead.

Well XFR does it only on one core. Let assume core 0 gets XFR, after 2 minutes core 1 gets XFR, and so on. If a hardware monitoring tool is used, then it will log the maximum frequency for each core individually no matter when each core reached XFR.

Yes, i'm interested in how to enable XFR in OC. Please do tell! ( I'm drooling over here)

For overclocking purposes the engineers at AMD have included a special mode (the "OC Mode"), which will disable all of the limiters, voltage controllers and protections (except the CPU thermal protection) upon the activation.

The "OC Mode" is automatically activated when the user raises the base frequency (P0 PState) of the CPU. The SMU indicates the activation of the "OC Mode" by sending "0C" code to the diagnostic display (Port 80) of the motherboard.

Understanding the different CPU frequency states (PStates), their voltages and especially the actual effective voltage is harder than ever before with Zeppelin. Unlike with the older designs (15h family) the boosted PStates (Turbo & XFR) are completely invisible.

Due to that fact, they are officially called as "Shadow PStates". This means that unlike with the previous designs these PStates are not defined in the standard MSR registers and cannot be modified (or be seen) by the user. The only way the user can even verify their presence is to see them actually firing (i.e. from the actual effective frequency & voltage).

Understanding the voltages specified for the standard PStates can be confusing as well. That's because in the normal operating mode (i.e. "non-OC") the SMU controls the voltages automatically through the voltage controllers.

For example, the P0 PState might specify 1.37500V voltage, while the actual effective voltage during the residency in this state is 1.26250V or slightly higher. This is not a glitch, but the normal operation of the CPU. Basically, the voltage specified in the MSR is just the upper limit and the SMU will automatically add a dynamic negative offset to this value, reducing the actual effective voltage. The amount of the negative offset varies depending on load and the temperature. For the tested sample the offsets were -120mV & -144mV for the two highest base PStates (3.6 & 3.2GHz).

When the "OC Mode" is activated the SMU will disable the voltage controllers, which among other things disables the automatic voltage offsets. This can create an illusion that the power consumption is heavily increasing due to the use of "OC Mode". While technically it is accurate, it is more of a consequence than the actual reason. A vast majority of the increased power consumption comes from the now disabled automatic negative voltage offsets, which causes the actual CPU voltage to increase anything between 50 and 150mV. Because of this behavior, it is advised that the user doesn't increase the CPU voltage right away (when overclocking), but only upon actual demand (as usual).

One of the major down sides of the "OC-Mode" is that upon activation both Turbo and XFR will be disabled as well. Basically, this means that unless you are able to reach at least the default MSCF / XFR frequency on all cores, then you will essentially be losing single threaded performance compared to stock configuration.

Since XFR apart from LLC can and will call for higher voltage spikes up to 1.475v, it is important to be running below this with enough headroom to absorb it. This is assuming that it will boost the same amount from stock voltage which I do not know. The other problem is the voltage offsets which if not accounted for could be dangerous.
Personally, while I'd like an extra 50-100Mhz on one of the cores above manual overclock, I do not feel it is worth the chance of overvolting, especially since the ranges on the LLC are unclear. I should contact AsRock and ask.
You should check in with the guys on this thread who have experimented with this:

The 2.3 BIOS is here. For Taichi and Gaming K4

Now with compatibility and OC improvements.


You seem to follow these things so Taichi vs Professional Gaming BIOS, are these identical and would I in a sense just pay more for actually getting hardware?

I'm starting to reach to the end of my infinite patience.. :cold_sweat:

The X370 Professional Gaming and X370 Taichi are literally almost the same board. Only difference being ethernet and some header IO. But the Taichi's BIOS is updated much earlier/frequently.
Mainly because it's the board all the reviewers got.



1 Like

In terms of bios and overall build quality they are pretty much the same.
The professional gaming has some additional feutures which might or might not be worth the additional cost based on personal preference.

I just wanted to add this information to this list. It is an external link to voltages and frequencies using p-states



I already know these, because reading hex is natural to me.
But reposting here for better visibility.

HEX Values for P State Overclocking on 22nd of March (by mysticjbyrd on asrock forums)

FID Frequency multiplier (Clock Speed)

90 - 3600mhz
91 = 3625
92 = 3650
93 = 3675
94 = 3700
95 = 3725
96 = 3750
97 = 3775
98 = 3800
99 = 3825,
9a = 3850
9b = 3875
9c = 3900
9d = 3925
9e = 3950
9f = 3975
a0 = 4000
a1 = 4025
a2 = 4050 --> Be honest with yourself.
a3 = 4075
a4 = 4100
a5 = 4125
a6 = 4150
a7 = 4175
a8 = 4200
a9 = 4225
aa = 4250
ab = 4275
ac = 4300
ad = ugh you win the lottery.

Values for DID (Increment adjustment adjuster and or bclk adjustments

8 = 25 mhz increments (The default value)
9 =22.2196
a = 20
b = 18.18
c = 16.667
d (final recommendation) = 15.384mhz - 3943mhz cap).

Values for VID Voltage Control

30 = 1.25v
2f = 1.256v
2e, 1.2562v
2d = 1.268
2c = 1.275v
2b = 1.2812v
2a = 1.287v
29 = 1.293v
28 = 1.3v
27 = 1.3062v
26 = 1.3125v
25 = 1.318v
24 = 1.325v
23 = 1.3312v
22 = 1.3375v
21 = 1.343v
20 = 1.35v -->Common 3.8Ghz stable voltage, some can go higher/lower
1f = 1.356v
1e = 1.3625v
1d = 1.368v
1c = 1.375v
1b = 1.3812v
1a = 1.3875v
19 = 1.3937v
18 = 1.4v
17 = 1.406v
16 = 1.4125v
15 = 1.418v
14 = 1.425v
13 = 1.4321v
12 = 1.4375v
11 = 1.443v
10 = 1.45v
next set is from f - a, 9 - 9 (1.45 - 1.55v), though be very careful overclocking in this voltage range.

is the asus rog ch6 supporting 3200 cl14 yet...

For some reason, my Ryzen Master is always blurry and washed out! I just don't get it! I know early adopters should take their woes with them to the bathroom and flush em with all the rest but jeez this is annoying.

Ok no Idea why it's blurry. That looks like a windows desktop compositing glitch of some sort.

As for the application, it's worth mentioning that you're currently on a read-only profile mode and need to select on of the bottom numbered tabs to create a profile.

Looks a bit like what happens for transparent moving gifs which I guess is because of colors, so I would check if colors are ok

Actually your Ryzen Master seems to be missing black & transparency

I found this information from Asrock forums. Here is the link



Pstate OC is bugged currently, or not fully implemented.

You can only change FID on pstate0 and leave the rest on auto, and then use Vcore offset in main UEFI page to increase the core voltage (if default is not enough).

Any change in VID and/or DID on pstate0, and you end up with full OC or pstate1 in Windows.

1 Like

Running mine like that and its just staying max clocks till I leave PC to be and then it goes to lower clocks, then HWMonitor starts to log lower numbers like I think it has been visiting 100MHz?~

Core power seems to adjust but I dont remember if that was happening without p-state oc

Been wondering if moving stock numbers one row down and then doing that state 0 for OC would be any different for just browsing and stuff like that