GPU Stuck at Motherboard Logo / POST Screen? BIOS Initialisation, GOP, CSM & Hardware Self-Test Troubleshooting

2026-10-21 ｜ GPU Repair ｜ 12 ｜ HK GPU Fix Editorial

Key Takeaways

A PC frozen at the motherboard logo is stuck in BIOS hardware initialisation, not a dead GPU. Debug LEDs name the failed stage — and a lit BOOT LED means a drive or boot-order problem, never the card. Old GPUs without GOP firmware need CSM; GTX 700/900/10-series DP 1.3/1.4 boot black screens are fixed by NVIDIA's UEFI firmware update tool.

Where the Boot Actually Stops

When a PC powers on, the motherboard BIOS/UEFI runs POST (Power-On Self-Test) in a fixed order: CPU initialisation first, then RAM detection, then graphics card initialisation, then storage devices, and finally the handover to the bootloader. A machine frozen on the motherboard logo is usually stuck at — or just after — the graphics initialisation stage.

Modern motherboards make this visible instead of guessable. ASUS Q-LED and MSI EZ Debug LED provide four LEDs that light in sequence — CPU → DRAM → VGA → BOOT — and whichever one stays lit is the stage where the process stopped. That is your first-hand positioning tool:

The last row is the single most important fact of this article: a lit BOOT LED means the graphics initialisation already succeeded and the board simply cannot find something to boot from. It has nothing to do with the GPU. Likewise, a lit DRAM LED is a RAM problem — no matter how much the symptom looks like a graphics fault.

Option ROM vs GOP: Why Old Cards Black-Screen on Pure UEFI

Legacy BIOS initialised the display through the graphics card's VBIOS legacy Option ROM (INT 10h). UEFI instead uses the GOP (Graphics Output Protocol) driver embedded in the card's firmware. An old card whose vBIOS contains no GOP driver has a predictable symptom on a board set to pure UEFI (CSM off): black screen or freeze. Some motherboards state the problem outright with the error "There is no GOP (Graphics Output Protocol) support detected in this card" and force a return to CSM — as happened to a Quadro 6000 owner in a Tom's Hardware thread.

The fix is to enable CSM (Compatibility Support Module) in the BIOS, which makes the board initialise the old card the legacy way and restores the display.

There is a trap for newer platforms: Intel 500-series and newer chipsets with current-generation CPUs do not support CSM at all — the option is greyed out or absent, because Intel removed VBIOS display support. On these boards, an old card without GOP has no legacy path to fall back on (ASUS officially recommends GTX 1000 / RX 5000 class cards and newer, which carry GOP support). If you are planning a pairing, this compatibility check comes before any purchase.

CSM vs Secure Boot

Secure Boot requires pure UEFI, which means CSM must be off — but an old card without GOP blacks out the moment Secure Boot goes on. This is the standard mechanism behind every "black screen after enabling Secure Boot" case. The recovery path: power off, clear CMOS (jumper, button, or remove the battery for a few minutes) to reset the settings, and if you have integrated graphics, connect the monitor to the motherboard output so you can get into the BIOS and reconfigure. A Tom's Hardware thread documents exactly this flow — removing the discrete card and using the iGPU to get back into the BIOS and disable Secure Boot.

NVIDIA's UEFI Firmware Update Tool (DisplayPort 1.3/1.4 Boot Black Screens)

There is a class of boot black screen with a very specific signature: a GeForce 700, 900 or 10-series card connected to a DisplayPort 1.3 or 1.4 monitor shows nothing until the OS loads — or hangs at boot — while the system is otherwise fine. NVIDIA ships an official tool for exactly this: the NVIDIA UEFI Firmware Update Tool (v1.1, released 2023-06-26). It updates the UEFI GOP portion of the card's firmware — not the whole VBIOS; GPU-Z shows no change afterwards, because only the GOP block is touched. Interrupt the update and you can damage the card, so follow the instructions and do not power off mid-flash.

Supported products: GeForce 700 series (GTX 745/750/750 Ti and other Kepler/Maxwell parts), the entire 900 series, the entire 10 series including the GT 1030, TITAN X (Maxwell/Pascal) and TITAN XP; Maxwell/Pascal Quadro cards may be affected — ask the OEM.

NVIDIA's own workarounds for running the tool while the screen is black, in order: boot with DVI or HDMI instead of DisplayPort → try a different monitor → toggle UEFI/Legacy in the BIOS → boot with integrated graphics or a second card, get into the OS, then run the tool. Real-world corroboration: an MSI forum thread documents a B450 board with a GTX 1050 Ti and a permanently lit VGA LED, where the suggested fix — move the card to another machine and run this tool — found the firmware genuinely needed updating. MSI's own black-screen troubleshooting guide lists the tool as a check item for older NVIDIA cards (e.g. GTX 970/1060) and adds practical tricks: move the card to a slower PCIe slot, switch the DP monitor to DP 1.2 mode, or use HDMI to get into the BIOS first.

Boundary Case: New Card in an Old Motherboard

The mirror image of the GOP problem is the new card that will not boot past BIOS in an old board. The usual cause is a motherboard BIOS too old to recognise the card. The fixes, in order:

1. Boot with integrated graphics or an old card and update the motherboard BIOS to the latest release.
2. Try forcing the PCIe slot to Gen3 (and test Gen4) in the BIOS.
3. Reset the BIOS to defaults if settings are suspected.

One caution that must not become a myth of its own: BIOS updates carry risk, so follow the board manufacturer's procedure exactly. Boards with Q-Flash Plus or BIOS Flashback can update without a CPU and without entering the BIOS, which makes the process considerably safer.

Telling Graphics Initialisation Failure Apart From Board/CPU/RAM Faults

Read the lights and listen first — never guess:

• A lit VGA / VGA Q-LED means the board finished the early stages but could not initialise the display subsystem (ASUS ROG forum; ASUS FAQ 1042678; MSI EZ Debug documentation).
• Beep codes require the motherboard speaker, and the codes differ by BIOS vendor — you must check your own board's manual, never memorise a generic table. As reference points: Award/Phoenix BIOS "1 long, 2 short" signals a display card error, while AMI BIOS uses "8 short" or "1 long, 8 short" for display memory/card errors. Reading the wrong vendor's table sends you fixing the wrong part.

Minimal-system elimination: strip the machine to CPU, one RAM stick in the manual's preferred slot, and the graphics card, then add components back one at a time. Pull the discrete card and switch to integrated graphics — if the display appears, the fault is in the discrete card or its initialisation path (a Tom's Hardware thread documents this exact procedure: remove GPU, reset CMOS, use iGPU, single RAM stick in A2).

Slot swap: move the card to a different PCIe x16 slot to rule out the slot and the CPU's PCIe lanes; cross-test with another card or another PCIe device if available.

Two traps to avoid:

• A Ryzen non-G processor has no integrated graphics. Pulling the card will *always* light the VGA LED — that does not mean the board is broken (MSI forum confirms: a 5600X without iGPU lights VGA by definition).
• Check where the monitor cable is plugged in. With a discrete GPU installed, a cable plugged into the motherboard's integrated output gives a black screen. That is a cable in the wrong socket, not a fault.

Common Myths

• "Stuck at the logo means the graphics card is dead." A lit BOOT LED is a drive/boot-order problem; a lit DRAM LED is a RAM problem. Read the LEDs before pronouncing the card dead.
• "A new card that won't light up is a dead card." Check the motherboard BIOS version, the CSM setting and the DP GOP firmware first — all three are fixes that need no replacement card.
• "BIOS updates are too dangerous to touch." When an old board meets a new card, a manufacturer-procedure BIOS update is the standard fix, and Flashback-class features make it low-risk.
• "DisplayPort black screen means the card is broken." On affected cards, the GOP firmware issue with DP 1.3/1.4 usually disappears over HDMI or DVI — change the cable and port before drawing conclusions.
• Memorising a universal beep-code table. AMI, Award and Phoenix define the same sounds differently; the only valid table is the one in your motherboard's manual.

FAQ

My PC freezes on the motherboard logo — is the graphics card broken?

Not necessarily. The freeze marks where POST stopped, and the debug LEDs identify the stage: CPU, DRAM, VGA or BOOT. Only a lit VGA LED points at display initialisation. A lit BOOT LED means the graphics already initialised and the board cannot find a boot device — a storage or boot-order issue, not the GPU.

Why does an old graphics card black-screen on a new motherboard?

The card's vBIOS likely lacks a GOP (Graphics Output Protocol) driver, which pure-UEFI boards require. Enabling CSM in the BIOS restores the legacy initialisation path. But on Intel 500-series and newer platforms CSM no longer exists, so such a card has no supported path on those boards — the pairing itself is incompatible.

I enabled Secure Boot and now the screen is black. What happened?

Secure Boot forces pure UEFI (CSM off). If your GPU has no GOP firmware, display initialisation fails at POST. Clear CMOS to reset the settings, then use integrated graphics or a different card to get into the BIOS and disable Secure Boot before re-enabling the discrete card.

My GTX 1060 shows nothing on a DisplayPort monitor until Windows loads. Is the card dying?

Probably not — this matches the documented DP 1.3/1.4 GOP firmware issue affecting GeForce 700, 900 and 10-series cards. Run NVIDIA's UEFI Firmware Update Tool (v1.1): boot over HDMI/DVI or integrated graphics first, then apply the update in the OS. The tool only updates the GOP block, and GPU-Z will show no change — that is expected.

Which beep code means a graphics card problem?

It depends on your BIOS vendor. Award/Phoenix: 1 long, 2 short is a display card error. AMI: 8 short (or 1 long, 8 short) is a display memory/card error. Do not trust a generic table — verify against your motherboard's manual, because the vendors assign the same sounds different meanings.

The VGA LED stays on even though the card worked in another PC. What next?

Try the card in a different PCIe x16 slot, update the motherboard BIOS, force the slot to Gen3, and clear CMOS. If the board has no integrated graphics path and the card works elsewhere, the fault is in this board's slot, lanes, settings or firmware — not necessarily the card.

When should I bring the card or system in for professional diagnosis?

When the minimal-system procedure, CMOS reset, slot swap, BIOS update, CSM configuration and the GOP firmware tool have all failed to move the symptom — or when the debug LEDs point at the VGA stage but reseating and cross-testing cannot distinguish the card from the slot. HK GPU Fix (Room 1209, Dali Plaza, Shek Mun; phone 2186 8010; WhatsApp 6558 6806) handles POST-stage diagnosis with published three-tier pricing (HK$400–2,800).

Sources

• The Computer Basics — motherboard debug LEDs: https://thecomputerbasics.com/motherboard-led-lit-but-computer-not-starting/
• ASUS FAQ 1042678 — Q-LED troubleshooting: https://www.asus.com/us/support/faq/1042678/
• ASUS ROG Forum — VGA LED meaning: https://rog-forum.asus.com/rss/message?board.id=MountMB&message.id=1
• MSI EZ Debug LED — VGA-LED documentation: https://manuals.plus/m/cec211f2220938b20b66971c23e6774ed623f275c8d2ea0f5799ee0d2
• Tom's Hardware — old card without GOP forced to CSM: https://forums.tomshardware.com/threads/can%E2%80%99t-enable-uefi.3745925/
• OneSDR — VGA card not supported by UEFI driver: https://www.onesdr.com/vga-card-not-supported-by-uefi-driver/
• ASUS FAQ 1045467 — Intel 500-series CSM unsupported: https://www.asus.com/ch-en/support/faq/1045467
• Position Is Everything — Secure Boot black screen mechanism: https://www.positioniseverything.net/solved-no-display-after-enabling-secure-boot/
• Tom's Hardware — Secure Boot black screen, iGPU recovery: https://forums.tomshardware.com/threads/black-screen-after-enabling-secure-boot.3756256/
• Tom's Hardware — CMOS hard reset procedure: https://forums.tomshardware.com/threads/i-need-to-turn-on-secure-boot-but-when-i-turn-off-csm-my-screen-goes-black.3893277/
• NVIDIA — UEFI Firmware Update Tool: https://www.nvidia.com/en-us/drivers/nv-uefi-update-x64/
• Hexus — tool updates GOP only: https://hexus.net/tech/news/graphics/119090-nvidia-firmware-update-supports-g-sync-hdr-monitors/
• MSI Forum — B450 + 1050 Ti VGA LED case: https://forum-en.msi.com/index.php?threads/pc-not-booting-with-vga-light-staying-on.392681/
• MSI Forum — black screen troubleshooting guide: https://forum-en.msi.com/index.php?threads%2Fguide-troubleshooting-a-black-screen-at-startup-cannot-access-msi-bios-menus.408824
• GuidingTech — new GPU won't boot: https://www.guidingtech.com/what-to-do-if-windows-wont-boot-with-a-new-gpu/
• The Filibuster Blog — old BIOS not recognising new GPU: https://howto.thefilibusterblog.com/how-to-troubleshoot-windows-boot-issues-after-installing-a-new-gpu/
• DOS Days — AMI/Award/Phoenix beep code reference: https://www.dosdays.co.uk/topics/pc_bios.php
• Ibertronica — beep code meanings: https://ibertronica.es/blog/en/news-en/bios-beep-solution-what-does-it-mean-and-how-to-resolve-it/
• Tom's Hardware — VGA LED minimal-system procedure: https://forums.tomshardware.com/threads/vga-led-on-and-pc-wont-boot.3240097/
• EveTech — discrete GPU boot issues, slot swap: https://evezone.evetech.co.za/build-lab/discrete-gpu-boot-issues

> Related reading: if the card shows nothing at all (not even the motherboard logo), the cause may be a legacy card without UEFI GOP on a UEFI-only board — see Old GPU, New Motherboard, No Display? UEFI GOP, Legacy Compatibility & CSM Explained.