AMD Ryzen 7 7800X3D CPU Burns Up

[jigger]

Just saw the video, glad i wasnt an early adopter of am5, its been a train wreck from the start.
Now light has been shed on this hopefully amd can get their act together and people haven't lost too much hope in them. A proper permanent fix is what people are still awaiting.

Those who havent had issues yet, im wondering if the life span of the cpus has been hit hard and will end up with issues 5-6 years down the line

Now we’re at the point where tiny little chips on incomprehensibly small manufacturing scales can offer such high levels of performance density, OEMs need to really step up even for retail products, motherboard manufacturers should offer closer to enterprise levels of qualification. Setting voltages outside of specs just so you can copy and paste as many memory venders parts as possible to QVL is not going to fly.

If I was the chip maker, any OEM caught colouring outside the lines without permission would get spanked.

Maybe the difference between working with a massive, ancient chip design on Intel and modern 5nm with AMD is where firms are going wrong.
With Intel and it’s chips firmly based on half shrinks you probably can just pump more volts to gain compatibility. Maybe Asus think the same can apply to AMD, and don’t realise this isn’t a rehashed 22nm Skylake chip.

 

[jigger]

Hopefully the end result of all of this is that reviewers and possibly even motherboard manufacturers will concentrate on things that count, such as board quality, accurate voltages set in the bios etc, instead of the current "gamer" more RGB, more volts = more fps nonsense.

A shame there are no viable no nonsense boards available from any manufacturer, high spec, high quality components, with a nice green no bs pcb. Ohh and proper documentation would be nice. I haven't seen a manual for a bios that actually explains what each setting actually does for years. Nor any real change log for when a new bios is issued.

There is no excuse that a board provides different voltages to what is actually set in in the bios. Currently a lot of the boards supply way over spec voltages to multiple components to either enhance performance or compatibility/stability with ram etc. Even my Asus z690 Intel board with a 13900k using bios defaults massively overvolts the system causing extreme heat & power consumption making it unusable. (not to the extent here - however I have not tried) . The first thing I did was undervolt it. Whilst it's obvious a lot of us here do like a bit over overclocking etc. Having it at default raise things beyond spec to edge out over the competition is a issue here. The push for a couple of fps to try and and validate the cost of a £700+ motherboard is a problem.

I could get behind products like that. Green PCB, multicoloured connectors, I don’t care. Put everything into quality and strip out all the fluff. Motherboard in a brown box, with the IO plate and a decent quality manual in large print.
Even swap the post code display for a beeper

 

[01001101]

I could get behind products like that. Green PCB, multicoloured connectors, I don’t care. Put everything into quality and strip out all the fluff. Motherboard in a brown box, with the IO plate and a decent quality manual in large print.
Even swap the post code display for a beeper

Just give us an instant bios access option without having to hammer del and I'm sold.

 

[Raiden85]

Pathetic quality control from AMD as well as the board vendors, really makes you worry about what protections may be broken or set to stupid levels on AM4. Hopefully that platform is fine considering how long it's been out, but I really hope AMD and board vendors look into potential issues on AM4 while they sort this AM5 mess out.

Just glad I've skipped AM5 so far as the 5800X3D has been working great for current high end gaming and hasn't self destructed yet, just hope by the time Ryzen 8000 series are out AMD as well as board vendors make sure their products are far more polished and aren't a ticking time bomb. It's worrying as I'm a user that leaves my PC on 24/7 so that last thing I want is a dead CPU and the board is still supplying lots of power because it thinks everything is fine and end up causing a fire.

 

[delta0]

Who else?

Gigabyte, MSI and ASRock according to GN.

 

[Cyber-Mav]

Maybe Asus think the same can apply to AMD, and don’t realise this isn’t a rehashed 22nm Skylake chip.

Going by the gamers nexus video it looks like its not an asus problem but an amd problem which they said needs to be addressed in the agesa and or chipset. Video also mentioned that amd needs to work more closely with mobo manufacturers, always found it odd that amd is not as tight knit with partners like intel is especially when providing fixes etc.

 

[Brizzles]

It seems that 'guidelines' laid down by AMD over the years have been treated exactly as that, just guide figures and mobo manufacturers have been adding their own tweaks to these guides.

As the cpu tech has got so fine tuned on the release models, the historical 'wiggle room ' has gone, or been greatly reduced.

AMD and the mobo manufactures need to implement a ' This is the hard limit ' and not play with guidelines anymore.

 

[Harlequin]

Going by the gamers nexus video it looks like its not an asus problem but an amd problem which they said needs to be addressed in the agesa and or chipset. Video also mentioned that amd needs to work more closely with mobo manufacturers, always found it odd that amd is not as tight knit with partners like intel is especially when providing fixes etc.

Going by the same video this is a motherboard makers problem. When the chip has died from overvolting , the board still pumps power into it, bypassing the CPU over voltage protection! Asus are known for this

 

[Harlequin]

It seems that 'guidelines' laid down by AMD over the years have been treated exactly as that, just guide figures and mobo manufacturers have been adding their own tweaks to these guides.

As the cpu tech has got so fine tuned on the release models, the historical 'wiggle room ' has gone, or been greatly reduced.

AMD and the mobo manufactures need to implement a ' This is the hard limit ' and not play with guidelines anymore.

They do in the tech docs, literally Asus ignored them.

 

[jigger]

Going by the gamers nexus video it looks like its not an asus problem but an amd problem which they said needs to be addressed in the agesa and or chipset. Video also mentioned that amd needs to work more closely with mobo manufacturers, always found it odd that amd is not as tight knit with partners like intel is especially when providing fixes etc.

Going by your post history, of course your opinion is this is AMD’s fault

Did you not read the rest of my post?

 

[Brizzles]

They do in the tech docs, literally Asus ignored them.

Wasn't just Asus though, was it.

 

[jigger]

Wasn't just Asus though, was it.

Seems like Asus was the only maker pushing the chips too hard, at least by default. The vast majority of failures are Asus boards, the others likely from manual overclocks and deaths from early failure.

 

[SkeeterUK]

Like most companies, if x failure rate is y then dont recall or do owt, if x failure rate is B then do somit as u cant cover up.

Asus be like tho, if youtuber wanabe tech guy shows u up, send the stealth assassins.

 

[Jamin280672]

The vast majority of failures are Asus boards, the others likely from manual overclocks and deaths from early failure.

ummm no, ASRock have had 2 chip failures, Gigabyte and MSI 1 to what we know of, all for the same reason, the motherboard has continued to pump current into the chip and fry the socket even after the chip has died causing the socket to burn and the chip to swell up, 1 of those was at default settings for everything, it was one of the chips sent into GN, how many have ASUS had ?

 

[Sythe79]

ummm no, ASRock have had 2 chip failures, Gigabyte and MSI 1 to what we know of, all for the same reason, the motherboard has continued to pump current into the chip and fry the socket even after the chip has died causing the socket to burn and the chip to swell up, 1 of those was at default settings for everything, it was one of the chips sent into GN, how many have ASUS had ?

To be fair, that's not true, the guy who sent it in said he wasn't running EXPO. Not running EXPO and running at stock are not the same thing if we assume they are being truthful.

About the only thing we do know for sure is everyone involved have been sloppy and lazy in both coding the bioses and testing these parts.

 

[01001101]

 

[Jamin280672]

To be fair, that's not true, the guy who sent it in said he wasn't running EXPO. Not running EXPO and running at stock are not the same thing if we assume they are being truthful.

I agree on the last part "if hes telling the truth", however, 4min 40sec in the GN video, User Skyfish lost his chip on a Gigabyte motherboard, he wasnt running EXPO, No OC and running factory settings, the motherboard survived though, the chip still died in the usual way'ish, he had only just finished the build, had booted to the bios once on bios F2 and was in the process of updating the board to bios F5 when the chip died.

Heres that mega thread here: https://www.reddit.com/r/Amd/comments/12yq4yb/megathread_for_am5_ryzen_7000/

 

[Raiden85]

Asus just has a lot more reports because it's a more popular brand.

 

[Brizzles]

Asus just has a lot more reports because it's a more popular brand.

Stop applying logic and reason, that will spoil certain peoples arguements.

 

[Sythe79]

I agree on the last part "if hes telling the truth", however, 4min 40sec in the GN video, User Skyfish lost his chip on a Gigabyte motherboard, he wasnt running EXPO, No OC and running factory settings, the motherboard survived though, the chip still died in the usual way'ish, he had only just finished the build, had booted to the bios once on bios F2 and was in the process of updating the board to bios F5 when the chip died.

Heres that mega thread here: https://www.reddit.com/r/Amd/comments/12yq4yb/megathread_for_am5_ryzen_7000/

Yup I'm not saying he's lying just we have No real way to know that the SOC was at 1.05 for example and still failed, in fact it seems to have died a little too quickly so either a faulty chip or really badly written BIOS code.