Question Ryzen 7 1700X Crashing - Event ID 35 "Performance power management...firmware problem"

May 11, 2021
During a recent gaming session my pc hard crashed to a black screen, and after checking event logs I noticed the following errors:
Event 35 Kernel-Processor-Power (Windows-Kernel-Processor-Power)
"Performance power management features on processor 0 in group 0 are disabled due to a firmware problem. Check with the computer manufacturer for updated firmware."
This error is duplicated for each of the 16 processor threads. My system has had the same stable OC for the last 4 years without any issues, and I've never seen these errors before.
I updated my BIOS to 5.50, and removed all my OC settings and set everything back to standard default settings (including lowering voltage), did a clean install of windows 10, and cleared out old error logs, but the same errors popped back up after reboot.
OS: Windows 10 Home Build 19042

CPU: R7 1800X @ 3.9 GHz

MB: ASRock AB350M Pro4 Socket (BIOS v. 5.50)

RAM: 32 GB G.SKILL Ripjaws V Series 32GB (2x16GB) DDR4 3200MHz CL16 Dual Channel Memory Kit 1.35V (F4-3200C16D-32GVK)

GPU: NVIDIA GeForce GTX 1080 (GP104) @ 139 MHz

PSU: EVGA Super NOVA 650 G3 80 Plus Gold 650W


Windows Power Management setting set to 'Ultimate Performance' Ryzen Balanced
Latest Chipset drivers installed from AMD website

CPU: 1.28125V

RAM: 1.350v

CPU-Z Validation Link (2021):
I've read in other threads a possible fix was to Disable Quiet and cool in the BIOS, but that feature option was removed in the current version of the BIOS I have. I also saw this may be related to a PSU issue. My temps running Prime95 small FFT for a few hours are in the mid to high 60 degree range, and usually in the mid 30 to mid 40 degree range when gaming.

Any advice is welcome, thanks!
Last edited:
May 11, 2021
Install the latest chipset drivers and set to "Ryzen balanced" power plan.

I have had tons of issues with the performance power plan.
I installed latest chipset drivers from AMD website, and set to Ryzen Balance plan. After rebooting, the same errors pop up again.


It might be time for a new CPU since you have run an OC for four years on a relatively new CPU architecture in which nobody really knows how they will hold up under such long term might be that you're finding out that four years is about it.

The fact that the error continues after re-installing Windows and a BIOS update points to the CPU.
I did extensive testing when I chose my OC settings, and I've had it running on those settings for 4 years. All my temps are within normal range as well, so it's puzzling.
1.28V for a first gen is pretty low voltage even for only 3.9G, you might try raising to 1.35V or so just to see if this problem goes away. If it does then lower it until you find it's new stable point. IIRC first gen is considered safe for up to 1.425V with temp under 70C, around 1.38 with temps in the upper 80's.

I can understand it's desireable to keep a low-leakage 1700X as un-degraded as possible with low volts but you also have to realize that degradation due to electromigration is unavoidable any time it's powered on and it only accelerates with higher core current and temperatures. So even if it was once stable at such low volts it's inevitable it will degrade and need greater voltage to hold a fixed OC.

I've been running a 1700 at 3.9G for a few years too, but it needs quite a bit higher voltage to do it. Even if your 1700X ends up being a bit degraded and need higher voltage it's hardly 'dead'. Just give it the volts it needs to be stable and truck on. You've got a lot of margin before it starts turning into a 1700 LOL
Last edited: