News Two Ryzen 7 9800X3D CPUs burned out on X870 motherboards — vendor investigates the Ryzen burnout issues

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
AMD should have stick to the pin grid method it's the best .....the pinless AM5 it's cool but it's pinless is something else...I hope AMD rectify this problem
 
It was actually Asus and Gigabyte boosting voltages to get the motherboard crown for performance that was the issue. Funny enough, after AMD pushed new BIOS for AIBs to not been able to do that with x3D, there never was a single more occurance.

Not to mention, all these issues were on ASUS and Gigabyte motherboards only.

Happened to me last year with a 7950x3D and the board I am running now... MSI MAG X670E Tomahawk. About a week after I built the PC in April 2023 I heard a pop while gaming and everything was dead. NewEgg replaced the CPU and board no questions asked.

After commenting on one of the GN videos about it Steve offered to buy both parts from me for analysis... but I had already shipped them back.

A BIOS update led to no further issues and I have since built another AMD system.


The cause of this was already investigated it was 100% motherboards with increased voltage.

Yep... I didn't lose any sleep over it.
 
We don’t know if the burn marks are a result of incorrect installation causing a misalignment or if they are caused by a factory non-conformance.
No, we don't. The point newtechldtech was making though is that the burn marks match up with the proper orientation so it was installed in the correct orientation when the damage occurred.

Something other posters seem to have missed is that the CPU is made with offset notches that match up with the socket, forcing you to use the proper orientation.

The damage in the top left isn't necessarily from improper installation either. I've seen similar damage on all kinds of electronics during my lifetime, all caused by the manufacturer.
 
  • Like
Reactions: KyaraM
No, we don't. The point newtechldtech was making though is that the burn marks match up with the proper orientation so it was installed in the correct orientation when the damage occurred.

Something other posters seem to have missed is that the CPU is made with offset notches that match up with the socket, forcing you to use the proper orientation.

The damage in the top left isn't necessarily from improper installation either. I've seen similar damage on all kinds of electronics during my lifetime, all caused by the manufacturer.

All true, but as yet we don’t have enough information to draw any conclusions.

Looking at the photos of the socket it shows signs of damage. If you install a zen 5 cpu properly it isn’t possible to damage the socket in the manner shown as the socket isn’t stressed. Pressure is applied to the IHS tabs but not the socket.
Could the damage have allowed a misalignment? Could the cpu have been forced in? Could the motherboard be at fault?

Tune in to the Internet next week for the results of some YouTubers deep inspection!
 
  • Like
Reactions: bit_user
I suspect someone probably made this point already on the thread, if so , apologies.
It does seem this is all a nothing burger. The CPU's it appears were installed incorrectly.

Question to ask, an experience PC builder is unlikely to make this school boy error? I mean, and apologies for the metaphor; if you're holding your personal jewels in your hand you place them down correctly, surely, not unless you're well endow with wealth and have no concept of value.

Conspiracy Theory? Or is Intel trying to fight back dirty, now that the momentum is with the Red Team?
 
  • Like
Reactions: tommo1982
buildzoid explained this. The user installed the cpu while the mobo was vertically. gravity did his thing and the cpu went out of the socket The user closed the latch and this happened. Case closed.
Odd way of installing CPU. I always place the case on its side, simply to have good access, even if it's inconvenient. Too many things can go wrong otherwise. Such is this example.
 
The Housing for the CPU has been damaged.
View: https://imgur.com/a/RDKZto4

I have highlighted the area of damage in this image.

This type of CPU mount damage happens from one of three reasons.
1) The fastening lever has applied too much pressure to the CPU plate upon securing CPU to the housing.
2) The CPU cooler/AIO was secured onto the plating too tightly, causing the mounting pins to buckle and cross under the pressure - Possibly wrong mounting screws used.
3) Genuine defect in manufacturing process where the CPU housing is uneven along its general securing area.

Can definitely rule out processor being secured with corners facing the wrong side. Arrow(triangle) was correctly aligned which is visible with the evident burn on pin contacts from both CPU and the Mount.
 
  • Like
Reactions: KyaraM and bit_user
Also Pebcak. Problem Exists Between Chair and Keyboard.
Hahahaha, love it! 😁

You might like my idea of what BMW stands for...

Bankrupt Myself Willingly 😉
I want to say in a very recent Jayz2Cents video they accidentally forgot to plug a 12VHPWR connector in all the way while they were testing an Arrowlake system?
That's pretty funny because Jay is YouTube's ultimate nVidia fanboy. You'd think that he'd remember something like that. 😆

I'm just glad that ATi decided to NOT use that dumb connector. One less think to worry about on my XTX. 😁
You are a genius or something?

It is not MSI's fault, it is the fault of the user who installed the CPU backward without noticing it.

View: https://youtu.be/qY0kEB-1MIc
I agree with you, it's not MSi's fault. Having said that, they're a terrible company and I won't touch anything from them either. Not because their products are especially bad, but because their customer service is.
 
Nvidia 12vhpower not installed correctly - nvidia should have predicted that people will fail to connect it and should have made it safer.

Amd's socket killing chips, oh well it's the user not installing it correctly.

Okay.
not the same.

the problem with the nvidia issue is people said exactly this "skill issue" and "failed to install it correctly", in fact i am pretty sure that was nvidia's origional response, after finally admitting it was happening.

and it was right, for most of the cases. the problem is it wasn't right for ALL of the cases. there is a problem with that plug in certain use situations. worse one of the prime fixes (the cable mod one) turned out to make the problem worse by being faulty. there are working solutions to the certain use problems (bending the cable to fit into a case) now, so all the criticism did resolve the issue after making the problem worse.

this is a super obvious socket issue. either he installed it wrong, or MSI is selling deformed sockets. I wouldn't doubt either as being the problem. but i think if msi was selling faulty sockets more people would be complaining by now.
 
not the same.

the problem with the nvidia issue is people said exactly this "skill issue" and "failed to install it correctly", in fact i am pretty sure that was nvidia's origional response, after finally admitting it was happening.

and it was right, for most of the cases. the problem is it wasn't right for ALL of the cases. there is a problem with that plug in certain use situations. worse one of the prime fixes (the cable mod one) turned out to make the problem worse by being faulty. there are working solutions to the certain use problems (bending the cable to fit into a case) now, so all the criticism did resolve the issue after making the problem worse.

this is a super obvious socket issue. either he installed it wrong, or MSI is selling deformed sockets. I wouldn't doubt either as being the problem. but i think if msi was selling faulty sockets more people would be complaining by now.
I think the other poster means that this is what people said, not what actually was the issue. Believe me, even after Youtubers posted proof of user error, I have seen enough people digging their heels in staying with the "it's entirely and solely Nvidia's fault!"-narrative, instead of admitting that the main, though not only, possible issue was in front of the system. They, in fact, still put all the blame on manufacturer error to this day.
 
I think the other poster means that this is what people said, not what actually was the issue. Believe me, even after Youtubers posted proof of user error, I have seen enough people digging their heels in staying with the "it's entirely and solely Nvidia's fault!"-narrative, instead of admitting that the main, though not only, possible issue was in front of the system. They, in fact, still put all the blame on manufacturer error to this day.
Well, I don't agree that most of the issue was the user in the 12vhpwr issue. It was their first release with the new connector, and in the founders edition card they know their card height, and then they bundle an adapter with a straight plug, which, for most PC case out there will need a tight bend against the PCISIG spec bending radius and cause potential problem unless one would use a vertical mount and let it dangle upward without trying to cable manage it. That is very different from a LGA socket being forced close with the CPU misaligned.
 
  • Like
Reactions: stuff and nonesense
Well, I don't agree that most of the issue was the user in the 12vhpwr issue. It was their first release with the new connector, and in the founders edition card they know their card height, and then they bundle an adapter with a straight plug, which, for most PC case out there will need a tight bend against the PCISIG spec bending radius and cause potential problem unless one would use a vertical mount and let it dangle upward without trying to cable manage it. That is very different from a LGA socket being forced close with the CPU misaligned.


That a connector can be so easily misconnected makes it flawed. Its use in GPUs with sometimes necessary a cable bend radius tighter than recommended by PCI SIG makes it unsuitable, not fit for this purpose. The connector isn’t inherently bad, it’s just not the right connector for the task.

Card makers don’t make it easy, burying the connector in the card on a 90° bent receptacle can make it awkward to properly connect safely. Hiding the mating face behind the heat shrink shroud makes it hard to verify that the connection is solid. Later cable ends are colour coded, a tell tale to highlight that it is badly mated - earlier cables didn’t have this luxury.

Implementations should fully follow a set of rules, a defined standard.

A thought, a straight connector, cable coming away from the PCB, in an area clear of the heatsink or on the rear of the card would have made the problem moot. There would be no need to bend cables, the connection could be seen and inspected.
 
  • Like
Reactions: YSCCC and bit_user
That a connector can be so easily misconnected makes it flawed. Its use in GPUs with sometimes necessary a cable bend radius tighter than recommended by PCI SIG makes it unsuitable, not fit for this purpose. The connector isn’t inherently bad, it’s just not the right connector for the task.

Card makers don’t make it easy, burying the connector in the card on a 90° bent receptacle can make it awkward to properly connect safely. Hiding the mating face behind the heat shrink shroud makes it hard to verify that the connection is solid. Later cable ends are colour coded, a tell tale to highlight that it is badly mated - earlier cables didn’t have this luxury.

Implementations should fully follow a set of rules, a defined standard.

A thought, a straight connector, cable coming away from the PCB, in an area clear of the heatsink or on the rear of the card would have made the problem moot. There would be no need to bend cables, the connection could be seen and inspected.
The last part was kind of done is some gigabyte cards where they forgo a part of the hs to let the cable exit along the card’s “end”, but it also comes in another trouble as cards are so long nowadays case fitting is very tight unless one is using those full tower huge cases and dual chambers. The connector is inherently difficult to make sure it’s fully connected compared to the bigger 8pin of the old standard and it’s actually the card size at the debut generation making it much worse.