• RedWeasel@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    4
    ·
    17 hours ago

    Could be a problem with the SSDs as well. AMD released the X670E last year after all. These aren’t new chipsets.

    • MonkderVierte@lemmy.ml
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      2 hours ago

      Caught you on reading the title only. Your charge is to read the linked article in the future, before replying.

      One of the affected users who is running an ASUS X670E motherboard with the Crucial T705 SSD got a response from Crucial’s support team which is provided below:

      We would like to inform you that we escalated your issue to our dedicated team for further investigation, and they informed us that the problem lies with the motherboard rather than the Crucial SSD. This behavior has been observed across various motherboards from different manufacturers, and we were able to replicate it on our in-house systems as well.

      The issue seems to occur when a Gen5 SSD is connected to a Gen5 slot on the motherboard, which is why you are not experiencing this problem with your Gen4 drive. If you were to connect the Crucial T705 SSD to Gen4 speeds at all times, this issue would likely be resolved.

      Unfortunately, the only fix for this issue is a BIOS update from the motherboard manufacturer. We recommend reaching out to your motherboard’s manufacturer to inquire about a potential BIOS update that addresses this specific problem. We have seen BIOS updates from multiple manufacturers that help resolve this kind of issue.

      Please note that the Crucial T705 SSD will perform at whatever speed the motherboard allows, and this is not a fault of the drive itself. We understand the inconvenience and will continue to support you, but at this point, it is necessary to work with the motherboard manufacturer to find a solution.

      Crucial Engineering Team

      • TexMexBazooka@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 hour ago

        Taknow that’a a pretty respectable response to get, I can really hear the frustration from the support guy “yeah man I don’t know it’s broken but it’s not our shit I’m sorry”