JimBo72

AMD has now specified that the issue is SoC voltage in a follow up statement. https://www.tomshardware.com/news/amd-issues-follow-up-state...

ASUS pointing out that they are defining new rules for vCore and SoC voltage to address these issues is in fact pointing to that as the issue. They aren't just "throwing that in there" because it is unrelated. If you need it to be even more direct, here is the statement from ASUS that says it is SoC voltage.

https://twitter.com/ASUSTechMKTJJ/status/1650920434404331520

Here is the statement from Biostar that says SoC voltages are being limited:

https://www.biostar.com.tw/app/en/news/news.php?S_ID=559

You've admitted that you work for AMD, which would make a casual observer think that you are being biased in your comments. There is verifiable proof of the correlation with SoC voltage from the ODMs themselves.

Four motherboard makers have come forward and issued press releases about new firmware they are releasing that limits the SoC voltage, thus preventing this issue. What further evidence is needed?

The press releases from the motherboard vendors are 100% proof that these failures are real and a problem. They all cite new firmware that limits SoC voltage, thus showing the analysis in the article is correct.

The four motherboard makers that have issued public press releases about revised firmware that is designed specifically to limit the SoC voltage to prevent failures would disagree with you here. If that isn't a public admission of this being the source of the failure, what is?

This is incorrect. Multiple instances (more than 6) have thus far been reported and pictured. All four major motherboard OEMs have now come forward with patches that are designed to limit the voltage. You can see their press releases in the link below.

These companies aren't making public statements about changes to their firmware to prevent failures for no reason.

https://www.tomshardware.com/news/preventing-ryzen-burnout-m...