KitGuru KitGuru.net – Tech News | Hardware News | Hardware Reviews | IOS | Mobile | Gaming | Graphics Cards
AMD has finally broken its silence on the socket burnout issue that has been affecting some AM5 users, particularly those with high-end X3D processors. In a recent Q&A session, AMD representatives addressed the problem, attributing the root cause to motherboard partner BIOS settings that deviate from the company's recommended specifications.
Speaking to Quasarzone (via Wccftech), AMD's David McAfee and Travis Kirsch explained that some ODMs (Original Design Manufacturer) BIOSes were the source of the problem. They stated the issue is complex, but the core of their message is that partners pushing CPUs beyond their preset voltage and power specifications is the primary cause. As a result, AMD is now strongly advising all AM5 customers to update their motherboard to the latest available BIOS version to ensure their system is running within safe parameters.
The burnout issue started by gaining attention on forums like Reddit earlier this year, with a disproportionate number of failure reports coming from users with ASRock motherboards paired with the Ryzen 7 9800X3D gaming CPU. In the most severe cases, the failures resulted in visible burn damage to both the CPU and the motherboard socket itself. ASRock was proactive in investigating the issue, and after several BIOS revisions, the company released an update in May that adjusted various PBO and voltage settings. This update has reportedly resolved the problem for the vast majority of affected users.
While ASRock's BIOS updates appear to have largely mitigated the problem, AMD's official statement now provides more clarity on the underlying cause. It's a reminder that while board partners often tune their BIOS to squeeze out extra performance, it can sometimes come at the cost of stability and, in this rare case, the health of your hardware. If you're running an AM5 system, make sure you update your BIOS.
Discuss on our Facebook page, HERE.
KitGuru says: Were you affected by this issue? How did you solve it?
