AMD asking motherboard makers to remove Ryzen 5800X3D overclocking and people are angry!

As many of you know, AMD is planning to launch a new Ryzen 5800X3D processor focused for gaming with new stacked memory. Essentially they’ve taken Ryzen 5800X and bolted 96MB of stacked memory on it (5800X has 32MB so 3x as much), that should apparently help gaming performance significantly.

Apparently, adding so much memory (96MB per CCD which means 96MB because 5800X only has one CCD) on a CPU created certain technical issues or limitations because Ryzen 5800X3D has a lower boost clock than it’s older sibling. It’ll only boost up to 4.5 GHz opposed to 4.85 GHz on 5800X. Despite this, it’s apparently suppose to give 15% better performance in games than with older Ryzen 5800X.

And this is where the title of the post comes in. AMD asked motherboard manufacturers to disable overclocking for Ryzen 5800X3D, presumably because of technical limitations this new stacked memory brought to the table.

And it’s this point where I’m a bit confused over the outrage of people who now scream “OH MY GOD, EVIL AMD DOESN’T ALLOW US TO OVERCLOCK ANYMORE!”

To which I wonder, has it ever? I happen to have 5800X and in basically 2 years of owning it (yeah, it’s been this long already), I couldn’t overclock it AT ALL.

You can raise max boost limit, you can enable Precision Boost Overdrive (PBO), you can increase PBO limits yourself, you can increase voltage, you can increase scaling multiplier, you can increase Loadline calibration (LLC) and… NONE OF IT EVEN MATTERS.

The way Ryzen 5000 processors are designed, they basically work as good as they ever will out of the box. You can fiddle with it and gain a % here and there and that’s about it. The most you’ll ever gain is by improving cooling and decreasing voltage leakage. Basically ensuring it’s cooled really well and you shave off as much voltage as you can through negative Vcore offset and Curve Optimizer before you start hurting performance is the way to go with Ryzen 5800X (or any Ryzen for that matter). These CPU’s are incredibly temperature sensitive and they start dropping clock the moment they go past 75°C with pretty dramatic drops at 80-85°C and they start thermally throttling at 90°C (5800X anyways).

Increasing boosting limit and PBO does nothing, if anything it hurts performance. Raising limit just makes it read nice numbers like 5GHz in monitoring software, but it’s just “clock stretching” where it goes to 5GHz, but not really. PBO just makes it eat tons of more power and then thermally clocking itself down as a result because that raises temperatures. Only thing that you can sort of gain is purely for multithreaded loads where you can raise all core performance a bit by gaining 100 to 200MHz more in all core loads. Not really useful for gaming.

Not to mention AMD has other overclocking issues, like if you increase multiplier, it just gets permanently stuck at that. Intel CPU’s can still drop the multiplier to base clock multiplier when not under load. And same for voltages. With AMD you can only do positive offset to increase voltage or make it permanent fixed increase. So it’ll just run at max voltage or at least at permanently increased one at all times. Intel CPU’s have “Adaptive Vcore voltage” option where it only applies increased voltage when under heavy load, where you actually need it. Miss this stuff on AMD…

So, why the outrage? Anyone who has actually used Ryzen CPU should know all the overclocking is all bullshit no matter how much AMD claimed CPU’s will be “heaven for overclockers”. And you’ll still be able to control voltages and curve for sure even on 5800X3D, meaning just lowering voltage overhead will automatically bring it to its maximum peak performance anyways.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s