PState 0 OC work for me with voltage offset in Extreme Tweaker page. Down clocking work for me, I can change High Performance or Ryzen Power Plan to do the same as Balanced. I can have this "setup" on W7 or W10.
This is not the issue.
The issue with PState OC is you can not increase the VID for PState as you require. If you can not change it there then what happens is basically idle/lower states voltage has also changed as we're applying a global voltage offset elsewhere in UEFI options. I have seen at stock my idle in OS on DMM, measuring at ProbeIt VCORE point is ~500-600mV, when on OC I get ~600-700mV. This is minor but read what is the real issue below.
Below issue especially for R7 1700 owners is further exacerbated when a failed boot occurs. What happens on C6H (and we have been told by Asus team on OCN, applies to other vendor boards) is you get extra voltage going through CPU.Case situation
- I set FID in PState 0 to gain 3.8GHz
- I set offset voltage on Extreme Tweaker as I need for OC (~+162mV).
- System does failed boot, AMD CBS page is reset. AMD "coding" apparently not play "nice" with vendor board UEFI.
- Extreme Tweaker is still active with offset voltage mode (+162mV in my case).
As OC mode has reset from UEFI due to AMD CBS reset CPU is in stock mode. The CPU is not using say 11875mV (default VID ceiling for R7 1700 stock PState 0 (ie base clock 3000MHz)). It is also not at base clock whilst in UEFI and PB/XFR is active, so CPU can be at ~1.35V (checked via DMM). Add in the offset which has not reset on Extreme Tweaker page = ~1.5V.
One owner had ~1.8V go through his CPU = borked chip, he fails to be able to use it at stock clocks, he needs to under clock it.
Some have had ~1.6V go through CPU.
I have had ~1.5V, about ~4x.
On 1700X/1800X PState 0 has ceiling VID of 1.35V, most need say ~+50mV to gain 3.8/3.9GHz, so on a failed boot it's not a biggie for them.
AMD allowing PStates editing is great idea better than what I had on my i5/Z97. But that had better implementation of offset, so I didn't really need State editing.
Now see how my i5/Z97 was.
The 0.001V only applied to all states lower than max, so CPU was basically getting default voltage, then final state got override of 1.254V+0.001V = 1.255V .
My current fix is to use "Sleep" on system, as then it does not need to do whole repost, so I have had no "borked" boot past 2 days.
Some can not use "Sleep" , as workaround or just for normal use, as they get CPU/board issues (which it is I do not know).
Then on C6H UEFI past 0902 we have "improved" SIO CPU Sensor mode. Super IO CPU Sensor reads tCTL and it applies +5°C to it. This then places my fan profile out of "skew".
I disable Sense MI Skew in UEFI, this gains me realistic CPU temps on R7 1700. But then as SIO CPU Sensor reading is used by fan profile it goes to "pot". As UEFI has no option to change SIO CPU Sensor mode I need to use an application that Elmor supplied to change SIO CPU Sensor mode to just using tCTL and not adding +5°C to it.
This application needs to be in OS startup as a reboot will reset SIO mode. This also needs to be in Windows Task Scheduler so on resume from "Sleep" SIO mode is as I want.
Now let's go back to "X" CPU.
AMD state +20°C for tCTL. I have explained some "magic" the SIO chip does, now look at this post
. So we can have further enhanced "tCTL" operation.