This model alters my system's memory configurations.
This model alters my system's memory configurations.
Hi, I recently replaced some RAM in my system, moving from 4 x 4 GB Crucial Ballistix Sport at 2666 MHz to 4 x 16 GB G.Skill TridentZ RGB at 3200 MHz. The rest of the hardware includes a Threadripper 1900X at base speeds and an RTX 2080 graphics card. At first, everything functioned perfectly, regardless of whether I used default BIOS speeds or selected XMP profile 1. After installing the new RAM, it automatically recognized the updated XMP settings and operated at 3200 MHz with recommended timings (CL16-18-18-38 @ 1.35V). So far, everything seems normal. I tried reverting to default speeds just to see what would happen, but the system kept restarting three times before resetting the memory back to 2100 MHz, which felt like an overclock attempt. I then switched back to XMP profile 1, rebooted, and it worked again. However, when I manually entered all the timings instead of letting the BIOS auto-adjust, the system failed repeatedly. I reset the BIOS and reconfigured the profile, but nothing changed. I even tried reseating the RAM, which didn’t help. It booted normally at default settings. The issue is that it runs slower than my old RAM, which isn’t ideal. I upgraded the BIOS from F11e to F12e because I suspected compatibility problems with the older version. Same outcome. Eventually, I swapped back to the original RAM, restored all settings, and everything functioned as expected. Then I switched back to the new RAM, and it immediately ran at XMP profile 1 as intended. The system booted into OS, stayed at 3200 MHz, rebooted, and worked fine. When I cut power and reconnected, it still operated correctly. In UEFI settings, I couldn’t modify anything, so I saved the changes. Still, it failed again when I changed the BIOS back. To restore XMP profile 1, I had to revert everything to its original state. This has led me to suspect a problem with the BIOS itself—specifically, that it corrupts memory settings upon saving. It’s possible a bug exists in the AORUS BIOS. What do you think?