AMD identifies the root cause of Ryzen 7000 CPUs burnout issue, new AGESA released

[harlan4096]

AMD Ryzen 7000 series with new firmware solving burning out issues

AMD releases a statement and new firmware for board partners. 
 


AMD has seemingly solved the problem of burning Ryzen 7000 CPUs. The just-released AGESA  (firmware) for AMD 600 series motherboards will limit the SoC Voltage to 1.3V. This means AMD acknowledges that the root issue was the SoC Voltage going higher than AMD intended for their CPUs.

Although AMD does not specifically mention the Ryzen 7000X3D CPU series with 3D V-Cache, those CPUs were among the most affected (or reported) cases. This is likely because X3D series are more sensitive to such voltages.

AMD confirms that the new AGESA will not impact Ryzen 7000 memory overclocking capability, which in this case means using AMD EXPO or Intel XMP memory profiles. Furthermore, no changes to Precision Boost Technology will be applied.
 

We have root caused the issue and have already distributed a new AGESA that puts measures in place on certain power rails on AM5 motherboards to prevent the CPU from operating beyond its specification limits, including a cap on SOC voltage at 1.3V. None of these changes affect the ability of our Ryzen 7000 Series processors to overclock memory using EXPO or XMP kits or boost performance using PBO technology.

We expect all of our ODM partners to release new BIOS for their AM5 boards over the next few days. We recommend all users to check their motherboard manufacturers website and update their BIOS to ensure their system has the most up to date software for their processor.

Anyone whose CPU may have been impacted by this issue should contact AMD customer support. Our customer service team is aware of the situation and prioritizing these cases.
— AMD

Users who were affected by this problem are asked to contact AMD support. It is unclear if AMD is willing to offer any replacement for affected CPUs or how widespread this problem was in the first place. AMD and board partners are still collecting affected issues, but the quick response seemingly ends the problem for now.
...

Continue Reading