PC Won’t Detect GPU | Fast Fix Guide

Troubleshooting / By

When Windows fails to see a discrete graphics card, check power, slot seating, BIOS, and drivers first.

Why Your PC Isn’t Detecting The Graphics Card

This guide shows a clean, tested path to restore detection with the least guesswork. You’ll start with fast checks, then move to firmware and driver fixes, and finish with hardware isolation steps. Each step lists what you should see and what to do next if the result isn’t right.

Fast Checks Before You Open Anything

  • Monitor on the right port: plug the display cable into the card’s output, not the motherboard’s port.
  • Firm power leads: seat the 6/8-pin PCIe connectors; for new ATX 3.0 cards, use the 12VHPWR cable that shipped with your PSU.
  • Full shut down: power off, flip the PSU switch, hold the case power button for 10 seconds, then boot.
  • Clear CMOS the simple way: unplug, short the CLR_CMOS pins or remove the battery for a minute, then restore. This resets odd firmware states that can hide devices.

Quick Fix Table

Symptom Likely Cause What To Try
No display when the card is installed Cable in the wrong port or loose power Move the cable to the card; reseat PCIe power leads; test a second cable/monitor.
Card fans spin but Windows lists only basic display adapter Driver or BIOS setting Install a fresh driver; disable iGPU auto-init, or set Primary Display to PCIe.
Random detection after restarts Fast Startup or power saving Turn off Fast Startup; disable hybrid sleep; use a full shutdown before testing.
Device Manager shows error 43/31 Broken or wrong driver Clean install the vendor driver; block Windows from swapping it mid-boot.
Card not visible in BIOS or Windows Poor seating or dead slot Reseat in the top x16 slot; test the second slot; inspect for debris or standoffs.

Set Windows Up For A Clean Driver Install

  1. Boot into Safe Mode with networking. This loads a minimal stack that avoids third-party tools grabbing the card mid-install.
  2. Uninstall old vendor packages. Remove GeForce Experience or AMD Software from Apps. Reboot.
  3. Clean up leftovers. Use Device Manager to remove display adapters with “Delete the driver software” checked where shown.
  4. Install fresh drivers you downloaded before the reboot. Pick the correct model and Windows version.

Get The Right Driver The First Time

  • NVIDIA users: grab the current WHQL or Studio release that matches your card series and Windows build from NVIDIA driver downloads.
  • AMD users: use the Auto-Detect tool or pick your exact GPU model and OS via AMD driver downloads.
  • Intel Arc users: download the latest package for your card and Windows build.

After install, restart and confirm the adapter model and driver date in Device Manager.

Check BIOS/UEFI Settings That Hide A Card

  • Primary display: set PEG/PCIe as first display. Some boards default to the integrated adapter.
  • CSM vs UEFI: stick with pure UEFI on modern cards. Mixed CSM can block option ROMs from initializing.
  • Resize BAR/Above 4G: leave it enabled on new platforms. If you’re reviving an older card, test with it off.
  • iGPU: set to “Auto” or “Disabled.” On some boards, “iGPU first” prevents handoff to the slot.

Save, power down fully, and test a cold boot.

Reseat The Hardware With A Short Checklist

  1. Ground yourself. Power supply unplugged, front panel power button tapped to drain caps.
  2. Inspect the slot. Blow out dust, check for a stray standoff touching traces.
  3. Use the top x16 slot. That lane group is wired straight to the CPU on most boards.
  4. Seat the card firmly. You should hear the latch click. Screw the bracket snug to stop sag.
  5. Connect PCIe power. Match the connectors to the card’s sockets; don’t split a single cable to two high-draw sockets.
  6. Check riser cables. Move the GPU back to a direct slot; risers add one more failure point.

Power And PSU Clues

  • New card, old supply: many cards need higher transient headroom than the sticker wattage suggests.
  • Multi-rail vs single-rail: tripping OCP on one rail cuts power during init. Try separate PCIe cables from the PSU.
  • 12VHPWR: use the vendor cable, avoid loose adapters, and fully seat until it clicks.
  • Quick math: add CPU TDP + GPU TBP + 150W headroom. If your number is close to the PSU rating, try a known good unit.

When Windows Still Lists Only “Microsoft Basic Display Adapter”

  • Show hidden devices in Device Manager, then Scan for hardware changes.
  • Right-click any stale display adapter entries and remove them, ticking the box to delete the driver.
  • Reinstall the vendor package and reboot. If it flips back to the basic driver on every boot, disconnect the internet during install to stop Windows Update from swapping drivers mid-setup.

Fixes For Common Error Codes

Code 31: reinstall the driver package, then reboot. If it returns, SFC /scannow and DISM restore health, then install again.

Code 43: often a driver crash at init. Try a different branch (Game Ready vs Studio, or prior stable). Test the card in another PC to rule out hardware.

Code 12: resource conflict on older chipsets. Move other PCIe cards, disable unused controllers in BIOS, or switch the GPU to the other slot.

Linux Or Dual-Boot Notes

  • For Ubuntu-based distros, install the recommended proprietary driver via “Additional Drivers.”
  • Secure Boot can block kernel modules. Enroll the MOK or switch Secure Boot off for the test. Re-enable when done.

Thermal And Mechanical Red Flags

  • Heavy sag can unseat the contact edge. Add a small bracket or the case’s GPU brace.
  • A bent 12VHPWR cable near the plug can arc. Route the cable straight for the first few centimeters.
  • Dust-clogged coolers can spike temps at POST. Clean fins and fans before repeat tests.

Motherboard And CPU Lane Limits

  • Budget chipsets sometimes drop lanes on the second slot. Stick to the primary x16 slot for testing.
  • Some CPUs share lanes with M.2 slots. Pull one NVMe drive temporarily to test for lane routing quirks.
  • Update the motherboard firmware to the latest stable release to pull in PCIe fixes and device IDs.

Safe BIOS Update Tips

Pick a stable release from your board maker, not a beta. Read the notes for PCIe fixes or GPU ID updates. Back up your current settings with photos. Use the built-in EZ Flash/M-Flash tool inside firmware, or a FAT32 USB stick with the file at root. Keep the system on a steady outlet or UPS. Do not flash through a sketchy Windows tool. After the update, load defaults, set date/time, enable XMP/EXPO again, then set PEG/PCIe as the first display. Power off fully, wait ten seconds, then try a cold boot with …

When To Suspect A Bad Card

  • The fans spin for a second then stop, and the card never shows in BIOS across two boards.
  • The card shows artifacts or hard locks at the Windows logo even with fresh drivers.
  • It works in a different rig only when underclocked. That points to aging VRAM or power stages.

Step-By-Step Flow You Can Follow

  1. Move the monitor cable to the card and reboot.
  2. Reseat the card in the top slot and reconnect power.
  3. Turn off Fast Startup and do a full shut down, then cold boot.
  4. Set PEG/PCIe as primary display in BIOS and save.
  5. Boot Safe Mode, remove old drivers, then install a fresh vendor package.
  6. Show hidden devices, scan for changes, and confirm the card model appears.
  7. Swap PSU cables or the PSU, then test again.
  8. Test the GPU in another PC, or try a known-good GPU in your board.

Why Fast Startup Gets In The Way

Fast Startup mixes hibernation with shutdown. The PCIe bus doesn’t re-initialize cleanly on some systems, so devices that were in a bad state stay invisible on the next boot. Turning it off forces a full init. Reboot after changing the setting.

Driver Branch Choices That Help Stability

  • Studio vs Game Ready: Studio is tuned for a calmer pace and longer validation; a good pick when you just need a steady desktop.
  • Clean install vs express: clean wipes old profiles and stale files. Use it when changing brands or rolling back.
  • Rollback path: if a new release breaks detection, pick the prior stable build that worked for your card.

Error-To-Fix Reference

Error message Meaning Action
“Microsoft Basic Display Adapter” Windows loaded a fallback driver Install the vendor package offline, then reconnect once it sticks.
“Code 43” in Device Manager Init crash or power fault Try a different driver branch; test another PSU or reduce PCIe power load.
“No signal” on monitor Cable or slot not active Move cable to the GPU, reseat the card, and check BIOS display order.

Extra Checks That Save Hours

  • Update chipset drivers so PCIe enumeration works as expected.
  • Remove third-party RGB/fan tools during testing.
  • If running a riser or vertical mount, try the shortest route possible.
  • Pull all USB hubs, capture cards, and PCIe cards during the run.

What To Document Before You RMA

  • Exact board model and BIOS version
  • PSU make, wattage, and cable setup
  • Windows build number and driver version
  • Steps you tried and the point where detection fails

Ready