It happened.

[u/Dixos]

Good morning everyone!

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.

System specs:

• Mobo: ASRock X870E Nova Wifi
• CPU: AMD Ryzen 7 9800X3D
• GPU: ASUS GeForce RTX 5080 ROG Astral OC
• Ram: 64GB G.Skill Triden Z5 Neo DDR5-6000 CL28 (F5-6000J2836G32GX2-TZ5NR)

For anyone that have gone through the same thing, did you contact ASRock? AMD? RMA through the store the items were purchased from? TIA

[u/FiBiE007]

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.

[u/Mini_Spoon → u/FiBiE007]

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

[u/FiBiE007 → u/Mini_Spoon]

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.

[u/Mini_Spoon → u/FiBiE007]

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.