Yesterday we reported that MSI announced a wave of firmware updates designed to address and alleviate potential issues with users on AM5 using AMD's Ryzen 7000X3D processors with 3D V-Cache. One of the main changes with MSI's latest UEFI firmware for AM5 included voltage restrictions when using Ryzen 7000X3D series CPUs. Further to recent reports of users with AMD Ryzen 7000X3D processors experiencing damage to their chip and motherboard socket, we reached out to AMD this morning to seek clarification. AMD has just responded with an official statement concerning the current problem.

The statement directly from AMD is as follows:

"We are aware of a limited number of reports online claiming that excess voltage while overclocking may have damaged the motherboard socket and pin pads. We are actively investigating the situation and are working with our ODM partners to ensure voltages applied to Ryzen 7000X3D CPUs via motherboard BIOS settings are within product specifications. Anyone whose CPU may have been impacted by this issue should contact AMD customer support."

As the statement clarifies, AMD themselves are investigating the issue that users have been experiencing, which has been reported on through various channels such as social media and Reddit. This is further to MSI, which launched new firmware yesterday, and ASUS announced new firmware today for users with AMD Ryzen 7000X3D processors, such as the Ryzen 9 7950X3D and the Ryzen 7 7800X3D. The new firmware specifically limits the SoC voltages applied so that these critical limits aren't breached when users enable AMD EXPO memory profiles on supported DRAM.

While AMD hasn't officially confirmed the problem regarding the burnt pads on the Ryzen 7000X3D series processors and the burnt pins within the motherboard socket, AMD is actively looking to resolve this issue. One theory thus far is that the issue is being triggered when users are enabling AMD EXPO memory profiles – which, much like Intel's XMP counterpart, is technically a form of overclocking and officially voids the product warranty. Given the rollout of new firmware, which targets SoC voltages and restricts them, all things point towards voltages and overclocking said processors, which are, by default, multiplier and CPU VCore locked.

AMD is actively working with motherboard vendors such as MSI, ASUS, GIGABYTE, and ASRock to roll out the new firmware. AMD also specifies that if users have a Ryzen 7000X3D processor affected by this problem, to contact AMD customer support directly.

Update (04/27): AMD has officially made a second statement regarding the Ryzen 7000 and 7000X3D burnout issues. It is as follows:

We have root caused the issue and have already distributed a new AGESA that puts measures in place on certain power rails on AM5 motherboards to prevent the CPU from operating beyond its specification limits, including a cap on SOC voltage at 1.3V. None of these changes affect the ability of our Ryzen 7000 Series processors to overclock memory using EXPO or XMP kits or boost performance using PBO technology.

We expect all of our ODM partners to release new BIOS for their AM5 boards over the next few days. We recommend all users to check their motherboard manufacturers website and update their BIOS to ensure their system has the most up to date software for their processor. 

Anyone whose CPU may have been impacted by this issue should contact AMD customer support. Our customer service team is aware of the situation and prioritizing these cases.

Image source: Speedrookie/Reddit

Comments Locked


View All Comments

  • zeroy - Wednesday, April 26, 2023 - link

    Who pooped in your cornflakes dude? And FYI, users are totally free to O/C their CPU/Ram, whatever, that is what those High End Motherboards are for!
  • philehidiot - Wednesday, April 26, 2023 - link

    I can see this both ways. Sending to GN and having a third party failure analysis lab examine it without any manufacturer intervention eliminates vested interests and protect consumers from companies claiming it was user error. The other side to this is that AMD are far better placed to conduct and interpret such an analysis but, amusingly, they might prefer it going to GN.

    Why? Because if this really is a more widespread problem, they're going to get enough samples to figure out what needs defuckulation. And, if GN really do stay entirely objective, and this turns out to not be AMD's fault, it helps stop people accusing AMD of denying responsibility.

    AMD might be in a stick situation. In my country, I would expect consumer law to say that XMP, etc is an advertised feature, that benchmarks are conducted with it on and that it's AMD's responsibility to ensure motherboard partners have the correct spec to not fry the chip. I'm not sure a "warranty void" warning holds up when you're selling the product based on those features being enabled. It's like saying a car can go 150mph but your warranty is void if you go above 70mph, and then advertising it as a suitable track car.
  • Zodwraith - Wednesday, April 26, 2023 - link

    If I spent $600 on a motherboard and $450 on a chip to have it burn out cause I enabled expo f*ck AMD. I'd MUCH rather send it to GN for it's full value than AMD hoping they don't come back weeks later to say "tough shit, you enabled expo and we aren't warrantying it." Especially when AMD has MUCH more to gain from hiding the true cause if they discover it was their f*ckup.

    Your attempt to discredit Gamers Nexus just makes you look like an AMD apologist that doesn't want the body cam footage released after a police shooting. I know if I'd bought this overpriced line of CPUs I'd be FAR more interested in independent testing than AMD's when they'd benefit FAR more from hiding any failures than GN getting a few more views.

    GN is taking a HUGE risk pissing off AMD by buying this chip in the search of truth and exactly why they're respected by the community.
  • Silver5urfer - Thursday, April 27, 2023 - link

    What risk are they taking ? Like how they ate money from Nvidia on giving out how 12VHPWR Is exclusively user error, like Nvdia PR was only given to them not to all because Nvidia liked GN way and how that way they could not be stressed to give an official PR statements low visibility and less money involved and less accountability. Their adapters and solution was garbage. Fact of Intel 3.0 ATX revision cements it.

    AMD's QC botch up or not this situation does not make GN any saint or such. Esp the fact he ignored the LGA1700 socket failure of bending for months only to come out after the Thermalgrizzly's Contact Frame was out.
  • Questor - Sunday, May 14, 2023 - link

    "Your attempt to discredit Gamers Nexus just makes you look like an AMD apologist that doesn't want the body cam footage released after a police shooting."

    Except that's a poor comparison. After whining about accountability and getting bodycams put on cops all over the place, deepening the taxpayer burden, the NAACP complained bodycams were an invasion of privacy when the overwhelming majority of footage vindicated police.

    In this scenario, that would put AMD in the victim category and the consumer being the entity causing the infraction.

    Also, Gamer's Nexus has no risk in this. That's just a silly statement to make. A person takes more risk crossing the street on a daily basis than Gamer's Nexus risks in this affair.
  • Arte - Thursday, April 27, 2023 - link

    "I skipped Zen 3 because it rightfully had IODie instability once you touch DRAM OC past 3200MHz and the USB drop outs no AGESA could fix them. My guess is it's due to the 3 variable system on the Uclock, Memclock, Fclock.. Zen 4 fixed all of them by decoupling that links to 2 variables now."

    Could be a couple of years since i last visited Anandtech.
    FF to 2023 and the "Silver FUDozer" still going strong, knowing it all.


    My 5700X rig ticks @ DDR4-4000 1:1 , for months now , with no issues whatsoever, especially at the USB.
    And i would know, since -amongst other- i use USB BT devices, namely a mouse and a headset.
  • Silver5urfer - Thursday, April 27, 2023 - link

    Anandtech article reported the USB failures, I go to OCN and see it always a thing for this reason alone OCN has WHEA Supressor made. Why would I have to lie about some X corporation and I do not care about your IMC ratio and it's irrelevant for an anecdotal take. As I've seen enough of these user complaints on OCN. Then the Videocardz comments for some of the users mentioning this, and a ton of reports on Reddit on brand new X570 series and other forums where I have knowns have reported issues on their own machines. The Zen 3 is a failure in terms of stability and UASP does not exist on that platform still. I did my research for my purchase as I do not want to fiddle around the BIOS with unknown non documented values for variables.

    And what I mentioned is accurate, Zen 4 does not have 3 links now. It's only 2 that IODie link is removed as a part of the change its only DRAM+ IMC and no FClock link anymore. If you do not know jacks just move on.
  • Silver5urfer - Thursday, April 27, 2023 - link

    To add - The last page of this article comment has one user mentioning the USB failures on Zen 3 platform. It's garbage. End of story. AMD users should get Zen 4 if they want stability or wait for Zen 5, as Intel is garbage in LGA1700 bendgate fiasco and untameable heat.
  • dwade123 - Tuesday, April 25, 2023 - link

    They have deleted so many threads on Reddit to sweep it under the rug but now the news have blown up all over the web like their processors.
  • Jonny_H - Tuesday, April 25, 2023 - link

    Reddit posts are being deleted to "cover this up"? The same reddit where the hardware and amd subreddit frontpages are completely filled with this drama? The same reddit that is completely blowing this up with no actual new information and rephrasing speculation as "Confirmed Cause"? That reddit?

Log in

Don't have an account? Sign up now