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
Add your own comment

207 Comments on Redditor's AMD Ryzen 9 9950X3D Reportedly Dies Shortly After Changing Motherboards

#76
Jtuck9
AusWolfSoC at 1.25 V isn't great, but VDDQ (also VDDIO, I assume) at 1.55 V is dangerously high. And that's at 4800 MHz? How high is it at 6200 MHz? I can't even fathom. :fear:
Yea, I only found out about those memory presets through that Skatterbench guide. The modules run hot as it is, especially in a MFF / SFF case. Would be nice if the board had a broader overall context of your cooling capability, but I suppose that is on you.
Posted on Reply
#77
Prima.Vera
Sorry, stupid question. Why not using an X870 motherboard?
Posted on Reply
#78
AusWolf
Jtuck9Yea, I only found out about those memory presets through that Skatterbench guide. The modules run hot as it is, especially in a MFF / SFF case. Would be nice if the board had a broader overall context of your cooling capability, but I suppose that is on you.
Or any context of what your RAM actually needs and what your CPU is capable of. Which confirms my theory, I guess...

1. Motherboard RAM profiles set idiotic values that are dangerous to your CPU.
2. CPU safeties don't kick in before catastrophic failure for some reason. Sensor placement problem? Manufacturing defect? Or does the motherboard disable them with the OC settings? This is the million dollar question.
Posted on Reply
#79
Jtuck9
AusWolfOr any context of what your RAM actually needs and what your CPU is capable of. Which confirms my theory, I guess...

1. Motherboard RAM profiles set idiotic values that are dangerous to your CPU.
2. CPU safeties don't kick in before catastrophic failure for some reason. Sensor placement problem? Manufacturing defect? Who knows.
Yea, again interesting to see failure rates across boards, pin sense / socket sense (if those are the correct terms) etc. I saw a video yesterday from a repair technician saying certain X870 boards have specialized chips (believe it was a clock sync chip in this case) which means it's cheaper to replace the board rather than source and replace the chip, so they just end up as e-waste. Data centre hardware sprang to mind...
Prima.VeraSorry, stupid question. Why not using an X870 motherboard?
Weren't people saying the upgrade wasn't really justified. Whether they'll rectify that with the next iteration?!
Posted on Reply
#80
Readlight
Where the plastic cover that was on AM3
Posted on Reply
#81
JimBob69
Asus aren't in the clear, but what's obvious is that ASRock poisons CPUs.
Posted on Reply
#82
AusWolf
Prima.VeraSorry, stupid question. Why not using an X870 motherboard?
Probably had it already. There's zero reason to upgrade as it's basically the same chipset.
Posted on Reply
#83
Sol_Badguy
My take on this.



These pictures need to be considered together, see the corner triangle and notch placement.
The two notches, north - south, which are offset relative to the middle of the socket, horizontally the portion toward the rear I/O is shorter than the portion toward the DIMMs.
Therefore the three scorched pins on the back of the CPU are closer to the DIMMs.
Solaris17T9: VDDCR
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
From what I can understand that pinout picture refers to the socket not the back of the CPU like this picture:

See the corner triangle and notch placement and compare with OP's CPU bottom view picture.
Therefore your interpretation of P12, P13 and T9 is incorrect as those pins would be closer to the rear I/O and not the DIMMs.

Thus on that socket pinout picture the three pins are actually:
P28 - VDDIO_MEM_S3
P29 - Test41
T32 - VSS
Posted on Reply
#84
LittleBro
Unlike previous one issue, this damage very closely mimmicks high damage done by high (SoC) voltage.

Anyway, two things are interesting:
- 2 CPUs died recently on the same board
- this particular ASUS board has experienced some serious repairs

Still, more info would be useful.

I suspect ASUS from releasing a piece of shit BIOS for this board. If you take a look at ASUS' support page,
you'll see this board gets BIOS update like every damn week. Every week there's a fix for some issue.
What the hell? No testiong prior to releasing new BIOS?
Posted on Reply
#85
starfals
Prima.VeraSorry, stupid question. Why not using an X870 motherboard?
Cus this whole platform was sold during the super high prices based on this? That u can use 1 motherbord for many generations? I also got that 1 gen MOBO + 7800X3D... i wont replace it either. When i get the next gen Ryzen stuff, the 10080X3D or whatever they call it. Plus if the old motherboards work, why not just get that 1? They are very similar, feature-wise... my board offers everything i can ever wish for.
Posted on Reply
#86
Tess
_roman_Let's do a quick check

Far too much thermal paste used which was put below on the pcb.




edit, checked a bit the text, maybe made a few passages friendlier, e.g beginner and not the other word
I agree... I knew there was a reason I replied to every youtuber ever with "Too much thermal pasted"!
And F Steve Burke for challenging me on that commonsensical reality!
It's of course the image we're not seeing that proves this!



:D Sorry guys, I couldn't help myself...
And that was actually an excellent critique @_roman_ !
Posted on Reply
#87
Recus
How AMD is still not sued?
Posted on Reply
#88
rv8000
AusWolfOr any context of what your RAM actually needs and what your CPU is capable of. Which confirms my theory, I guess...

1. Motherboard RAM profiles set idiotic values that are dangerous to your CPU.
2. CPU safeties don't kick in before catastrophic failure for some reason. Sensor placement problem? Manufacturing defect? Or does the motherboard disable them with the OC settings? This is the million dollar question.
Even my apex sets some idiotic values when things are left to auto. Case and point, auto vddg values get set to 1050mv even at FCLK 2000 when stock should be 850mv.

No one can say for sure but the user admitted to: sticks not being on qvl, being lazy, and using a memory profile not made for their kit as well as it likely being designed for a higher quality hynix kit. 1.55vdd/q is A LOT, and with no additional cooling, is asking for problems. I wouldn’t be surprised if that same profile had 1:1:1 settings for vddio/vdd/vddq.

The damage could have certainly been pre-existing, but the user seems to have no idea what they were doing with specific memory and bios settings.

USB dropouts and other onboard failures are general signs of instability, many times related to vsoc/fclk. Again it could have been a bad CPU, but the users recollection and explanations aren’t painting a good picture.
Posted on Reply
#89
Dr. Dro
AusWolfThere's this thing called physics that disagrees.



Also, have you heard about 7800X3Ds burning in mainly ASRock motherboards due to high SoC voltage, that AMD issued a limit for in an AGESA update? I'm sure you have.


Then you were lucky or had a good chip. X3D has a notoriously low tolerance towards overclocking.


I don't mean memory voltage directly. There's many things memory overclocking affects on an AM5 CPU. The IF and MC clocks, SoC voltage, VDDQ/VDDIO, etc.
Dielectric breakdown and electromigration both occur due to heat and strong current, I just don't think it's on the table for this case - both Lex and JustBenching are correct here.

My memory voltage point (DIMMs themselves) is 1.4 because it's air cooled. If just this was enough to damage a processor to the point of swelling AMD would not issue EXPO certifications for any kit in this frequency range.
danc00 doesnt mean a dead cpu. it can means it failed to startup after overclocking failure.

just power down, let everything discharge for 5 minutes and try powering up again. if it still fails, then do the cmos clear button thing.
Please read the post, and no, 00 means "no CPU detected", not a simple overclocking failure. You should never see a code 00, it's the worst kind of bad news.

The CMOS clear is the first thing anyone does when a computer doesn't POST after setting, there is clear hardware damage involved.
Prima.VeraSorry, stupid question. Why not using an X870 motherboard?
The X670 and X870 are physically the same chip, those with an E designation contain two chips. Technically doesn't matter, it's downstream I/O - since Ryzen is a system-on-a-chip it can operate without a chipset.
Posted on Reply
#90
Evrsr
ASUS is the company that was pushing Ryzen 2000 chips to support 3200MHz RAM by pushing SoC voltage 40%+, with seemingly no warning to the user.

Would you be surprised they do the same to get that extra 200MHz the user reports? I would not.
Posted on Reply
#91
R-T-B
freeagentGood luck on quick and timely RMA from AMD. Pretty sure I have been waiting 3 weeks for an approval or even just a reply. I just checked before making this post and still nothing.
So ironic, when I worked for TPU briefly and had a 1800X with the "linux abnormality" they overnighted a new one to me without questions and acted like they do that for everyone. I swear the press gets preferential treatment even when we explicitly tell them "please treat me like a normal peon, I am not acting in official capacity or writing a review"

My condolences on your timeframe. Chaotic neutral: If you want to speed it up, just tell them you are a mod here, lol.
Posted on Reply
#92
AusWolf
Dr. DroDielectric breakdown and electromigration both occur due to heat and strong current, I just don't think it's on the table for this case - both Lex and JustBenching are correct here.

My memory voltage point (DIMMs themselves) is 1.4 because it's air cooled. If just this was enough to damage a processor to the point of swelling AMD would not issue EXPO certifications for any kit in this frequency range.
1.4 V is high, but not enough for sudden catastrophic failure. However, there was a post earlier with a motherboard built-in Hynix profile that gave 1.55 VDDQ for 4800 MHz RAM. That's already on the border of dangerous, and not on the good side of that border. Imagine what a 6200 MHz profile would do.

A motherboard maker being irresponsible with their buli-in profiles is not surprising, imo.
Posted on Reply
#93
Yumi
rv8000Even my apex sets some idiotic values when things are left to auto. Case and point, auto vddg values get set to 1050mv even at FCLK 2000 when stock should be 850mv.

No one can say for sure but the user admitted to: sticks not being on qvl, being lazy, and using a memory profile not made for their kit as well as it likely being designed for a higher quality hynix kit. 1.55vdd/q is A LOT, and with no additional cooling, is asking for problems. I wouldn’t be surprised if that same profile had 1:1:1 settings for vddio/vdd/vddq.

The damage could have certainly been pre-existing, but the user seems to have no idea what they were doing with specific memory and bios settings.

USB dropouts and other onboard failures are general signs of instability, many times related to vsoc/fclk. Again it could have been a bad CPU, but the users recollection and explanations aren’t painting a good picture.
Hi, my ram sticks aren't on qvl for 6600mhz but they are for 6000mhz in ASRock board it's a Corsair Dominator Titanium 6600cl32 2x32, SKU: CMP64GX5M2X6600C32W, they are on qvl for Ryzen 7000 in ASRock board also, it's a "old" kit without expo

The pre built setup of rog extreme tweaker are based on RAM IC, my ICS are Hynix A-Die as you can see in this picture (I took this picture in march 2025, few months before the 9950x3d arrival)

I admit I was lazy to use the rog preset but this doesn't mean I wanst unaware the situation about the CPU/motherboard, that's why I tested both boards for 2 months and I knew my CPU could be damaged or the Asus could kill the chip, that's why I always stated the CPU died after the swap and the ASRock board shows no signs of life anymore, this board only had 2 CPU in that socket, a 9950x who died in 5 months after purchase with PCIE erros and tons of corrupted files and buggy temp reading and the 9950x3d who's sitting in that socket since may/June 2025 till this Sunday (9/6/2026)

The paste was gross, I knew but this was after the CPU removal, I didn't cleaned anything because I was testing both CPUs in both boards after the incident, now both are cleaned and AMD accepted the RMA, I sent them the same photos you saw on reddit
Prima.VeraSorry, stupid question. Why not using an X870 motherboard?
Isn't a stupid question, the reason was 2

First I already owned the hero board but after a bios update failure and a USB issue I sent to repair shop

Second the x670 and x870 are the same except for one more PCIE 5.0 and I'm not using any nvme 5.0 so there's no reason for me
Posted on Reply
#94
AusWolf
YumiThe pre built setup of rog extreme tweaker are based on RAM IC, my ICS are Hynix A-Die as you can see in this picture (I took this picture in march 2025, few months before the 9950x3d arrival)
Nah, I think those profiles are based on whatever weird stuff the guys at Asus were smoking on the day they set them up. I don't expect that any engineer made any testing on any of them ever.

Lesson learned, better stay away from built in memory profiles. They are irresponsible and dangerous.
YumiAMD accepted the RMA
That's good news! I wish you good luck, and thank you for sharing your story. :)
Posted on Reply
#95
Dr. Dro
AusWolf1.4 V is high, but not enough for sudden catastrophic failure. However, there was a post earlier with a motherboard built-in Hynix profile that gave 1.55 VDDQ for 4800 MHz RAM. That's already on the border of dangerous, and not on the good side of that border. Imagine what a 6200 MHz profile would do.

A motherboard maker being irresponsible with their buli-in profiles is not surprising, imo.
Yes but we are talking about CPUs that don't just fail, they go up in smoke, with the hardware physically bloating and shorting every pin around it, often resulting in a fire. The voltages required to do this should be off the charts high, not dipping your toes in the hot zone :p
Posted on Reply
#96
AusWolf
Dr. DroYes but we are talking about CPUs that don't just fail, they go up in smoke, with the hardware physically bloating and shorting every pin around it, often resulting in a fire. The voltages required to do this should be off the charts high, not dipping your toes in the hot zone :p
That's what I meant - if a 4800 MHz profile contains dangerously high voltages (which are in no way necessary for basic bitch JEDEC RAM speed), then imagine what a 6200 MHz profile does.
Posted on Reply
#97
Dr. Dro
AusWolfThat's what I meant - if a 4800 MHz profile contains dangerously high voltages (which are in no way necessary for basic bitch JEDEC RAM speed), then imagine what a 6200 MHz profile does.
Not even a full excess volt here would cause such catastrophic damage if there wasn't a fault somewhere, that's the point people are trying to make, stuff isn't made of sugar ;)
Posted on Reply
#98
AusWolf
Dr. DroNot even a full excess volt here would cause such catastrophic damage if there wasn't a fault somewhere, that's the point people are trying to make, stuff isn't made of sugar ;)
After a quick googling, I'm not so sure about that. I don't want to post another AI-aggregated screenshot, but basically consensus is that voltage above 1.5 V on the memory controller drastically shortens lifespan, while at around 2 V, you can instantly fry your CPU. Over temperature protection doesn't pick up on it, either (why that is would be a great question).

Intel's recent 13-14th green degradation fiasco wasn't about dangerously high voltages, either, as far as I recall.
Posted on Reply
#99
Dr. Dro
AusWolfAfter a quick googling, I'm not so sure about that. I don't want to post another AI-aggregated screenshot, but basically consensus is that voltage above 1.5 V on the memory controller drastically shortens lifespan, while at around 2 V, you can instantly fry your CPU. Over temperature protection doesn't pick up on it, either (why that is would be a great question).

Intel's recent 13-14th green degradation fiasco wasn't about dangerously high voltages, either, as far as I recall.
Yes, but I'm not talking about merely just killing the CPU, but the fireworks spectacle, like see this case. this is extreme physical damage.

Raptor Lake was degrading for a similar reason, high volts + high current = dielectric breakdown, accelerated electromigration, dead CPU, but even then, they did not combust like this

Posted on Reply
#100
Yumi
AusWolfNah, I think those profiles are based on whatever weird stuff the guys at Asus were smoking on the day they set them up. I don't expect that any engineer made any testing on any of them ever.

Lesson learned, better stay away from built in memory profiles. They are irresponsible and dangerous.


That's good news! I wish you good luck, and thank you for sharing your story. :)
Thanks, i'm sorry to make a fuss about this, i ordered a Intel kit to replace the Am5 asap because i need to work, here's some pics

Both boards will remain stored till i'll decide what to do with them, maybe i'll buy another CPU with x3d cache to test again the X670E Crosshair Hero, but first i'll send them to a repair shop to check if nothing happened to both board since the ASROCK is dead solid after the removal of the 9950x3d
Posted on Reply
Add your own comment
Nov 11th, 2026 04:18 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts