Announcement

Collapse
No announcement yet.

Asrock X670E Steel Legend memory issue with new bios

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Asrock X670E Steel Legend memory issue with new bios

    So I'm having boot issues when I update to the newest bios version 3.01, on a restart everything is fine, but on a cold boot each and every time it does memory training-double boot-memory training again. I have memory training on auto, so as to not perform training every time, it still does it. The strange thing is when I downgrade to the previous bios 2.10, everything is fine. I contacted Asrock, but they were unhelpful, and only said they didn't have my memory kit to test with and it wasn't on their QVL list. The memory I'm using is Flare X5 32gb F5-6000J3038F16GX2-FX5. The memory kit they tested with is F5-6000J3038F16GX2-TZ5N, and they have no issue with the mentioned 3.01 bios.

    So hopefully you guys can shed some light on this issue, thanks in advance.

  • #2
    It's probably not what you want to hear, but I'd probably just skip that version and give the next release another go.

    If the issue keeps persisting with all upcoming releases, maybe they are willing to look into it. Your kit and their test kit are very similar in terms of specification and should be fully interchangeable when it comes to compatibility (even the self certification reports on the product pages are practically identical).
    Team HardwareLUXX | Show off your G.SKILL products!

    Comment


    • #3
      Originally posted by emissary42 View Post
      It's probably not what you want to hear, but I'd probably just skip that version and give the next release another go.

      If the issue keeps persisting with all upcoming releases, maybe they are willing to look into it. Your kit and their test kit are very similar in terms of specification and should be fully interchangeable when it comes to compatibility (even the self certification reports on the product pages are practically identical).
      That's what i thought pretty much, but you just confirm that reasoning. I believe it's something to do with their bios or the AGESA code even, I'm hoping it's fixed it's fixed in the next update.

      Comment

      Working...
      X