- AMD’s Ryzen processor burnouts have been a problem for some time
- Team Red has now clarified that this is a problem because some mother cards do not work with the recommended AMD values
- Instead, they grow too hard with power and tension – and burns are always reported daily
AMD officially commented on the destructive burnouts of the chips that affected a small number of its Ryzen processors, and actually put the blame on the feet of motherboard manufacturers – at one point, anyway.
Tom’s equipment noticed an interview with the leaders of AMD David McAfee and Travis Kirsch led by Quasarzone (a South Korean technological site) in which the RED team was questioned about the problem of professional exhaustion concerning the Ryzen (3D V-Cache or X3D chips, including the Ryzen 9800x3d), and mainly (but not exclusively) Ryzen 9800x3d), and mainly (but not exclusively) affecting Ryzen 9800x3d), and, and not exclusively) affecting Ryzen 9800x3d) and, and without exclusively) affecting Asrock.
Keeping in mind that it is a translated article – so we must be careful about interpretation – Quasarzone noted that processors in AM5 motherboards have “tested socket burnouts” and that “some users always signal these symptoms”. The technological site then asked what was AMD’s position and response concerning the problem.
AMD answered to say (again, remember that this is a translation): “This problem arises because certain bioses ODM do not adhere to the recommended values of AMD.”
The term ODM refers to the manufacturer of the motherboard (original design manufacturer), and what is essentially said is that these manufacturers do not stick to the stock market values of AMD (around power, voltage, etc.) with their boards. In other words, these companies grow stronger than they should, which could cause a problem.
This is not a final conclusion here, the spirit, because the leaders continue to say: “AMD … offers a wide range of combinations and also supports PBO [AMD’s automated performance boosting feature] and overclocking. This means that there are a large number of possible scenarios. Although it is a complex problem, we work in close collaboration with our partners to solve problems and further evolve the platform. “”
So, this is a complex problem to undo, and AMD stresses that he is working with motherboard manufacturers to solve any problem.
The leaders also mention that it is highly recommended that any owner of the AM5 motherboard updates to the latest version of the BIOS, which is good advice for any motherboard in equity. (The latest finished version of the BIOS, I must clarify – Do not try to use new versions which are still in beta).
Analysis: guess game
So, this is not a crystalline declaration of AMD by all means – and translation complications must be taken into account (yes, I hit a little, because it is an important shade) – but there is a fairly clear point in the direction of the manufacturers of motherboard pushing too far with their environments.
As mentioned, Asrock motherboards were particularly in the shooting line as a manufacturer of equipment that is most often reported (by a long way) – but other suppliers have also been affected by processor failure incidents.
While ASROCK initially blamed a “problem of compatibility of memory present in the versions of previous BIOS” and pushed an update of the BIOS to solve this problem, that did not do the trick to heal the Burnnets. As Tom’s equipment underlines, an update of the subsequent BIOS which arrived in May 2025 modified various PBO parameters and this (finally) smoothed most of the problems – if not all.
Unfortunately, there are still reports on Ryzen X3D processor burnouts that flow daily in Reddit, so it’s a thorn. Does Asrock still have work to do in terms of improvement of his organic to prevent these incidents? Or could this be a case of fleas that have already been pushed too hard, for too long, suffering from the damage caused under the hood and ultimately abandoned the ghost (the last update of the BIOS cannot save them, because they were too far)?
There is still too much guess, frankly, and it is an unfortunate situation for AMD and especially Asrock. Although it was not as if Intel had not had any worse problems – by that, I mean the smacas of instability with the processors of the 13th and 14th generation of Team Blue (it was quite saga).
