F5F Stay Refreshed Hardware Desktop Performance during low usage periods High idle speeds observed in Ryzen 5 3600X models

Performance during low usage periods High idle speeds observed in Ryzen 5 3600X models

Performance during low usage periods High idle speeds observed in Ryzen 5 3600X models

Pages (2): Previous 1 2
S
SmileyFishMC
Member
60
04-30-2019, 07:20 PM
#11
AMD warns that if the system remains above 1.0 while idle, you must report it. This issue is documented in their chipset firmware—though they’ll likely shift blame to motherboard makers. The real solution involves adjusting the power plan, setting CPU states in advanced options between 85% and 100%, as AMD recommends. This should resolve the problem, though if it persists, consider initiating an RMA (if you’re using the latest OS, BIOS, and chipset drivers). Be cautious about what you share, as AMD acknowledges the concern but confirms it’s addressed in newer updates.
S
SmileyFishMC
04-30-2019, 07:20 PM #11

AMD warns that if the system remains above 1.0 while idle, you must report it. This issue is documented in their chipset firmware—though they’ll likely shift blame to motherboard makers. The real solution involves adjusting the power plan, setting CPU states in advanced options between 85% and 100%, as AMD recommends. This should resolve the problem, though if it persists, consider initiating an RMA (if you’re using the latest OS, BIOS, and chipset drivers). Be cautious about what you share, as AMD acknowledges the concern but confirms it’s addressed in newer updates.

D
DriveIn
Senior Member
739
05-05-2019, 08:56 AM
#12
Refers to a short-term solution.
D
DriveIn
05-05-2019, 08:56 AM #12

Refers to a short-term solution.

S
Seoulsib
Member
192
05-05-2019, 02:06 PM
#13
He clarified what the AMD representative intended. I was focusing on a different solution, but the latest BIOS, Windows, and chipset drivers resolved it. If the issue persists, this is the correct fix.
S
Seoulsib
05-05-2019, 02:06 PM #13

He clarified what the AMD representative intended. I was focusing on a different solution, but the latest BIOS, Windows, and chipset drivers resolved it. If the issue persists, this is the correct fix.

Pages (2): Previous 1 2