ZenStates-Linux package recommended here is dated and no longer maintained, there is a much better fork at https://github.com/irusanov/ZenStates-Linux that comes with optional gui, manual OC, PPT, TDC, EDC support. P-state overclocking provided by the original package does not affect newer zen+ and beyond cpus with turbo boost enabled Rafradek (talk) 14:28, 7 September 2022 (UTC)

zenstates-git^AUR is the only package exist in AUR, so here I think you should contact the AUR maintainer first. Update the package then update the page. --Fengchao (talk) 08:07, 23 January 2023 (UTC)

In 4.1, it says: "To solve this problem you need to supply higher voltage to your CPU so that it is stable when running at peak frequencies. The easiest way to achieve this is to use the AMD curve optimiser which is accessible via your motherboard's bios. Access it and put a positive offset of 4 points, which will increase the voltage your CPU is getting at higher loads."

I tried that, first 4, later 6 points. No effect. Switched off PBO and tweaked a number of BIOS modifications that I found on the web, i.e. various recommendations for preventing random reboots with AMD Ryzen.

I have an AMD Ryzen 9 7900X.

What did help is

"sudo cpupower frequency-set -g powersave; sudo cpupower frequency-set -d 800MHz" i.e. my minimal frequency was increased from 400 to 800 MHz.

I did not experience any more random reboots with low workload after that.

But it did reboot once with a high workload. Then I switched off the positive offset of 6 points. Back to default.

I have not experienced any reboots with a low and high workload since I set this, a week ago. Sparrow (talk) 11:12, 6 September 2024 (UTC)

I found out (the hard way) that the same error pops up at reboot when my PC crashes from too high video ram frequency. If I set it at some higher unstable value, game would crash and I'd get that "CPU:x" failed message at reboot. Even with +5 on all core voltage curve on CPU. I am sure the reboot is due to too high video memory clock, yet that CPU:x failure still appears on reboot.

So also watch your video memory frequency that you set, if you get that kind of error message on reboot. Bibi (talk) 23:19, 14 May 2025 (UTC)