Just got a completely brand new device and can't make it past the initial AMI startup screen.
Just got a completely brand new device and can't make it past the initial AMI startup screen.
Recent motherboard updates triggered error code 64, causing the system to hang on the AMI boot screen with no BIOS access. CPU temperature settled at a stable 32°C, but it couldn't progress beyond the BIOS prompt. The motherboard’s status indicates "CPU DXE initialization started," yet the process stalls. Despite a clean 00 error code display, a solid red LED blinks persistently. Pressing DEL or F12 yields no response, suggesting a faulty keyboard. Two USB keyboards tested on another machine also failed to function. CPU heat is rising (31°C), and overall system performance appears suboptimal. All components seem physically intact, but functionality remains elusive.
You're experiencing a delay before the system powers up. DDR5 setups may need some time to initialize, which can cause noticeable lag during the initial boot phase. Temperatures around 31°C are normal and indicate the processor is receiving power.
I notice the display shows detailed information about the system setup. The keyboard connections appear to be using older ports, specifically USB2. When a USB drive with Windows installed is connected, the system adjusts the boot sequence without requiring any manual BIOS changes.
I waited roughly a second after the AMI boot screen appeared before giving up. Pressing DEL didn’t take me into BIOS. Might it really mean I didn’t wait long enough? Could there be a better time to press DEL? (The AIO fans are spinning but their lights aren’t turning on. I thought that wasn’t important for diagnosis, but I shouldn’t be guessing at this level.)
I tested my keyboards with every USB port available—anything connected straight to the motherboard, no hubs, and not using my case’s USB. Nothing changed. I’m not planning to use that Windows stick until I verify the build is stable, so it’s currently unplugged.
Does this keyboard manage "del" correctly on another machine? It might be a faulty key triggering the issue.