It only slightly improves all cores.
It only slightly improves all cores.
I recently changed my R5 1600 to an R5 5600 on an Asrock AB350m Pro4 board. I was told via reviews and videos that the stock CPU would run at 4.1-4.3 GHz per core based on silicon variation, and that the Ryzen 5000 is quite energy efficient. My 5600 with a Wrath Spire achieved 3.56 GHz on Cinebench R23, while paired with an Arctic Freezer Duo it hit 3.75 GHz. To push it above 4 GHz I need to increase power through PBO and tweak the curve optimizer. With PBO active it reaches around 4.3 GHz at 125 watts. Is this normal performance or a faulty unit? The Asrock AB350m Pro4 latest BIOS/chipset drivers work just like with the 1600 Cinebench Wrath Spire screenshot: https://imgur.com/a/P412Jj3 and the Arctic Freezer Duo screenshot: https://imgur.com/a/QsNx96j
This refers to a maximum speed estimate, not a fixed number. It varies based on factors like material quality, operating conditions, and voltage levels.
Not unusual, some folks simply receive a very disappointing outcome. There’s always the chance to request a replacement or return if you believe it’s faulty. Certain dies are merely overly prone to leakage, allowing current to escape and power that isn’t needed for processing ends up as heat—still, they generate heat regardless. I’d suggest if you’re running around 3.55Ghz on a standard cooler, there’s likely an issue and it should probably be RMA’d.
It could be related to W11 as well. Consider switching power settings to performance mode. What's your RAM speed? I just looked at my setup. My system runs at 5600 boosts with 4.16 all-core (no overclocking, default Windows 10 settings). A base clock of 3.5 suggests instability or insufficient cooling for higher speeds.
I noticed the voltages appear quite low in the screenshots, which might impact clock performance. Have you experimented with adjusting the voltage offset to +0.15-0.2 or setting a value between 1.25 and 1.35 according to your BIOS software? Considering you're using PBO enabled, what seems to be the problem?