Preventing Ryzen Burnout: Motherboard Makers Issue New Firmware

Biostar updates AM5 motherboard BIOS
(Image credit: Biostar)

Motherboard makers have been swift to respond with firmware updates, now that AMD has released an official statement regarding the worrying spate of ‘Ryzen burn out’ issues. Today we have seen all the major AM5 motherboard partners release or announce mitigating motherboard BIOS updates. Thus, we have statements from the likes of Asus, Gigabyte, MSI, and Biostar to share with you, and we will look at what each vendor has to say about their updates. We will cover these updates in alphabetical order.

Asus AM5 Updates

Latest Videos FromTom's Hardware
Mark Tyson
News Editor

Mark Tyson is a news editor at Tom's Hardware. He enjoys covering the full breadth of PC tech; from business and semiconductor design to products approaching the edge of reason.

  • zecoeco
    Unsurprising consequence when overclocking.
    Just don't overclock and you're safe (hopefully).
    Reply
  • edzieba
    zecoeco said:
    Unsurprising consequence when overclocking.
    Just don't overclock and you're safe (hopefully).
    There's a big difference between
    "Intentionally overclocking and overvolting a CPU with a user-selected voltage above a certain threshold may damage your CPU"
    and
    "Enabling the DIMM-manufacturer-provided timings via the CPU-manufacturer-provided tool (EXPO) may silently set CPU voltage above a dangerous threshold without user intervention or knowledge"

    Particularly as consumers have been used to a decade and a half of enabling an analogous feature (XMP) without the same CPU overvoltage risk.
    Reply
  • bourgeoisdude
    Asrock? They released some beta bios updates yesterday for this,
    Reply
  • hotaru251
    if it was just SOC I have a feeling AMD wouldn't of been so "we accept the fault" as EXPO/XMP is seen as OCing and void warranties.
    I am type who always checks what setting is applied to pre-set stuff (as i know sometimes companies are way to generous on voltage or not generous enough)
    Usually i'll see the EXPO/XMP settings, copy em down, manually tune em to that and lower voltage if its over what I think is needed.
    Reply
  • Brian D Smith
    They only ever refer to the new "3D" chips...
    Reply
  • RedBear87
    zecoeco said:
    Unsurprising consequence when overclocking.
    Just don't overclock and you're safe (hopefully).
    It is fairly surprising when using one click solutions, normally they. I don't remember seeing CPUs literally exploding because of XMP. At worst I've read about people seeing faster than usual degradation because of PBO, but that's not really the same thing. Either AMD or its partners didn't do their homework well enough if they allowed something similar to happen.
    Reply
  • AdamB15
    ALL of Biostar's available BIOS files are from 4/13...So either they foresaw this and already limited the voltages, they did it by accident/chance, or their statement is false and their fixed bios is still incoming, right?
    Imagine if they foresaw this issue lol
    Reply
  • laxman10100
    I guess ASRock hasn't been on the list of manufacturers to release a BIOS update addressing this issue because their boards didn't push the SoC_Voltage over 1.3V with EXPO enabled. In my experience with the Taichi Carrara, the EXPO settings only pushed SoC_Voltage to 1.3V. It does, however, push the Memory_Controller_Voltage to 1.35V or 1.4V with an EXPO profile enabled...

    I wonder if this could cause the same problem - as AMD didn't state that the MC_Voltage being over 1.3V would cause this issue.... They just stated that the SoC_Voltage being over 1.3V would cause this issue...
    Reply
  • TerryLaze
    AdamB15 said:
    ALL of Biostar's available BIOS files are from 4/13...So either they foresaw this and already limited the voltages, they did it by accident/chance, or their statement is false and their fixed bios is still incoming, right?
    Imagine if they foresaw this issue lol
    The video of derbauer frying a x3d chip in asia is from 3/19 so the industry knows that there is something going on at least since then but realistically they should know stuff well before we find out.
    Maybe they thought that it would be much rarer or something.
    FVkTGq7brP4:1374View: https://youtu.be/FVkTGq7brP4?t=1374
    Reply
  • TerryLaze
    laxman10100 said:
    I wonder if this could cause the same problem - as AMD didn't state that the MC_Voltage being over 1.3V would cause this issue.... They just stated that the SoC_Voltage being over 1.3V would cause this issue...
    Isn't the SOC_Voltage the "all including" voltage and the mem controller a part of the soc?
    Reply