News AMD 9800X3D 'failures/deaths' Reddit megathread indicates the vast majority may be happening on ASRock motherboards

[SomeoneElse23]

This smacks of insufficient "revision testing" to uncover firmware bugs.
https://fastercapital.com/content/F...o-Test-Your-Product-for-Firmware-Quality.html

At work we spend weeks testing each new firmware update on aeronautics hardware. The test rigs generate copious amounts of data which is then passed back to the software design team.

When working in the Aerospace industry, you don't want planes, rockets and satellites falling out of the sky, just because you've failed to test hardware/firmware/software thoroughly.

Asrock (and all the other motherboard manufacturers) together with AMD are faced with similar problems, each time AGESA is updated. I guess they just don't spend as many millions of dollars revision testing on commercial CPU/motherboards as some industries do.

Corporations generally do the absolute minimum necessary for their products. If they think they can get away with it, they will try it.

Aerospace has to do this testing, so they do.

Consumer electronics don't, so they don't.

 

[qxp]

Corporations generally do the absolute minimum necessary for their products. If they think they can get away with it, they will try it.

Aerospace has to do this testing, so they do.

Consumer electronics don't, so they don't.

A long while back when computers were new, writing computer code was treated as an engineering discipline.
After all, computer code is just a bunch of mathematical formulas and you should be able to go through it line by line and prove that everything is correct. The computers kept getting bigger, the code kept getting more lines and the trend was that the cost of computer programs was going to be exponentially more than the hardware.

This got solved by innovation of not checking your code that thoroughly - turned out consumers preferred buggy code they could afford to the well-checked code they could not. Everybody learned to save your work often because you don't know when its going to crash.

Nowadays we have automated tools to check our code, and the computers got powerful enough so that you can waste cycles running interpreted code that is easier to get right. The code crashes rarely, but is connected to the Internet and now people have to find ways to write code that is mathematically correct, lest someone finds a 0-day exploit and owns the system.

 

[DS426]

I was actually going for that exact board. I spent weeks trying for either that board or the Taichi Lite. I only ended up with the Tachi Lite because it was available for a few minutes whereas the Nova never was. I am guessing the Nova is just used more as it is the best bang for buck board for the X870E chipset.

Nah, I'm a fan of the Taichi lite as it's basically a Taichi without the bling and associated cost. Nova might look like a good value on paper but it now appears some corners were cut somewhere.

 

[DS426]

Corporations generally do the absolute minimum necessary for their products. If they think they can get away with it, they will try it.

Aerospace has to do this testing, so they do.

Consumer electronics don't, so they don't.

Aerospace and consumer tech have very different risk tolerances, yes -- for obvious reasons. In consumer tech, competition is fierce, so if there's no perceivable advantage to continue testing (or rather it diminishes margins to almost nothing), extra stringent testing isn't going to occur. Generally, most companies do more thorough testing and validation for business-class products, e.g. you just don't see stuff like this on EPYC processors, including the ones with 3D V-Cache.

This CPU is also a big physical departure from previous designs -- it's not just an iteration on the same old x86 CPU design. That adds a degree of uncertainty.

 

[Ogotai]

AMD is the one that knew about the problem from the 7000 series and didn't fix it, AMD knew they had no over volt protection on the vsoc and they just don't care.

you mean just like how intel knew about the degradation issues their own cpus have, but did squat about for what was it, 1.5 years apparently, cause in tel just done care as well ??

come on terry... intel does the same basic things, as you accuse amd of.. but yet you dont say squat about that, but harp on amd left right and center for any thing they do wrong.

 

[TerryLaze]

you mean just like how intel knew about the degradation issues their own cpus have, but did squat about for what was it, 1.5 years apparently, cause in tel just done care as well ??

come on terry... intel does the same basic things, as you accuse amd of.. but yet you dont say squat about that, but harp on amd left right and center for any thing they do wrong.

So you agree that amd did what I said, so what is your problem?! Why should I mention intel in an amd thread?! Why do you mention intel in an amd thread? Just to reflect from the issue and to pull a fast one on intel?
So why do you harp on about intel left and right and center on anything they do wrong?

 

[nogaard777]

The vast majority are occurring on Asrock boards so the problem lies there right? Ironic that no one said the same when the vast majority of failing Intel chips were on Asus boards. 🤔 Really shows the difference in how AMD is always innocent while Intel is always guilty

 

[nogaard777]

you mean just like how intel knew about the degradation issues their own cpus have, but did squat about for what was it, 1.5 years apparently, cause in tel just done care as well ??

come on terry... intel does the same basic things, as you accuse amd of.. but yet you dont say squat about that, but harp on amd left right and center for any thing they do wrong.

Yes, exactly like that. So you see the irony that when Intel does it everyone dogpiles on Intel but when AMD does it everyone's running defense for them? When AMD chips are failing everyone points the finger at Asrock because that's where the majority of issues are, but when the exact same thing happens with Intel on Asus boards I don't remember anyone blaming Asus, and this was even as GN and J2C was pointing out all the shady crap Asus has been pulling.

 

[rambo919]

The vast majority are occurring on Asrock boards so the problem lies there right? Ironic that no one said the same when the vast majority of failing Intel chips were on Asus boards. 🤔 Really shows the difference in how AMD is always innocent while Intel is always guilty

If the primary source is an asrock subreddit.... it tends to skew results no?

This is also only happening on a specific CPU.... not two whole generations.

 

[TerryLaze]

This is also only happening on a specific CPU.... not two whole generations.

Ryzen had problems with working with specific ram since 2017 when they first came out....

 

[Gururu]

So you agree that amd did what I said, so what is your problem?! Why should I mention intel in an amd thread?! Why do you mention intel in an amd thread? Just to reflect from the issue and to pull a fast one on intel?
So why do you harp on about intel left and right and center on anything they do wrong?

Intel rightfully got flogged for this to the point people (many who didn't even own a 13th/14th chip) want to see them burn to the ground. Is the title for this thread still current? Are we still looking at a chip or ASRock problem?

 

[rambo919]

Ryzen had problems with working with specific ram since 2017 when they first came out....

Yeah it is funny when people refuse to admit AM5 specifically has initial RAM stability problems.... but boot problems due to RAM issues is basically a nothing-burger.

It's when your CPU is a ticking time bomb that might become half useless and in the event you might not be able to have it returned.... THAT is when people start getting upset.

 

[TerryLaze]

It's when your CPU is a ticking time bomb that might become half useless and in the event you might not be able to have it returned.... THAT is when people start getting upset.

So like in this article where CPUs just stop working after working fine for a while?!

"Some 9800X3D's are allegedly dying during boot-up, while some are dying within hours, days, or weeks of ownership. Some reports also claim their CPUs were dead on arrival. "

 

[TerryLaze]

Intel rightfully got flogged for this to the point people (many who didn't even own a 13th/14th chip) want to see them burn to the ground. Is the title for this thread still current? Are we still looking at a chip or ASRock problem?

Was it rightfully or was it just a "media" (influencers) witch-hunt to make intel look bad?!
If you had a system tuned for stability then 13th and 14th gen was more stable than ryzen.
It's only when you go with dudebro mobos that have everything dialed to 11 that you get some CPUs that degrade faster than older ones.

https://www.techpowerup.com/325250/...lure-rate-than-intel-13th-and-14th-generation

 

[rambo919]

So like in this article where CPUs just stop working after working fine for a while?!

"Some 9800X3D's are allegedly dying during boot-up, while some are dying within hours, days, or weeks of ownership. Some reports also claim their CPUs were dead on arrival. "

Yeah.... it's unclear how much of that is user error, how much is asrock error and how much is AMD error. Remember that it also took many months for the intel scandal to reach a point where people were certain that both intel and the mobo manufacturers were at fault.

You are merely being too hasty for outrage.

The funny thing about that graph every time someone trots it out.... very few people had actually experienced a CPU dying before the the whole thing it means to disprove started. Personally I have never had a CPU die on me once in my life... same for RAM. And if you take a gander at the comments of the thread you linked you would notice that Puget does not exactly have a stellar reputation with everyone.

But please, point out how all the 11th gen CPU's were dying but no one ever seemed to notice?