AMD Ryzen 7000X3D Processors Prone to Physical Damage with Voltage-assisted Overclocking, Motherboard Vendors Rush BIOS Updates with Voltage Limiters

[AnarchoPrimitiv]

Yes, this appears to be true - and is even more painfully true in notebooks. It's a major reason every manufacturer is trying to avoid AMD's chips I believe, no matter how good they are.

"You believe"....oh, OK, so you have absolutely no evidence to support your assumptions? Anyway, the lack of laptop designs is caused by the fact that AMD doesn't have the same financial resources to bribe OEMs...now the OEMs call that "product development cooperation", but that's what they mean, that AMD doesn't have the same money to hand over like Intel...after all Intel's R&D budget is over $17 billion and AMD's is around $5 billion, that makes a HUGE difference, and yet, there's no shortage of people who compare Intel and AMD like they're on equal footing.

 

[Vayra86]

You understand that sethmatrix7 was making a joke, right? Because it doesn't seem like you do

I do! The joke behind it though is that people really think this way.

 

[AnarchoPrimitiv]

It's not just the 3d chips that are going kaboom.

http://imgur.com/a/1oNS9DC

Just out of curiosity, what's your issue with AMD really?

 

[mahoney]

Just out of curiosity, what's your issue with AMD really?

None. Just never go 1st gen on them like ever. Ryzen Zen 1st gen had huge problems with memory frequency.
You have 3-4 gen's of support so don't be an idiot and become their beta tester/early adopter.

 

[bobsled]

Play stupid games, win the clickbait Youtube titles. Roman surely knows better…

 

[Hxx]

>do something not recommended or covered under warranty

>it breaks

HOW COULD AMD DO THIS

You are missing the underlying issue which is that there is a very blurry line drawn by both board makers and chip maker between what is covered and what is not covered under warranty and due to performance reasons. Basically they want to advertise the best possible performance and blame you for enabling performance tuning options .

For example enabling xmp is not covered by warranty but sure as shit no one designs a bios where there is a big fat warning for it and ofc 99.99% users enable it . Same goes for most bios “tuning” options outside of specific voltage adjustments so ofc users will poke around thinking it’s “safe”. There has to be a clear line between what users can do and cannot do in bios that would not be covered and manufacturers have zero interest in clarifying it but they will hold u accountable when shit breaks

 

[Metroid]

AMD and motherboard partners should have blocked overclocking/overvolting only, only underclocking/undervolting should have been allowed.

 

[MarsM4N]

It's not just the 3d chips that are going kaboom.

http://imgur.com/a/1oNS9DC

It could all be connected to the EXPO settings, which would be a major blow if running DDR5-6000 would put your CPU in danger. Eager to see how this developes.

Igor from igorsLAB posted some numbers in the forums. Enabling EXPO 6000 ramps up the VDDCR_SOC to 1,35v. Reduced manually to 1,30v and he can only run 5800 solid. Might be just a BIOS bug, but if it turns out that you can't run DDR5-6000 without putting your CPU in danger because you need that juice to run the OC RAM solid, then that would be big PR nightmare. DDR5-5200 vs DDR5-6000 can make a difference of up to 10%, so you would loose quite some performance.

There's also a reddit post gaining traction:
Pin analysis of the destroyed Ryzen 7800X3D - All burned pins supply the VDDCR (CPU Core Power Supply) | igor'sLAB

 

[Dwarden]

this leaves important question, does even using faster memory (imagine 1:1 DDR5-5600/6000/6200 or just EXPO) risk the similar fate
because this ability to use fast memory and 4 of them (yes the trash limit of 2 modules) is overclocking in the eyes of AMD
limit of 2xddr5-5200 or 4xddr5-3600
and means the X3D could burn your money in multiple ways

 

[R0H1T]

I doubt that but board makers have done worse things in the past, so who knows!

 

[Shelterdeck]

Because you can gain another 10-25% for free and it's fun? A tuned 7800X3D with PBO undervolt and fast memory is a seriously awesome chip.

If you're at the 15C for 100Mhz point then you either pushed WAY past diminishing returns point and should turn back.

Usually CPUs don't explode - so that's not typically a risk people account for these days.

''Usually CPUs don't explode - so that's not typically a risk people account for these days.''
You are right there..never leave the fire service!

 

[Darmok N Jalad]

I'm really at a loss for how people are blaming AMD for a user error....the info has been widely disseminated since the 5800x3d that they're not for overclocking, and it's probably safe to assume that if a user is experimenting with overclocking these, then they're "enthusiast" enough to have been exposed to that warning.

As for the people (or person) claiming that AMD doesn't work enough with MOBO partners......what? There is absolutely no doubt in my mind that mobo manufacturers are FULLY aware of the limitations of these chips, but probably tried to push it even further for a competitive advantage. As far as "working with" these manufacturers, It seems like I'm the only one who knows or acknowledges the fact that Intel spends over 3x the amount AMD does on R&D and that includes bribing, I mean "reimbursing development costs" to OEMs....funds that AMD probably dont have.


You understand that sethmatrix7 was making a joke, right? Because it doesn't seem like you do


Although I try not to engage in whataboutisms....name another company of the SAME SIZE and FINANCIAL resources as AMD who hasn't had some problems

Yeah, and Intel will even help OEMs pay for advertising. That’s a pretty big carrot, TBH, as building a laptop only matters if you can get people to know it exists.

Also, if anyone remembers the Surface “hot bag” woes, it was because MS implemented a v1.0 power feature on Kaby Lake. Why did no other OEM have trouble with their Kaby Lake rollout? Because they all had a practice of not implementing a v1.0 feature from Intel. They waited for the next release.

 

[evernessince]

It 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.

"clearly"? Surely then you can provide links and not mere conjecture for your theory. Evidence presented thus far does not support such a conclusion

It's not just the 3d chips that are going kaboom.

http://imgur.com/a/1oNS9DC

The 7000 series chips have been out since September of 2022. That we've not seen any reports until now says to me that the regular chips are not experiencing the same issue in any volume or that the issue is the result of a recent AGESA update.

 

[Mahboi]

Watch all the idiots who will go and cry that it's AMD's fault for releasing CPUs on a set clock and them not respecting that clock.

"b-b-b-but all these years we could go and do whatever and it all went fine!!!!!!!!!! !THIS IS ALL AMDS FAULT!!!!!!!"

Yes, my idiot, that's where you see that it's a proper new technology. It breaks when you pull on it. It's not just an automatic step up from what you're used to, and actually comes with increased fragility/risks.

>do something not recommended or covered under warranty

>it breaks

HOW COULD AMD DO THIS

Edit: I was clearly too late to the thread!

 

[Outback Bronze]

I did read this a little while ago somewhere but didn't look too much into it.

I'd really like to know how widespread the issue is, or if it's just a one-off case? Not reading many details in the info.

Let's see how "not cool" the issue is.

 

[phanbuey]

Watch all the idiots who will go and cry that it's AMD's fault for releasing CPUs on a set clock and them not respecting that clock.

"b-b-b-but all these years we could go and do whatever and it all went fine!!!!!!!!!! !THIS IS ALL AMDS FAULT!!!!!!!"

Yes, my idiot, that's where you see that it's a proper new technology. It breaks when you pull on it. It's not just an automatic step up from what you're used to, and actually comes with increased fragility/risks.


Edit: I was clearly too late to the thread!

Increased fragility and risks are not inherent features of new technology -- they're just risks that weren't properly mitigated.

Shifting blame to the user is the standard approach, which also never works.

 

[sethmatrix7]

Increased fragility and risks are not inherent features of new technology -- they're just risks that weren't properly mitigated.

Shifting blame to the user is the standard approach, which also never works.

But there are no increased fragility or risks.

Within manufacturer specifications.

If I overclock my 65 inch LG tv and it breaks- do I now get to blame LG? Of course not- that’s braindead.

 

[marios15]

We haven't had new process nodes for 10 years and everyone thinks that safe voltages on 7nm process are also safe at 5nm process.

This is exactly why nobody should ever trust all those great "100% 24/7 stable 6.7GHz 1.1V OC" stories from forum bros.

any manual overvolting on CPU or change of multiplier, will disable manufacturer-set power and current limits for the CPU
Then it's up to motherboard or user to set limits

Now go play with the EDC 1A bug

 

[Mahboi]

weren't properly mitigated.

What does "new" mean to you exactly?

 

[phanbuey]

But there are no increased fragility or risks.

Within manufacturer specifications.

If I overclock my 65 inch LG tv and it breaks- do I now get to blame LG? Of course not- that’s braindead.

Yeah but if the TV came with an 'overclock' button that blew the TV up - that would piss you off. Or better yet, if there was a setting called "COLOR BOOST" in the menu and then your pixels exploded when you enabled that.

What does "new" mean to you exactly?

It doesn't mean it comes with a setting that fries itself.

 

[Metroid]

What I have learnt through the years is, never be the guinea pig, take your time and research a lot as long as it takes before the purchase.

 

[Mahboi]

But there are no increased fragility or risks.

Within manufacturer specifications.

If I overclock my 65 inch LG tv and it breaks- do I now get to blame LG? Of course not- that’s braindead.

These people are braindead though.

Literally getting a new technology and going pompously pointing fingers and throwing shade at the creator of the new tech for "not mitigating" well enough.
Hey genius, that's what being NEW is. We don't know the mitigations because they're new. That's the entire concept of "new", or "unknown" or "innovative" or really anything that isn't just walking the same inroads we've been doing for 15 years. Ignoring instruction sets, 3D Vcache is probably the first very big CPU improvement since multi core.

And here we have these Holy Judges passing their Holy Judgement on AMD for their users playing around with a completely new tech and not somehow magically guessing how to stop them doing something stupid before they even do any of these things.

What I have learnt through the years is, never be the guinea pig, take your time and research a lot as long as it takes before the purchase.

Well, that is quite boring.
I mean it's safe and all, sure. But boring.

 

[TTPPUU]

Why is the article outright lying ? Speedrookie DID NOT OVERCLOCK THE CPU AT ALL, HE ONLY ENABLED EXPO1

read here:
https://www.reddit.com/r/Amd/comments/12tlk7s/_/jhbfh8y

 

[phanbuey]

These people are braindead though.

Literally getting a new technology and going pompously pointing fingers and throwing shade at the creator of the new tech for "not mitigating" well enough.
Hey genius, that's what being NEW is. We don't know the mitigations because they're new. That's the entire concept of "new", or "unknown" or "innovative" or really anything that isn't just walking the same inroads we've been doing for 15 years. Ignoring instruction sets, 3D Vcache is probably the first very big CPU improvement since multi core.

And here we have these Holy Judges passing their Holy Judgement on AMD for their users playing around with a completely new tech and not somehow magically guessing how to stop them doing something stupid before they even do any of these things.


Well, that is quite boring.
I mean it's safe and all, sure. But boring.

Yeah... keep blaming it on the braindead users not using it properly that it exploded lmfao.

I love how you stick to this argument that stands up to 0 scrutiny. The guy didn't even OC it just enabled XMP. What an absolute idiot that guy is -- clearly everyone knows not to enable XMP on the 'NEW' products because their NEWNESS just means added fragility.

All the motherboard manufacturers rushing out bios updates to fix their default settings is definitely not a sign of a flaw... it's just new! these users are so dumb and cant handle the newness. Maybe send them a dictionary with the definition of 'new' tabbed for 'em... that'll fix it.

 

[sethmatrix7]

These people are braindead though.

Literally getting a new technology and going pompously pointing fingers and throwing shade at the creator of the new tech for "not mitigating" well enough.
Hey genius, that's what being NEW is. We don't know the mitigations because they're new. That's the entire concept of "new", or "unknown" or "innovative" or really anything that isn't just walking the same inroads we've been doing for 15 years. Ignoring instruction sets, 3D Vcache is probably the first very big CPU improvement since multi core.

And here we have these Holy Judges passing their Holy Judgement on AMD for their users playing around with a completely new tech and not somehow magically guessing how to stop them doing something stupid before they even do any of these things.


Well, that is quite boring.
I mean it's safe and all, sure. But boring.

>tampers with component in a way the manufacturer did not intend

>it breaks the component

HOW DID THE MANUFACTURER NOT MITIGATE THIS