AusWolfI'd say it's not just a little suspicious. I'm smelling Youtube sensationalism again.

trparkyTrue, but that doesn't mean that people shouldn't still be a little cautious until we know more.

GicaIt is not the first time that manufacturers have to respond to AMD's blunders. It is clearly a mistake in the design of the socket and the protection of the processor. Hard to destroy a processor these days. He doesn't actually let you kill him.

Chrispy_LGA1700 - issues with the socket bending and first-gen non-heterogenous cores requiring numerous bios fixes, patches, and scheduler re-writes to iron out all the problems.

jigar2speedGica, you okay there little buddy ? You keep insisting its AMD's fault where as everyone knows AMD has blocked OCing on X3D chips. If motherboard makers are bypassing recommended protocols, its on motherboard makers and not on AMD.

What is so difficult to understand ? Please explain.

jigar2speedGica, you okay there little buddy ? You keep insisting its AMD's fault where as everyone knows AMD has blocked OCing on X3D chips. If motherboard makers are bypassing recommended protocols, its on motherboard makers and not on AMD.

What is so difficult to understand ? Please explain.

nguyenIn your example if FORD show in an advertisement that their cars can run submerged and when you do it, it kills the engine, that is false advertisement isn't it

ZubasaI wouldn't pin it on the user so soon. DIY motherboards often run things out of spec even by default.

Vayra86Correct, I remember this one vividly

www.gamersnexus.net/guides/3590-dont-run-z490-motherboards-with-default-settings-for-your-build
I could easily fish for another handful of generations/sockets where this has occurred at one or more mobo mfgrs.

So again... user due diligence is needed, has been needed and will always be needed with DIY building. Its why we call it DIY. People need to get a life. And AMD/mobo partners need to lock this down on X3D's just as well, because there is literally no purpose to leave it unlocked. And if unlockable, it needs to come with warning on the UEFI toggle.

fevgatosYes and no. Z490 pushed insane sa voltages (basically imc) whenever you tried to run DDR4 at 4400 and upwards like 1.5 - 1.6 sa voltage was quite common at auto settings. That is almost insta death territory for the imc. But it would never lead to that catastrophic of a failure we are seeing with the am5 here. Your cpu would just die, not cook itself and the mobo.

Vayra86But does it cook itself and the mobo, or are we looking at a big bunch of lies?
We're still talking about an extremely rare occurence and a world full of people looking for ad revenue with cool videos
If this was a board default thing even on ONE board of ONE vendor, we would have seen many more issues. Shit just doesn't line up

fevgatosWell - what I said was assuming the rumors are true. For all we know it could just be Asus doing Asus things again, not the first time their super high end mobos end up being trash. My z690 apex.... yikes

KlemcAsus and all others, x3d and non-x3d, read more pages

Bomby569asus, gigabyte and asrock, according to derbauer

KlemcI lost 10°c at stock by using MX5 instead MX4 btw

R0H1TWith how many chips failing? Is there a scientific conclusion that can be drawn from any of these "outrageous" observations or just click-bait/fluff videos!

Berfs1Alrighty, here's the deal with warranty. If you are in the US, you are covered under the Magnuson Moss Warranty Act, because applying EXPO also changes other settings that the motherboard auto defined. Because the MOTHERBOARD entered in the unsafe settings and not you, you wouldn't be liable for this kind of damage, the motherboard manufacturer would. While yes the manufacturer of a product has to prove you caused the damage, in this particular case since the motherboard was auto defining unsafe values as safe, it would be the motherboard manufacturer that would be liable for this. Also why did AMD not test these chips beforehand? If over 1.3V SOC voltage instantly kills CPUs, AMD should have known about this prior to launching them. This is mainly AMD's fault for not testing their products and telling motherboard manufacturers what values to NOT auto define. Imagine Ford shipped you a car that should work in ideal conditions, but when driving below sea level, the engine blows up because of the higher air density. Why would that be YOUR fault because you drove it in a place that was 200ft below sea level? It's not like you are visiting a volcano or going to the core of the earth which would need a special kind of car, it's 200 feet below sea level.

jigar2speedGica, you okay there little buddy ? You keep insisting its AMD's fault where as everyone knows AMD has blocked OCing on X3D chips. If motherboard makers are bypassing recommended protocols, its on motherboard makers and not on AMD.

What is so difficult to understand ? Please explain.