• frezik@midwest.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 months ago

    Not from AMD. From the autogenerated transcript (with minor edits where it messed up the names of things):

    amd’s official recommendation [f]or the cut off now is 1.3 volts but the board vendors can still technically set whatever they want so even though the [AGESA] update can lock down and start restricting the voltage the problem is Asus their 1.3 number manifests itself as something like 1.34 volts so it is still on the high side

    This was pretty much all on motherboard manufacturers, and ASUS was particularly bad (out scumbaging MSI, good job, guys).

    At the start of this Intel mess, it was thought they had a similar issue on their hands and motherboard manufactures just needed to get in line, but it ended up going a lot deeper.

    • mox@lemmy.sdf.orgOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      3 months ago

      That doesn’t contradict anything I wrote. Note that it says AMD’s recommended cutoff is now 1.3 volts, implying that it wasn’t before this mess began. Note also that the problem was worse on Asus boards because their components’ tolerance was a bit too loose for a target voltage this high, not because they used a voltage target beyond AMD’s specified cutoff. If the cutoff hadn’t been pushed so high for this generation in the first place, that same tolerance probably would have been okay.

      In any case, there’s no sense in bickering about it. Asus was not without blame (I was upset with them myself) but also not the only affected brand, so it’s not possible that they were the cause of the underlying problem, now is it?

      AMD and Intel have been pushing their CPUs to very high voltages and temperatures for small performance gains recently. 95°C as the new “normal” was unheard of just a few years ago. It’s no surprise that it led to damage in some cases, especially for early adopters. It’s a thin line to walk.