During testing of some of Nvidia's new GTX 650 and GTX 660 graphics cards, we ran into an interesting issue. The computer would turn on, show the BIOS splash screen but won't enter the BIOS and any other keyboard shortcut functions like "Del" or "F8" are seemingly ignored. A single POST beep would be heard, and it would repeat every 5 seconds or so. Sometimes, if you left it, it would eventually boot Windows, but the adapter wouldn't be recognized in Windows 7 64-bit when it would boot, but would show as a "VGA Display Adapter" instead of "Nvidia GTX 650 Ti" or its respective model number regardless if the appropriate driver was installed or not. Other times, after the repeated POST beeps, a blank screen would be seen with LED debug Code A9.
CPU: Intel i5-3570K
CPU Cooling: Cooler Master TPC 812
PSU: Cooler Master SPH 1050W
Motherboard: Gigabyte Z77X-UD3H
and Nvidia GeForce GTX 650 Ti
OS HDD: OCZ Agility 3 120GB SSD
Secondary HDD: Kingston HyperX 3K 240GB SSD
OS: Windows 7 Professional 64-Bit
Since these are brand new cards and the board we were testing on was running an old BIOS version, we thought that'd fix the problem (and it did). So you've got two options if you're running into this debug code with your new build:
- If you've got a spare graphics card, toss that in so you can boot into the BIOS. If you can enter the BIOS, download the latest BIOS version from Gigabyte's Z77X-UD3H product page and transfer it to a USB flash drive.
- If you don't have a spare graphics card, you're in luck, because the Z77X-UD3H enables use of the integrated graphics adapter of the Ivy Bridge processor. Remove your new graphic's card and plug your monitor into the DVI port on the I/O panel of your motherboard, and grab the BIOS as described in Step 1.
- Enter the BIOS and use EZ Flash 2 to ugrade your BIOS to the latest version. I'd recommend POSTing/booting once after the upgrade.
- Reinstall your new GTX 650 or GTX 660 series GPU, and enjoy!
We found a similar issue posted on Tom's Hardware, so this indicates it won't be an isolated issue once Nvidia's new GPUs become more popular. If you had a different solution to the same error code, let us know in the comments below!