GPU Not Detected? PCIe Slot, Motherboard, and BIOS Settings Troubleshooting Guide
Key Takeaways
A graphics card the system cannot see is not necessarily a dead card. Detection depends on the PCIe slot, the motherboard, and BIOS settings such as Above 4G Decoding and CSM. This guide explains PCIe link training, the three BIOS settings most easily overlooked, slot and riser-cable causes, and a step-by-step elimination order to try before suspecting the card itself.
Introduction: The Card Is Installed, But the System Cannot See It
A new card is installed, the PC powers on, and yet the system behaves as if no graphics card is there. Device Manager may show no card at all, or show it with a warning. The display may work through integrated graphics while the discrete card sits unrecognised. Or the machine may not complete boot at all.
The instinct is to conclude the card is dead. But detection is a negotiation between the card, the motherboard, and the system firmware — and any side of that negotiation can be the one that fails. This guide covers the system side: the PCIe slot, the motherboard BIOS settings, and the riser cables used in vertical mounts. A separate topic is damage to the card’s own edge connector (the gold fingers): that concerns physical damage on the card side, while this guide covers the system side. These are the causes most easily overlooked, and several of them are fixed without any repair.
How PCIe Detection Works
PCIe is a point-to-point serial connection: the graphics card connects to the motherboard's chipset or CPU through the PCIe slot, with no shared bus in between. At startup, the two ends perform link training — a negotiation in which they agree on how many lanes to use (for example, x16) and at what signalling rate (the generation: Gen3, Gen4, Gen5, and so on).
Two properties of that negotiation matter for diagnosis:
- It can step down. If signal quality is imperfect, the link may settle for fewer lanes (x8, x4) or a lower generation than the hardware supports. A card running at x8 or Gen3 is not necessarily faulty; the negotiated result reflects the state of the slot, the riser cable, and signal integrity.
- It can fail outright. If negotiation fails badly enough, the system does not detect the card at all. That is the "not detected" state — and it can be caused by the slot, the cable, the settings, or the card.
The negotiated lane count and generation are therefore diagnostic readings, not just performance trivia. A card that detects at reduced lanes is telling the user something about the physical link.
Three Motherboard BIOS Settings That Govern Detection
These three settings live in the motherboard BIOS / UEFI setup, and they are the most easily overlooked system-side causes of detection failure. Note that BIOS menu names vary between board makers; the underlying functions are what matter.
| Setting | What it does | When to check it |
|---|---|---|
| Above 4G Decoding | Allows the system to assign more than 4 GB of address space to the graphics card | A large-memory card is not detected, especially after a card or board upgrade |
| Resizable BAR (ReBAR) | Allows the CPU to access the card's entire video memory at once instead of in small chunks | Detection or stability problems after enabling it, or after a platform change |
| CSM / Legacy mode | Provides compatibility for older boot methods | A large-memory card fails to initialise while CSM is enabled; pure UEFI mode may be required |
Above 4G Decoding is the first setting to verify. A graphics card with a large amount of video memory needs address space above the 4 GB boundary to initialise fully. If Above 4G Decoding is disabled, the system may be unable to map the card's memory, and the card may fail to initialise or not be detected. Cards with modest memory may work without it; cards with large memory may not. After a card upgrade, this is a prime suspect.
Resizable BAR (ReBAR) allows the CPU to access the whole video memory in one mapping rather than in small windows. It requires simultaneous support from the motherboard, the CPU, the graphics card, and the card's VBIOS — all four. If ReBAR is enabled on a combination that does not fully support it, initialisation problems can follow. Note the reverse as well: failure to enable ReBAR is generally only a performance difference, not a fault. ReBAR being off is not, by itself, a problem to fix.
CSM (Compatibility Support Module) provides legacy boot compatibility for older operating systems and boot methods. In some combinations, CSM enabled alongside a large-memory graphics card prevents the card from initialising; switching to pure UEFI boot mode resolves the detection failure. If a card is not detected and CSM is enabled, testing with CSM disabled (UEFI-only mode) is a legitimate diagnostic step — after noting the original setting so it can be restored.
One caution: changing BIOS settings is safe when done deliberately, one setting at a time, with the original value noted. Reflashing the motherboard BIOS is a different matter entirely — it carries real risk and should not be attempted as a casual troubleshooting step. Settings changes are the scope of this guide; BIOS flashing is not.
Slots and Contact: The Physical Side
Detection also depends on the physical connection between card and slot:
- Dust in the slot. Dust and debris in the PCIe slot can break contact on individual pins. A slot that looks clean may still benefit from a careful inspection.
- Incomplete seating. A card that is not fully seated — common after moving a PC, or where a heavy card has shifted — may make partial contact. Re-seating the card, with the PC powered off and unplugged, is the basic fix.
- Physical slot damage. A cracked slot, a bent pin, or a slot stressed by a heavy card without support can cause intermittent or total detection failure.
- Trying another slot. Moving the card to a different PCIe slot is a decisive test. If the card is detected in another slot, the original slot — or its contact — is suspect. If it fails in every slot, attention moves back to the card, its settings, or its power connections.
Heavy cards deserve a note here: a card that sags in its slot puts sustained mechanical stress on the slot and the card's connector. A support bracket removes that stress and prevents contact problems that develop slowly over time.
Riser Cables and Vertical Mounts
Vertical GPU mounts use a riser cable — an extension that carries the PCIe signal from the motherboard slot to the card. Riser cables add length and signal loss to the link, and not every riser cable sustains the highest signalling rates.
The practical consequence: a system that fails to detect a card through a riser, or detects it only intermittently, may be a signal-integrity problem rather than a card problem. A useful diagnostic step is to set the slot to a lower PCIe generation in the motherboard BIOS (for example, from Gen4 to Gen3) and observe whether detection becomes stable. If a lower generation restores detection, the riser cable's signal quality is the likely limiter — the cable is not necessarily "broken", but it cannot sustain the higher rate reliably. Removing the riser and testing the card seated directly in the slot is the decisive confirmation.
What the System Itself Reports
Several system-side clues help narrow the problem:
- Device Manager. If the card appears with a warning, note the reported state. Windows error Code 43, for example, is a generic "device reported a problem" code — it means the device is not working, not why. Treat it as a direction to investigate further, not as a diagnosis.
- Motherboard debug LEDs. Many boards have LEDs or a numeric debug display that indicate which boot stage the system reached. A system that stalls at the graphics stage behaves differently from one that passes graphics and stalls elsewhere.
- Cross-machine test. A card detected in another machine but not in its own points at the system side: slot, settings, power, or riser. A card detected nowhere points back at the card.
Step-by-Step Elimination
Follow this order, from the outside in. Before changing any BIOS setting, note down the original value so it can be restored. Stop as soon as the card is detected, and note which step fixed it.
- Confirm power. With the PC off and unplugged, verify every auxiliary power connector on the card is firmly seated at both ends.
- Reseat the card. Remove the card, inspect the slot for dust or damage, and reinstall it fully, confirming it is level and the latch engages. If the card is heavy, use a support bracket so its weight does not hang from the slot.
- Try another slot. If a second PCIe slot is available, test the card there.
- Check BIOS settings. Verify Above 4G Decoding is enabled for a large-memory card, test CSM disabled (pure UEFI) if CSM is on, and review ReBAR in light of whether the platform supports it.
- Test the PCIe generation. If a riser cable is in use, set the slot to a lower generation and observe. Then test the card seated directly in the slot without the riser.
- Cross-test. Try the card in another machine, or try a known-good card in this machine. The result separates system-side from card-side causes.
- Consider the card. Only after the system-side steps have been exhausted does the card itself become the primary suspect.
FAQ
Q: Device Manager shows the card with a yellow warning. What does that mean?
A: It means the system can see the card but the device is reporting a problem. Code 43, a commonly seen code, is a generic error — it does not identify which part of the card is at fault. Check drivers, BIOS settings, and power connections before concluding the card is faulty, and note exactly which code is shown.
Q: I enabled ReBAR and now the card is not detected. What happened?
A: ReBAR needs support from the motherboard, CPU, card, and VBIOS together. Enabling it on a combination that does not fully support it can interfere with initialisation. Revert the setting, confirm the card is detected again, and then verify support on each of the four sides before re-enabling.
Q: Why is the same card detected in another PC but not in mine?
A: Because detection is a negotiation between the card and the system. The other machine's slot, settings, power delivery, and BIOS version may all differ. The difference between the two machines is the diagnostic information: compare BIOS settings (Above 4G Decoding, CSM), try another slot, and check power connections on the machine that fails.
Q: My card detects at x8 instead of x16. Is it broken?
A: Not necessarily. A negotiated x8 link reflects signal quality or a slot limitation, and it can also result from a slot that is electrically wired for fewer lanes. Check seating, dust, and riser cables, and confirm what the slot itself is wired for. A card that works reliably at x8 has a link problem, not necessarily a card problem.
Q: How do I clean dust out of the PCIe slot?
A: With the PC powered off and unplugged, blow loose dust out gently with air. Do not poke at the pins inside the slot with a hard object, and do not use a damp cloth or cleaning agents. Deep dirt or physical damage should be left to a professional.
Q: Should I update the motherboard BIOS to fix detection?
A: A motherboard BIOS update can resolve compatibility problems, but reflashing a motherboard BIOS carries real risk: an interrupted flash can leave the board unbootable. Exhaust the settings, slot, and cross-testing steps first. If a BIOS update is genuinely indicated, it should be done carefully, with the update obtained for the exact board model, and not interrupted. If you are not confident doing this, do not attempt it — bring the machine in for repair instead.