Tuesday, September 8th 2026
Redditor's AMD Ryzen 9 9950X3D Reportedly Dies Shortly After Changing Motherboards
A Ryzen 9 9950X3D has reportedly died just an hour after being moved into an ASUS ROG Crosshair X670E Hero motherboard. According to Reddit user SpecialistConcept423, posting in r/GamersNexus, the chip had been running fine for about a year and a half in an ASRock X670E Taichi Carrara before the swap. After switching to the new board, no manual overclocking or voltage tweaks were applied; only one of the board's built-in memory presets was enabled for a set of SK hynix 6200 MHz modules. After saving that setting and rebooting, the board threw a "00" Q-Code and refused to post. Pulling the CPU and inspecting it revealed two brown marks on its contacts, which all but confirmed the catastrophic failure.
Things got stranger when the user resorted to an older Ryzen 5 8500G that had previously worked fine on the same board. That chip apparently now throws a "4D" code too, pointing at the motherboard itself as the culprit, not just the CPU. There's no confirmation yet on whether a faulty BIOS, a bad batch of boards, or something else is to blame, and ASUS hasn't commented on this specific case. It is worth noting that the ASUS board was not new, and it had undergone USB-related repairs and a BIOS rewrite. The user has since contacted AMD in Brazil for an RMA, but has shared no updates yet.
Interestingly, this isn't the first CPU failure tied to this exact board either. We covered a Ryzen 7 7800X3D that swelled and burned on the same ROG Crosshair X670E Hero model just days ago, and last year ASRock also admitted that overly aggressive PBO current limits fried a wave of Ryzen 9000 chips on its own boards. It's too early to say if these share a root cause, but there is certainly a pattern here. In this particular case, the X670E Hero claimed not one but two CPUs, and it only needed a single setting change to do so.
Source:
Reddit
Things got stranger when the user resorted to an older Ryzen 5 8500G that had previously worked fine on the same board. That chip apparently now throws a "4D" code too, pointing at the motherboard itself as the culprit, not just the CPU. There's no confirmation yet on whether a faulty BIOS, a bad batch of boards, or something else is to blame, and ASUS hasn't commented on this specific case. It is worth noting that the ASUS board was not new, and it had undergone USB-related repairs and a BIOS rewrite. The user has since contacted AMD in Brazil for an RMA, but has shared no updates yet.
207 Comments on Redditor's AMD Ryzen 9 9950X3D Reportedly Dies Shortly After Changing Motherboards
if anything, it could have been a botched USB related repair, and flashing the wrong BIOS in it...
heck, it could have also been user error with a standoff shorting out something on the motherboard
And then the mobo is all smoked up like it's been rescued from a fire. And the CPU looks all gunked top side too, as if he'd used way too much thermal paste - which also looks to be the electrically conductive type.
At least we're onto something regarding the other exploding X3Ds. Maybe they were also "one click overclocked"?
She uses this system for work, and the reason for the motherboard swap is that when she was using the processor with the AsRock motherboard, the system was experiencing instability such as USB dropouts and audio skipping. The refurbished ROG board was actually working fine with the 8500G, so the problem must already have been developing slowly in the AsRock and, if my theory is correct, the "generous" (although not entirely unsafe) voltages of the ASUS baseline presets probably finished the job.
A Q-Code "00" on an ASUS motherboard means "No CPU detected" - my best guess being, there is some sort of runaway condition that causes rapid degradation of a very specific circuit in the processor, the way AsRock programmed its BIOS routines seem to trigger the issue with particular ease and for whatever reason, AGESA's hardware safeties fail. 4D on the other hand is an initialization failure, which means either the power line to the CPU is toast (which COULD be caused by attempting to operate a damaged processor), or some other initialization related error, such as NVRAM still expecting a 9950X - I have no idea.
In any case, there was no overclocking involved.No, there are multiple documented cases of this issue occurring across multiple motherboards from numerous vendors. Most noteworthy in this particular case is that she was using BIOS 3902, which contains AGESA 1.3.0.1B Patch A, which means the issue is not yet resolved.
The community has been speculating that this problem might happen due to excessive voltage and current being applied on the CPU VDDIO line, both XMP/EXPO presets and motherboard reference presets seem to overshoot VDDIO and VDDQ quite high, in the 1.4V range. However, this alone doesn't justify the hardware physically bulging as it we have been seeing, it clearly means that some safety that the hardware should have is clearly not working. The replacement of the USB chipset should not affect any CPU-related functionality, and remember: there are two motherboards involved.
Since her CPU did not suffer some catastrophic physical bulge or extreme scorch marks like most documented cases thus far, we can correlate her dead chip with the socket AM5 pinout - the damaged pins seem to be related to MEM VDDIO and VSS (Row N 20 or thereabouts? Please help, my eyesight is no good). Too many little squares lol, but I will leave you with the reference:
Ryzen flame up problem has been around for a long time, it just never got the same wrath of Raptor Lake because it is much, much rarer and seems to occur in poorly understood waysFWIW, my A620A motherboard has no features that are considered "overclocking", like PBO, XFR, Curve Optimizer, etc. - but even this lowly motherboard does contain EXPO settings and ASUS memory presets section, so that is something that greatly weighs in the favor of those affected by this problem IMHO
P12: VSS
P13: VDDCR_SOC
The original SVG is much better.
upload.wikimedia.org/wikipedia/commons/2/2d/Socket_AM5_pinmap.svg?utm_source=commons.wikimedia.org&utm_campaign=index&utm_content=original
Do not buy second-handed not officially refurbished motherboards?
But yeah who knows what happened.
What's even more mind boggling is that my motherboard also has a setting called "memory overvoltage". Just... Why?
I wouldn't be surprised if it turned out that such settings were behind all these CPU deaths.Yes. Considering that even EXPO is considered overclocking... :)
The maximum officially supported memory speed is 5200 MHz on 7000 and 5600 MHz on 9000 series Ryzen. Somehow everybody seems to forget this.
Here is a log of a hardware monitoring I did on my Asus X670E crosshair hero (bios 3902, latest, as well) with stock voltages / EXPO 6000 enabled while stress testing CPU (7800X3D) and RAM with a full pass of all tests of ycruncher (see attached file). You can use log visualizer to open it and view every sensors readings over time.
Also added a screenshot of HWI window for a quick look of average / min / high as well.
Voltages are a bit on the high side of safe ranges but still not borderlining or past anything dangerous afaik.
From what you explained your friend's CPU could have been degrading and switching it to another motherboard could have precipitated its death. The origin of this degradation could very well have been the Asrock motherboard too. It could be worth checking the stock voltages it uses as well. But the fact that your friend's crosshair was refurbished might not be a coincidence too.
Delusional people I guess.
Also, God knows what Asus put into that memory profile that could have killed that CPU.Great! Thanks for coming. :)
I don't think I ever asked if she had a TPU account, but I'll ask and send the thread anyways, hopefully she can answer some of you guys' questions