F5F Stay Refreshed Power Users Overclocking Report about Ryzen 7 1700X overheating issues - Event ID 35 "Performance power management...firmware issue"

Report about Ryzen 7 1700X overheating issues - Event ID 35 "Performance power management...firmware issue"

Report about Ryzen 7 1700X overheating issues - Event ID 35 "Performance power management...firmware issue"

Pages (2): 1 2 Next
T
TheDragon_Man
Member
59
03-19-2017, 10:35 AM
#1
During a recent gaming session my computer crashed to a black screen. After reviewing the event logs, I observed these errors repeatedly across all 16 processor threads. Despite having maintained the same stable operating configuration for the past four years without any problems, these issues have now reappeared.

I upgraded the BIOS to version 5.50, removed all custom settings and reset everything to the standard defaults—including adjusting the voltage—and performed a fresh installation of Windows 10. Additionally, I cleared out previous error logs. However, upon restarting, the same errors resurfaced.
T
TheDragon_Man
03-19-2017, 10:35 AM #1

During a recent gaming session my computer crashed to a black screen. After reviewing the event logs, I observed these errors repeatedly across all 16 processor threads. Despite having maintained the same stable operating configuration for the past four years without any problems, these issues have now reappeared.

I upgraded the BIOS to version 5.50, removed all custom settings and reset everything to the standard defaults—including adjusting the voltage—and performed a fresh installation of Windows 10. Additionally, I cleared out previous error logs. However, upon restarting, the same errors resurfaced.

F
fireroster
Member
150
03-19-2017, 07:14 PM
#2
Upgrade the chipset drivers and configure the power plan to "Ryzen balanced."
I've experienced many problems with the performance power plan.
F
fireroster
03-19-2017, 07:14 PM #2

Upgrade the chipset drivers and configure the power plan to "Ryzen balanced."
I've experienced many problems with the performance power plan.

C
catseecoo
Senior Member
662
03-19-2017, 08:49 PM
#3
I put in the newest chipset drivers from the AMD site and chose the Ryzen Balance plan. Once I restarted, the same issues kept appearing.
C
catseecoo
03-19-2017, 08:49 PM #3

I put in the newest chipset drivers from the AMD site and chose the Ryzen Balance plan. Once I restarted, the same issues kept appearing.

M
Machi_Gamz
Member
204
03-19-2017, 10:00 PM
#4
May you c00ked it
M
Machi_Gamz
03-19-2017, 10:00 PM #4

May you c00ked it

M
MILKANDOREOS
Junior Member
4
03-20-2017, 11:52 PM
#5
I thoroughly tested my OC settings before using them, and they have been functioning properly for four years. My temperatures remain within the expected range, which is confusing.
M
MILKANDOREOS
03-20-2017, 11:52 PM #5

I thoroughly tested my OC settings before using them, and they have been functioning properly for four years. My temperatures remain within the expected range, which is confusing.

B
BenMank
Junior Member
2
03-25-2017, 08:01 AM
#6
It could be time to upgrade your CPU because you've been overclocking for four years on a new architecture where no one really understands how long it will last under such extended use...it's possible that four more years are all you'll get.
B
BenMank
03-25-2017, 08:01 AM #6

It could be time to upgrade your CPU because you've been overclocking for four years on a new architecture where no one really understands how long it will last under such extended use...it's possible that four more years are all you'll get.

I
Infecto35
Junior Member
9
03-26-2017, 08:37 AM
#7
The 1.28V specification is quite low for a first generation device, especially when only running at 3.9G. You might consider increasing it to around 1.35V to check if the issue resolves. If it does, adjust again until you reach a stable operating level. Generally, the first generation is thought to be safe up to 1.425V with temperatures below 70°C, which would be about 1.38V at higher temperatures in the upper 80s. It's understandable you want to maintain low leakage devices like 1700X or 1800X with minimal voltage, but remember that electromigration causes inevitable degradation when the device is powered on, especially as core current and temperature rise. Even if it was stable at such low voltages before, it will eventually degrade and require a higher voltage to maintain performance. I've also experienced this with a 1700 at 3.9G for several years—it demands significantly more voltage. If your CPU starts showing signs of degradation and needs higher power, it's not necessarily dead; just ensure it gets the necessary voltage to remain stable. You have plenty of headroom before it becomes a problematic 1700 model.
I
Infecto35
03-26-2017, 08:37 AM #7

The 1.28V specification is quite low for a first generation device, especially when only running at 3.9G. You might consider increasing it to around 1.35V to check if the issue resolves. If it does, adjust again until you reach a stable operating level. Generally, the first generation is thought to be safe up to 1.425V with temperatures below 70°C, which would be about 1.38V at higher temperatures in the upper 80s. It's understandable you want to maintain low leakage devices like 1700X or 1800X with minimal voltage, but remember that electromigration causes inevitable degradation when the device is powered on, especially as core current and temperature rise. Even if it was stable at such low voltages before, it will eventually degrade and require a higher voltage to maintain performance. I've also experienced this with a 1700 at 3.9G for several years—it demands significantly more voltage. If your CPU starts showing signs of degradation and needs higher power, it's not necessarily dead; just ensure it gets the necessary voltage to remain stable. You have plenty of headroom before it becomes a problematic 1700 model.

G
geglman
Member
87
03-28-2017, 05:46 AM
#8
Same here with a new build Ryzen 5 3600 Asus b450-F-II MOBO all 12 cores report Event Error 35 (2) power management firmware problem and my temps never go above 45 C I have the latest BIOS update 6/2021 so it is NOT a BIOS deal and there is no 'cool-n-quiet' setting in BIOS like the old M5A99FX had.
G
geglman
03-28-2017, 05:46 AM #8

Same here with a new build Ryzen 5 3600 Asus b450-F-II MOBO all 12 cores report Event Error 35 (2) power management firmware problem and my temps never go above 45 C I have the latest BIOS update 6/2021 so it is NOT a BIOS deal and there is no 'cool-n-quiet' setting in BIOS like the old M5A99FX had.

I
iiArctixAlex
Junior Member
1
04-01-2017, 12:34 AM
#9
Zen 2 (3600) on B450 presents a distinct situation compared to Zen 1 (1800X) on B350. Please create a separate thread for your issue.
However, relying solely on the 'latest BIOS' update might not be ideal, as the current B450 BIOS is likely designed for a Zen 3 CPU. If you cannot revert back to the previous Zen 2 BIOS, ensure the chipset drivers are updated and reset the CMOS to check if issues continue.
Cool-n-Quiet is no longer supported; it's typical to see this option removed in most Zen 3 BIOS versions as it's considered unnecessary.
I
iiArctixAlex
04-01-2017, 12:34 AM #9

Zen 2 (3600) on B450 presents a distinct situation compared to Zen 1 (1800X) on B350. Please create a separate thread for your issue.
However, relying solely on the 'latest BIOS' update might not be ideal, as the current B450 BIOS is likely designed for a Zen 3 CPU. If you cannot revert back to the previous Zen 2 BIOS, ensure the chipset drivers are updated and reset the CMOS to check if issues continue.
Cool-n-Quiet is no longer supported; it's typical to see this option removed in most Zen 3 BIOS versions as it's considered unnecessary.

W
Windiox
Member
226
04-08-2017, 04:10 PM
#10
The 'latest BIOS' suggestion from Asus applies to every series and covers all components of the board. It's not related to a chipset problem either, friend. Everyone had their devices updated during the initial setup.
W
Windiox
04-08-2017, 04:10 PM #10

The 'latest BIOS' suggestion from Asus applies to every series and covers all components of the board. It's not related to a chipset problem either, friend. Everyone had their devices updated during the initial setup.

Pages (2): 1 2 Next