Error code A2/ B4/ C9 along with a 130-second boot time.
Error code A2/ B4/ C9 along with a 130-second boot time.
I recently upgraded to the 5th Gen model, which includes a CPU/MOBO/RAM setup and a 990 EVO. Everything has worked well so far during intensive gaming sessions and stress tests. Initially, I encountered several error codes such as 64 and C9, but now I consistently see an A2 code (which detects and installs all connected IDE devices). Restarting my computer triggers the A2 code; a full shutdown brings up the 64 code (related to CPU DXE installation). I’m uncertain whether these codes affect performance or if they’re just causing freezing during boot. This issue occurred after an A0, with all codes resulting in a boot time of about 120-130 seconds.
I’ve tried reseating the RAM, using ultra-fast boot settings, and clearing CMOS. These changes cleared other errors but didn’t resolve this one. The problem appears to manifest immediately after posting, as the hotkeys on the screen display the "Aorous" screen, freeze for around 120 seconds with the MOBO code, then proceed normally. I haven’t found a solution on any forums, so I’m relying on this as my best approach. It’s worth noting that all drivers are up to date, Windows is current, and the latest Windows version with Expo 1 profile enabled is in use. The memory is correctly placed per the configuration guide for A2/B2, and boot priorities are limited to the Windows drive.
Hardware specs:
- CPU: AMD 7950x 3D
- GPU: 7900 XTX Nitro+
- PSU: Corsair RXe 1KW
- Motherboard: GIGABYTE X670E AORUS Master
- RAM: CORSAIR VENGEANCE RGB DDR5 64GB (2x32GB) at 6000MHz CL30
- Case: Corsair 7000D Airflow
- Cooling: Water-cooled CPU/GPU block, dual radiators + four 140mm fans, eight 120mm fans, two Corsair hubs
- SSD: SAMSUNG 990 EVO PRO 4TB, 970 EVO PRO 2TB, Samsung 870 Pro 500GB
Did you reinstall Windows after installing your drive on the new motherboard?
Yes, I cleaned all my drives completely. Various fixes I attempted didn't help much—rearranging RAM, using just one stick, booting from individual drives, unplugging others, checking drive health, turning off integrated graphics, switching GPU settings, resetting CMOS, and disabling post-graphics none improved things at all. It seems the issue might be with the motherboard itself, especially given the recurring A2 error code or the B4 error before posting for 130-137 seconds.