Can You Check GPU In BIOS? | Before Drivers Load

When a PC won’t boot cleanly, or a new graphics card stays dark, you want answers before drivers load. The firmware screen is the one place you can confirm what the motherboard detects and which display output it plans to use.

Below you’ll learn what firmware can tell you, where to look in common menus, and what to try when the card doesn’t appear. Then you’ll see quick OS checks that confirm the exact model and driver state.

What the BIOS can show about your graphics adapter

Most modern PCs use UEFI firmware, though people still call it “BIOS.” The menu handles early hardware detection and picking an initial display device. That’s why it often exposes at least one of these GPU clues:

• Primary display selection (PCIe/PEG, iGPU/IGD, Auto).
• PCIe slot status such as link speed or lane width.
• Device list entries that reference a “VGA” device, “display controller,” or a vendor string.
• Integrated graphics toggles on CPUs with built-in graphics.
• Resizable BAR / Above 4G decoding options that can affect detection on newer GPUs.

What you usually won’t get is a full spec readout with memory size and clocks. Firmware data is meant for boot and routing, not shopping comparisons.

Can You Check GPU In BIOS? When it works and when it doesn’t

If your board sees the card and the card can initialize enough to present a signal, the firmware screen will often confirm that a discrete GPU exists. If the card is not seated, not powered, or the slot is disabled, the system may fall back to integrated graphics and act like the discrete card isn’t there.

There’s also a middle case: the GPU is detected on the PCIe bus, yet you get no image from the card’s ports during boot. This can happen with a loose power lead, a finicky DisplayPort handshake, a monitor on the wrong input, or a firmware setting that still points “initial display” to the motherboard port.

How to find GPU details in common UEFI menus

Vendors name the same idea in different ways. Hunt for terms tied to the PCI Express slot and display priority. Start with “Advanced” mode if the interface has an EZ view.

Look for the primary display setting

Common labels include Primary Display, Initiate Graphic Adapter, Initial Display Output, or PEG/PCI. If you want the discrete card to light up first, pick the option that points to the PCIe graphics slot (often “PEG” or “PCIe”). Save, reboot, then check if the monitor now shows the card’s output.

Check PCIe slot status pages

Many boards show a per-slot readout like PCIe x16_1: x16 @ Gen4. Even if the firmware doesn’t print a GPU name, this line can tell you the slot is active and negotiating lanes. A “Not Present” or “Empty” status is a strong hint the board is not seeing the card.

Scan device lists for a display controller

Some UEFI screens have a system inventory table under sections like System Information or Onboard Devices. You might see entries that reference “VGA,” “Display,” or a PCI device ID. It’s not pretty, yet it can confirm the card is on the bus.

Integrated graphics controls on iGPU CPUs

If your CPU has integrated graphics, firmware often offers an iGPU enable/disable option and a multi-display toggle. Leaving iGPU enabled can be handy during troubleshooting, since you can still get video output while you sort out the discrete card. If you disable the iGPU and the discrete card still fails, you may end up with a black screen until you reset firmware settings.

Why firmware info can look off even when the GPU is fine

Firmware screens can be blunt. A few situations make the readout confusing:

• Auto mode picks the motherboard port if the card doesn’t initialize quickly.
• CSM versus UEFI settings can change how early video initializes on some older GPUs.
• Multiple GPUs can swap “primary” status after you move monitor cables.
• Firmware updates can tweak PCIe training and device naming.

If the label is vague, confirm the exact GPU model once the OS is running. That’s where you’ll see the full name and driver details.

Fast checks in Windows and Linux after boot

These checks don’t replace firmware troubleshooting. They answer “What GPU is installed?” and “Is the driver active?” in minutes.

Windows: DxDiag for a quick identity check

Windows includes DxDiag, which lists the display device name and driver info. Microsoft shows how to run it and where to read the results on the page about which version of DirectX is on your PC.

Linux: nvidia-smi when you’re on NVIDIA

On Linux with NVIDIA drivers installed, nvidia-smi can show the GPU name, driver version, and utilization. NVIDIA describes the tool and its output in the nvidia-smi documentation.

If you’re on AMD, tools like lspci still show a clean vendor and model string, even without a vendor CLI.

Table: What you can verify at each stage

Use this as a quick “where to look” map when you’re trying to separate a firmware issue from a driver issue.

Checkpoint	What it tells you	What it can’t prove
Primary display setting (PCIe/PEG vs iGPU)	Which device should show the boot screen	Exact GPU model and VRAM size
PCIe slot status (Gen, lanes, “present”)	Whether the board detects a device in the slot	That the card can drive a monitor
Firmware device list (VGA/display controller)	Proof that a display device is enumerated	Driver readiness inside the OS
Windows Device Manager	Device name plus driver state	Whether the card is stable under load
DxDiag Display tab	Adapter name, driver version, feature levels	PCIe lane negotiation details
Linux lspci	Vendor and device IDs on the PCI bus	Clock behavior and temps
nvidia-smi (NVIDIA)	Driver, GPU name, temps, power, processes	Firmware boot display routing
Game or benchmark load	Real stability and performance behavior	That firmware settings are sane

Steps to take when the GPU doesn’t show in BIOS

If the firmware menu looks like the discrete card doesn’t exist, work from the physical layer up. Each step tries to rule out one class of failure without changing five things at once.

Step 1: Reseat the card and re-check PCIe power

Power off, switch the PSU off, then press the power button once to drain residual power. Reseat the card until the retention clip clicks. Then verify every PCIe power plug is fully latched. A half-seated 8-pin can spin fans yet fail during device initialization.

Step 2: Move the display cable to the GPU

If your monitor is plugged into the motherboard, you might be staring at the iGPU while the discrete card sits idle. Plug HDMI or DisplayPort into the card itself, then reboot.

Step 3: Force the initial display to PCIe/PEG

Set the primary display option to the PCIe graphics slot, save, and restart. If you don’t see the firmware screen after this change, wait a full minute, then power down and reset CMOS to return to defaults.

Step 4: Swap slots, cable, and monitor input

Second x16-length slots often run fewer lanes, yet they’re fine for testing detection. Swapping cables and changing monitor input can also fix a boot screen that never appears on DisplayPort until the OS loads.

Step 5: Trim to a minimal boot

Run one RAM stick, one storage device, and the GPU. Remove extra PCIe cards and unneeded USB devices. This can expose a power or stability issue that only shows up with a crowded setup.

Step 6: Update firmware after the basics are solid

Board firmware updates can improve PCIe compatibility, especially with newer GPUs. Use the vendor’s built-in flash utility and follow the board manual. Avoid updating during storms or on a flaky power strip.

When firmware sees the GPU but Windows shows “Microsoft Basic Display Adapter”

This mismatch usually means the card is detected, yet the vendor driver isn’t installed or isn’t loading. You may also see this after swapping GPUs without cleaning old drivers.

Start with a clean driver install from the GPU vendor, then reboot. If the driver still won’t load, check power cables again and check for error codes in Device Manager. A Code 43 on NVIDIA often points to driver trouble or hardware faults.

Table: BIOS settings that commonly affect GPU detection

These options sit in different places on different boards, yet they’re the usual suspects when detection feels flaky.

Setting name you might see	Typical choices	What to try
Primary display / initiate adapter	Auto, iGPU/IGD, PCIe/PEG	Pick PCIe/PEG when using a discrete card
iGPU multi-monitor	Enabled, Disabled	Disable if you want only the discrete card active
CSM	Enabled, Disabled	Disable CSM for a clean UEFI boot with modern GPUs
Above 4G decoding	Enabled, Disabled	Enable when using large BAR features or many PCIe devices
Resizable BAR	Auto, Enabled, Disabled	Try Auto first, then toggle if games or boot act odd
PCIe link speed	Auto, Gen3, Gen4, Gen5	Force a lower Gen if training fails on Auto
Secure Boot	Enabled, Disabled	Leave enabled on modern systems unless troubleshooting older OS installs

A quick final check before you close the case

Once you get a stable boot screen from the GPU ports, do one more pass:

• Firmware shows the PCIe slot as present and negotiating lanes.
• Windows or Linux lists the GPU name and loads the vendor driver.
• Under load, temps stay in the vendor’s normal range and you don’t get random black screens.

At that point, the firmware screen has done its job. It confirmed the motherboard and GPU can see each other before the OS takes over.