Changes in BIOS trigger a CMOS reset, but updating via Ryzen Master works just fine
Changes in BIOS trigger a CMOS reset, but updating via Ryzen Master works just fine
PC Specifications: Ryzen 7 3700X, RTX 2070 Super, 2x8GB G.Skill Trident Z Neo 3600, X570 I/O, Aorus Pro Wi-Fi (ITX), all systems functioning normally initially. Occasionally encountered boot failures after attempting to overclock RAM, resetting back to the default 2133 MHz speed. CMOS errors appeared, leading to suspicion of a battery issue. Recently replaced RAM and same problems persist. Testing revealed that saving BIOS settings still results in temporary boot attempts before reverting to defaults. Ryzen Master remains capable of overclocking. I managed to achieve stable speeds around 3800 MHz or higher with auto mode enabled, and BIOS confirms the changes were saved. I’m new to overclocking and haven’t used Gigabyte boards before—any advice would be appreciated!
right now, I can't perform any overclocking, underclocking, XMP settings, or leave everything unchanged in the BIOS. However, in Ryzen Master it's running at 3800 MHz at 1.35V (auto value) with some timing adjustments. The issue isn't with the OverClock setting itself, but rather with how changes are saved manually versus what Ryzen Master handles automatically.
Have you experimented with saving changes individually? Increasing the voltage, saving, rebooting, repeating the process—sometimes it works, other times it doesn’t. If that approach fails, updating your BIOS is a good next step (or downgrading if you're already up-to-date). Keep in mind that Gigabyte motherboards are known for poor memory support, making overclocking challenging. I recently removed my Gigabyte board because it lacked adequate memory support and the manufacturer didn’t offer fixes. It remained unstable above 2133MHz with all tested RAM modules.
Have you explored the latest BIOS version? They include AGESA updates that enhance RAM compatibility.
It seems the choices were BIOS updates or returning the product for repair. This approach has likely been used before, but this issue might be new. Clearly, certain configurations are persisting since the system can locate the boot drive without warning about changes to CPU or RAM after each startup.
You recently re-flashed the same BIOS from the identical download on the same USB drive, and it seems to function now. I’m doubtful about this since yesterday I briefly adjusted settings (similar to what’s happening now), before the issue occurred. It might be due to a minor error during the previous flash or some changes in settings that triggered this problem.