• 1 Post
  • 33 Comments
Joined 1 year ago
cake
Cake day: July 17th, 2023

help-circle





  • The only thing I can think of is to try the drives in a different system and see how they behave (same OS and configuration).

    If they behave the same then that rules out everything except the drives themselves and the OS.

    Considering how you mentioned the behavior is better in Windows, it sounds like a software issue, but you never know until you try.


  • FWIW I’ve also had memory issues with XMP.

    Turns out that ASUS firmware is omega pepega and decided to go against AMD’s specifications even for XMP profiles.

    CLDO VDDP was stuck at the same voltage as SOC. Per AMD it has to be up to VSOC - 0.1V

    So, after manually setting that, and other VDDP and VDDG voltages, it magically started working perfectly.

    So do check voltages anyway even if you found a bad stick. Mine endured through the crappy firmware thanks to it being Samsung B-die.

    Also check this for more info in general (I recommend this even if you won’t OC, just the memtest alone is a huge section)

    https://github.com/integralfx/MemTestHelper/blob/oc-guide/DDR4 OC Guide.md

    I tested with OCCT to find even more errors, so either do that in a mini windows environment or do one of the Linux tests to check memory some more. Memtest86+ isn’t enough.














  • It needs to be accurate and fast, indeed. The code being old isn’t a problem unto itself, but rather the side effects of it.

    It is fine for all intents and purposes today. But, there is some inherent difficulty associated with decisions brought years ago when some of the code was originally written, making portability quite a challenge.

    I wasn’t making a comment on its age, mind you. I don’t necessarily think it’s that big of a problem and probably can be fixed easily. If anything, it has gotten way better thanks to the departure from the plugin system and various other optimizations over the years.