I GOT Q CODE 99 BECAUSE MY MOUSE AND KEYBOARD WERE NOT PLUGGED INTO THE USB ON THE MOTHERBOARD, WHICH CAUSED NO DISPLAY AND NOT TO PASS POST
Hello and thank you very much for your post. I have had the same issue from building a brand new system, after building many more over the years. I have pulled my hair out for 2 whole days. I eventually found your post and hey presto, I changed my wireless mouse to a cable mouse and board and tada, we have lift-off. ASUS, you suxxxxx
This Post is originally from 2016
Its now 2023 and i bought an ASUS motherboard for almost 600€ and this exact same issue is still present.
ASUS i will never ever purchase anything from you guys again. Shame on you
The Q-code is designed to tell you something isn't working or correctly configured. 99 can mean a device is either disconnected from the IO or isn't functioning correctly. This can include (but is not exclusive to) USB peripherals, storage devices or lack of signal input from the display or GPU. Trying to troubleshoot a system without a Q-Code LED is far more time-consuming.
I had somewhat of a similar issue and your post helped me figure it out. At boot, I was briefly getting code 99 or 98 followed by 64, which it was then stuck at forever. My monitors were blank the whole time. It wasn't a new build, but I had just deleted some snap packages before restarting by accident without uninstalling them first (I'm on Ubuntu).
I fixed it by unplugging a USB hub that had a Yeti, Astros A40s, webcam, and an external hard drive plugged into it. As soon as I unplugged it the 64 code went away and I was able to boot.