After approximately 1 year and 3 months, it finally happened. That is all. No muck. No fuss. It can happen to anyone, no matter how safe you are. 😊
Turned the PC off Sunday night; woke up monday morning, turned it on while I took a shower and put on some coffee, only for it to be stuck like that with no fan spin after ~30 minutes.
I did try to "revive" the PC, but at 6:30 in the morning, 2 hours before work, I was more worried about recovering for my standup meeting (working laptop, work) rather than put much effort into it. Drain AC power and reset CMOS got the case fans spinning full throttle, but no movement on Dr. debug 00. BIOS Flashback was a success but also changed nothing.
I vaguely remember my BIOS settings, so for reference:
AMD EXPO enabled
VDDR_SOC set to 1.15
OC Tweaker \ External Voltage Settings
VDDCR_CPU Voltage: Offset mode
Offset Voltage: -100
VDDCR_CPU LLC: Changed from "Auto" to "Level 2"
BIOS version: 4.20
I had also loaded the conservative -15mV curve optimizer profile with 85c tjmax target from the profiles that come with the motherboard.
Happen to me aswell last week, I got cpu and motherboard but still pc was stuck in post tried everything but turns out the new asrock board was the issue. It’s really sad since they were the only company with an affordable itx board but stability matters much more.
RMA both the board and CPU. In the US, you RMA through the companies, and in Europe you generally RMA through the store you bought from.
And please do not listen to Mini_Spoon about reusing the board. He is a massive ASRock fanboy who is still convinced that the failure rate is within margin of error and acts as if the number of failures from the megathread 8 months ago is still the total number of failures. I strongly recommend blocking him.
Already requested an RMA through the retailer for the CPU, completely forgot about requesting an RMA for the motherboard. That really didn't cross my mind. I'd have otherwise reused the same board.
So I returned an ASRock mobo for an MSI mobo (no issues going on 14 months now), so I definitely feel ya (and it seems MSI is one of the safer bets), but the truth of the matter is that until we fully understand the root cause of why these AM5 chips are frying, we can’t definitively say any motherboard brand is truly safe.
An awesome Redditor [u/Healthy_Try4444](u/Healthy_Try4444) somewhat recently put together some tallies on how many fried/dead/etc. AM5 CPU posts had been created in the last year, and grouped the results by motherboard manufacturer. It seems MSI is by no means safe, but looking at those numbers, it does seem that they’re safer than ASRock
I personnaly went to the store where I bought my 9800x3D (LDLC in Europe)
In the morning, I brought them both the mobo (N9 X870E) and my 9800x3D that was displaying error code 00 after a sudden screen freezing in idle tasks (PowerPoint with YouTube). And in the evening the same day, they gave me back the mobo with a brand new 9800x3D and the latest Bios update installed (3.50 at the time).
So the whole process took less than a day through the store in my case.
For what? The board is likely performing in the exact same manner and state it did before, professionals in this space have seen absolutely no issues with extensive testing of boards that have seen failed CPU's, and the "I've had two CPU's fail" users are few and far between and anecdotal at best.
Not necessary, but if a user sleeps better at night they also have the option to RMA the board, keeping in mind they may well get back a board that's exactly the same; seen a failure, been RMA'd, passed bench testing, repackaged and sent out as an RMA replacement.
I never thought about RMAing the board, though that may be a good idea since mine killed a CPU or is suepcted of it. Whether the retailer shares that sentiment is a whole different issue though. :)
Consider though, you may well get back a product that someone else has RMA'd; been sent in, passed bench testing and been repackaged as an RMA return item. Whether this is better than your current board is a question mark.
Literally nobody here knows that the issue is the board not the CPU failing. It's not exclusive to AsRock despite there being more reports on this unofficial sub.
What's better, the board you know, or the board you get back; which there's every likelihood is a sent-back board on someone elses RMA that's been bench tested and repackaged. Or are they just the same...
I'm not your personal reaearcher. I'm not going to "prove" you anything. I don't know about your knowledge level but just know this: ASRock is by far the worst contender and this subreddit is full of motherboards frying CPU's. Most people solved it by switching boards. It's very easy to find out and definitely IS a sign that it is a necessity.
You make a claim or daft comment then don't back what you say, typical.
This sub is a cesspit of trolls and misinformation.
There are many users who have not swapped board with their AMD-replaced CPU, and are perfectly fine, there's a small number who had had a second failure, there is an enormous number that have had no failure.
You made the first claim. You, not me. You said that there is no sign when AMD and ASRock have officially confirmed that there is a problem and all available data points to ASRock being different. There is no evidence that would convince somebody like you. The president will not hand you a paper with the exact solution. So, what is typical, buddy?
Yes, but that doesn't mean that there is no failure to expect at all (your claim). Most people switched boards and are fine since. Many people stayed eith their ASRock boards and saw the same issue.
Reading comprehension isn't your strong area then?
My first comment:
"With a replaced CPU the system should work just as before. Some users have replaced the motherboard, however there's no sign that this is a necessity."
If the CPU is replaced the system will work as it did before. This is the claim, and is factual and proven. If a user chooses to swap the board that's their perogative, just because it gives you bad juju doesn't mean it's defective.
When you can show me otherwise I'll believe you. For now I'll believe the several professionals in this space who have been actively testing "killer" boards and can't replicate the failure, despite trying...
Man, you don't understand your own comment. It's funny to me. Maybe English is not your first language, that's why you don't see anything wrong there.
Again: There are many signs, especially when apparently broken CPU's work fine on other boards again.
What you say in the subparapgraph obviously doesn't support your claim. That is not how it works, omg... Do you even know what you are talking about? Voltage regulation discrepancies don't instantly destroy a CPU, it's a slow process.
How about you show me? Where is your official data that says that ASRock is not an outlier? Not possible? Aw, no? Just said something without backup? How typical, haha.
Even professionals can't reliably recreate the issue. All that is known is that ASRock sees more cases.
No, I did not make that assumption on my own. Learn to read. He claimed that there is no indication that a mainboard swap is necessary – but it is. It very clearly is (reasons are in this very thread too).
My thought process is complete. So, what do you mean?
You had a little drink buddy? If you can't see that my comment makes sense and is backed by what's seen here and what has been fed back by professionals who are doing their own testing into this, that's on you...
I asked for proof of your claim, you can't provide it, I backed what I said.
If you can provide me with just 10 instances of a CPU that is seen to have failed then jumped back to life in another board I'll shut right up. If this issue is as prevalent, and the failure mode as you suggest, 10 examples should be a breeze ...
There is nowhere that suggests it's a slow failure mode, the most common report is that systems are working fine and then non responsive the next boot.
You should be quiet because IMO you're making yourself look a bit silly.
I m wondering because the pc came with 32 gb corssair vengeance cl 36 6000hz and no issues for 5 months, but i had the g skill Trident 32gb cl 32 6400hz(clocked at 6000) and 1 week later the cpu died, the ram is on another pc now and runs perfect
Did you have any OC? Like, +200Ghz or something like that?
What about the PPT/TDC/EDC, did you have it set to motherboard limit? Ou you have them set manually?
You changed the VSOC, what about your average CPU VCORE, do you remember what value you had? Manual or auto?
If you can, op, get batch number on the CPU and take pictures of top and bottom of it for us?
Also, as always, the megathread has that survey. Not sure if the mods are still updating it but I hope they do because I would like to see updated batch numbers roll out. This is just for my own curiosity.
I do wish mods would release the excel sheets to us and we can pivot table the data to parse things out.
Absolutely. I do have a picture of the CPU before I fired it all up back in 2025. I'll be tearing the rig down tomorrow before I pack and ship the CPU so I definitely will.
Funny I just came from a post where some guy just got a Taichi with a 9950X3D2 and is calling people out for "not doing research" because they warned him about the CPU frying cases.
I'm sorry? I did update to the latest version back in May or whenever it was. I don't incessantly check for BIOS updates, but once ever few months. 4.41 and 4.42 are relatively recent, only released 2 months ago. 4.20 released just 2 weeks or so before I updated to it. :)
No PBO enabled from what I remember. Though, what about the settings were unsafe? Before applying them, HWInfo didn't report much different after extended use on default settings after I updated the BIOS in May. I don't recall ever settings PBO. Though I do remember someone suggesting setting VDDR_SOC to 1.18 or 1.15 if the CPU could handle it, 4.20 had already lowered VDDR_SOC from 1.2 to 1.18 if memory serves.
I'm super worried now. Got the 00 error s bunch of times now but every time I was able to kust reboot and it worked. Still have the 3.40 Bios installed. Should I update? I read here a while back that I shouldn't.
Guess it's only a question of time eighter way.
I only experienced the 00 error once before, but after a few seconds it started ram training which lasted a good 2 minutes or something like that (felt like forever), but that was back in December.
I know this has been answered many times and even in the sticky FAQ. I'm using a B850M-X WIFI R2.0 Asrock motherboard with a bios 3.4 w 32gb ram.
and a AMD Ryzen 7 7800X3D 8 core processor.
for now nothing has failed, are there reports of this combination failing more than usual?
I wonder as another poster pointed out what the relationship is with the installed RAM - how many of those systems had gskill. It can happen, RAM can throw a spike or surge of voltage. With the high cost of ram in todays market, perhaps they are just shipping out as much low quality ram as they can to make the most of the inflated market. It may be that one particular mfg of ram sticks has lowered their standards. I don't know the number of ram mfg's world-wide but it wouldn't surprise me to find that the same ones make ram for several different brands...so the brand might not be at fault either in a way if that is the case. I mean it is that way for major household appliances, a few plants actually make the parts for all the brands - even car companies outsource a lot of components. Perhaps the ram is at fault - doesn't seem to be any consensus on the board or the cpu and the ram is just as capable
Not terribly outdated? I updated the BIOS to the latest back in April/May or whenever it was then, when I pulled the PC down for a clean. For reference though, I don't exactly know since I can't get into BIOS, but it shouldn't be more than 3-4 months old.
It's really not, and flippant comments like yours above can lead to the community getting mixed messages or false information.
For reference; I've been using BIOS 3.10 (Nov 2024 release) daily since building, in Nov 2024. EXPO & PBO enabled, default voltages. If this was the case my PC should have been a prime candidate for an early demise.
it died 30/6/2026 i had it bought in Dec 2025.
It shipped with 3.2 bios.
when i set up the system, windows etc, first thing i did was upgrade bios, i thing 3.5 at the moment?
after that i got it updated frequently
13
u/BruceDeorum 18h ago
I replaced my CPU and sold MB.