Gygabyte ultra Z390 boot loop issue Troubleshoot and resolve startup problems
Gygabyte ultra Z390 boot loop issue Troubleshoot and resolve startup problems
I mounted a 9900k on the GYGABYTE Z390 ultra board. The BIOS menu showed the keyboard wouldn't respond. I changed the keyboard and left the HDMI plug in, but it still didn't work. I reset the CMOS and tried booting with just one RAM stick, but nothing happened. I left it on while away and when I returned, the BIOS loaded properly. After an update, it functioned correctly. Updated November 10, 2018 by lmmersion
Are you noticing the CPU getting warm or even hot? Look closely at the connections near the CPU block. Have you checked each RAM stick individually in every slot? Did you test without a GPU attached? Is your BIOS up to date, possibly needing an older CPU model with a BIOS upgrade before installing the new one? If none of these steps help, inspect the motherboard for bent pins—removing the cooler and CPU can be quite challenging.
Consider giving the CPU another try, especially after some time away—it finally seated properly. The cooler or CPU block might not have been fastened correctly, possibly too loose, too tight, or a pad could be causing issues. A BIOS update could also help, as the 9900k is newer than the Gigabyte Z390 board. Although it works with the chipset, the board may need a BIOS upgrade for full stability, similar to what I did with my 870A using an older Athlon II x2 setup.
Sure, the initial setup will likely require more time than expected.
Feedback remains valuable even without a brand-new clean board. Product stays available on Amazon. A boot loop problem occurred—similar situation... Updated mainboard (Aorus Master z390) transferred the graphics card and power supply to an older model. Restarted after installing into the (Aorus Z390 Gamer X). Cleaned up to the essentials (Aorus Z390 Gamer X), which meant taking out the CPU cooler. It turned out a memory module wasn’t properly seated; during cable setup I accidentally hit the clip, loosening the DDR4 Channel 1. Realigning that clip resolved the issue.