Displays & Graphics: no signal, artifacts, GPUs and second monitors that refuse to wake

Symptom: The monitor is powered on but shows “No Signal” (or similar).

Likely causes: Wrong monitor input, a loose or bad cable, the PC on the wrong output port, or the PC not sending video at all.

1. Confirm the monitor's input matches the cable's port (HDMI 1 vs 2, DP, etc.).
2. Reseat the cable at both ends, then try a known-good cable.
3. Make sure the cable is in the graphics card's port, not the motherboard's (if you have a discrete GPU).
4. Confirm the PC actually boots (fans, POST beep, or an LED).

Verify: an image appears. Stop if the PC powers on but sends no signal on any port or cable — the fault is the GPU or the machine, not the monitor. See the advanced isolation guides.

Symptom: Fans spin and the PC is on, but there's no picture and the monitor may or may not say “no signal.”

Likely causes: The system isn't reaching display output — a GPU that isn't initializing, the wrong output port, a RAM problem, or no POST.

1. Listen for POST beeps and watch for a motherboard diagnostic LED code; they name the failing part.
2. Check you're using the active GPU's output (see the integrated-vs-dedicated guide).
3. Try the motherboard's own port if your CPU has integrated graphics — if that works, the discrete GPU is suspect.
4. With the power off and unplugged, reseat the RAM and GPU as a last beginner step.

Verify: you get a POST and then the desktop. Stop if there's no POST at all with a clear beep/LED code — that points to board, RAM, or power, and it's a hardware assessment, not a display tweak.

Symptom: No picture, but the monitor is clearly on (LED lit, OSD works).

Likely causes: The monitor is set to a different input than the cable you're using, or auto-input is mis-detecting.

1. Use the monitor's own buttons to open its menu and select the input that matches your cable.
2. Cycle through each input once to be sure.
3. If it keeps flipping on its own, switch the monitor from “auto input” to a fixed input.

Verify: the correct input shows the desktop. Stop if no input shows a picture — then the signal isn't arriving, so this wasn't an input problem.

Symptom: Intermittent picture or no signal that seems to change when you move things.

Likely causes: A bent or worn connector, a kinked cable, or a loose seating.

1. Unplug and reseat both connectors firmly; listen/feel for the clip to engage (DisplayPort has one).
2. Look at both connector ends for bent or missing pins.
3. Swap in a known-good cable and compare.

Verify: a stable picture on a known-good cable. Diagnostic: a bad cable usually affects only that one cable-and-port pair — if another cable works, the first was the cause. If all cables fail on one port, the port or GPU may be at fault.

Symptom: A black screen where you can't tell if the monitor is even on.

Likely causes: The monitor is asleep, on the wrong input, or its power has failed — all of which look identical from the front.

1. Check the monitor's power LED: solid on, blinking, or off each means something different.
2. Open the monitor's on-screen menu — if the menu appears, the panel and power are alive.
3. Test the monitor on another device (a laptop or game console) to confirm it can display anything.

Verify: the monitor shows its own menu and then another device's image. A monitor with power but no menu and no image on any source is likely faulty and should be replaced or repaired.

Symptom: It was working, then went black — either truly off or frozen on the last frame.

Likely causes: Lost input, a cable, a graphics driver crash (screen freezes or goes black), or the monitor losing power.

1. Note whether it's truly off (LED off) or frozen (LED on, last image held).
2. If frozen, press Ctrl + Win + Shift + B to reset the display driver.
3. Reseat the cable and check the monitor's power.
4. If it went black under heavy use, check the GPU temperature — that's a thermal issue.

Verify: the image returns and stays. Stop if it blackouts repeatedly under load — that's thermal or GPU instability, covered in the advanced section.

Symptom: You suspect the cable, but it sometimes works.

Likely causes: A cable that's worn, or a cable whose spec can't carry your resolution/refresh (works at 60Hz, not 144Hz).

1. Test the suspect cable in a known-good device pair (laptop to a known monitor).
2. Test a known-good cable in your own setup.
3. Check the cable's rating (HDMI 2.0/2.1, DisplayPort 1.4) against your target resolution and refresh.

Verify: a confirmed-good cable sustains your resolution and refresh with no dropout. Cable testing only proves the cable — it does not clear the GPU or the monitor, so don't stop there if the problem fits another cause.

Symptom: No power LED, no menu, completely dead.

Likely causes: The power cable, the outlet, a physical power switch, or a failed monitor power supply.

1. Check the power cable and try a known-live outlet (skip the strip for this test).
2. Look for a physical power switch at the back of the monitor and flip it.
3. Try a different power cable if the monitor uses one (many do).

Verify: the power LED comes on. If a live outlet and a good cable still give no power, the monitor's internal power is likely failed — that's a replacement or repair.

Symptom: No picture, or a picture on the “wrong” port, on a system that may have both integrated and discrete graphics.

Likely causes: The monitor is on the integrated graphics port while a discrete GPU is present (or vice versa), so the active adapter isn't driving that port.

1. Work out whether you have a discrete GPU (a horizontal card with its own ports, usually lower on the case).
2. Connect the monitor to the discrete GPU's ports, not the motherboard's.
3. Check Display adapters in Device Manager to see which adapter(s) are present and active.

Verify: the desktop appears on the active adapter's port. If you have a discrete GPU and the motherboard port is blank, that's expected — use the GPU ports, not the board's.

Symptom: A blurry, stretched, or “1024×768” image.

Likely causes: A missing or generic graphics driver, or the monitor not being detected at its native resolution.

1. Open Display settings and set the resolution to the monitor's native (usually marked “Recommended”).
2. If the native option is missing, repair or update the graphics driver.
3. Set the correct refresh rate afterward.

Verify: a crisp image at native resolution. If the native resolution is unavailable and a driver repair doesn't restore it, the driver or the output link is limiting it — see the intermediate driver and bandwidth guides.

Symptom: The image looks wrong or the refresh feels off on a newly connected display.

Likely causes: Windows often defaults a new display to 60Hz and a non-native resolution.

1. Display settings → set resolution to “Recommended.”
2. Open Advanced display → set the refresh rate to the highest stable value.
3. Watch for 30 seconds for flicker before you commit to the higher refresh.

Verify: a stable image at your intended resolution and refresh. If a higher refresh flickers or won't hold, check cable bandwidth — that's an intermediate topic.

Symptom: Soft text or image, as if the focus is off.

Likely causes: Wrong resolution or aspect ratio, analog (VGA) without sync, or an overscanned/“TV” sized image.

1. Set the native resolution and a 16:9 (or the panel's) aspect ratio.
2. On the monitor, set the size/overscan to “PC” or 100% instead of “TV.”
3. For VGA, run the monitor's auto-sync feature.

Verify: crisp text at native resolution. Persistent blur on a digital cable at native resolution suggests scaling or the panel — check the scaling settings next.

Symptom: A partial or frozen picture — sometimes the last frame holds while the cursor still moves.

Likely causes: A graphics driver hang (frozen frame), a split or offset signal, or a mis-seated cable.

1. If it's a frozen frame with a live cursor, reset the driver with Ctrl + Win + Shift + B.
2. If the image is split or offset, fix overscan/aspect on the monitor.
3. Reseat the cable to rule out a partial connection.

Verify: a full, correctly framed image. Recurring frozen frames point to driver or GPU stability — see the advanced TDR and artifact guides.

Symptom: A laptop's external monitor stays dark.

Likely causes: The laptop is asleep, the external output is off, or the monitor is on the wrong input.

1. Wake the laptop and confirm it has a desktop.
2. Press the display-output hotkey (usually Fn plus a monitor icon) to enable the external output.
3. Choose Extend or Duplicate in the projection menu, and confirm the monitor's input.

Verify: the external monitor shows the desktop. If the laptop is awake and the output is enabled but the monitor stays dark, check the cable or dock — the intermediate docking and adapter guides.

Symptom: One cable-and-port combination works; the others don't.

Likely causes: A specific faulty port, or specific faulty cables, rather than the whole system.

1. Map exactly which cable and which port works.
2. Test that “working” cable in another device to confirm it's genuinely good.
3. Test other cables in the working port to see if the port accepts many cables or just one.

Verify: a consistent picture on the working combination. This isolates a specific cable or port — if it's the port that's picky, follow that thread into the advanced port/PCIe isolation.

Symptom: No picture, and you need clues about what's failing before you can see anything.

Likely causes: The system often reports its state through POST beeps, motherboard diagnostic LEDs, and the monitor's LED before any image appears.

1. Listen for POST beeps at power-on (the pattern points to memory, GPU, or no fault).
2. Watch for a diagnostic LED code on the motherboard and look up what it means for your board.
3. Note the fans: do they spin and stop, or run constantly? That changes the diagnosis.

Verify: you've matched a beep or LED code to a specific component. A specific code is a strong pointer — follow it before guessing at cables or settings.

Symptom: Moving lines, “snow,” or a wavy image.

Likely causes: A loose or poor cable (especially analog), interference, or a failing connector; on digital, usually the cable.

1. Reseat the cable and move it away from power cables.
2. Swap to a known-good digital cable.
3. Inspect the connector for damage or corrosion.

Verify: the interference is gone on a clean cable. If interference persists on a good digital cable, the GPU output or the monitor may be degrading — move to hardware isolation.

Symptom: You want a second screen but nothing appears on the external monitor.

Likely causes: The wrong cable or adapter, or the projection mode not set.

1. Identify the laptop's video output (HDMI, USB-C, or DisplayPort).
2. Connect with a cable or adapter that actually carries video (some USB-C cables are charge-only).
3. Press the display hotkey and choose Extend or Duplicate.

Verify: the external monitor shows an extended desktop. If there's still no output, the cable/adapter may not support video — see the intermediate docking and adapter guides.

Symptom: One display works; the second isn't listed in Display settings.

Likely causes: Cable/port, an adapter, the monitor's input, or a GPU output that isn't being offered.

1. Confirm the second monitor's input and power.
2. Try a different cable and a different GPU port.
3. Check Device Manager → Display adapters for a fault, and confirm the adapter reports all its outputs.

Verify: the second display appears in Display settings. If it shows in Device Manager but not as a usable display, or not at all, the GPU output or the adapter is the limit — see the advanced output guides.

Symptom: The second display goes black after sleep or lid-close and won't come back.

Likely causes: The OS/GPU failing to reinitialize that output on wake, or the monitor not waking on signal.

1. Note whether it fails after sleep or after lid-close specifically.
2. Update the graphics driver (wake reinit is a common driver fix).
3. In the monitor's menu, enable wake-on-signal; adjust the OS display power settings for that port.

Verify: both displays return reliably after wake. A consistent wake failure on one specific monitor suggests that monitor's wake-on-signal is failing.

Symptom: The display drops and returns, sometimes with a connection chime.

Likely causes: A loose or failing cable, a bad port, an adapter, or a driver dropping the device.

1. Open Event Viewer and filter for display “connected/disconnected” events — frequent ones point to the physical link.
2. Reseat or swap the cable; try another port.
3. Check for a failing dock or adapter in the chain.

Verify: no dropouts over a period of normal use. If dropouts persist on a good cable and port, the GPU output or the monitor input may be failing.

Symptom: The image flickers or strobes.

Likely causes: A refresh-rate mismatch, a weak cable at high bandwidth, a driver issue, or (less often) a failing GPU or monitor.

1. Set a stable refresh; compare with a lower one to see if flicker changes.
2. Swap to a known-good cable.
3. Update the driver and disable any GPU overclock.

Verify: flicker is gone at a stable refresh. Flicker that follows one specific cable is that cable; flicker independent of cable at any refresh points to the GPU or monitor.

Symptom: You can't select 120/144/165Hz, or it reverts to 60.

Likely causes: Cable or dock bandwidth, the driver, or the monitor's capability at that resolution.

1. Use a DisplayPort 1.4 or HDMI 2.0+ cable for high refresh.
2. Set the high refresh at a lower resolution first to confirm the panel supports it.
3. Set it in the GPU control panel rather than Windows, and update the driver.

Verify: the high refresh holds. If it never holds above 60 even at low resolution with a good cable, the link (cable/dock) or the monitor is capping the bandwidth.

Symptom: A black screen, “Your display driver has stopped responding and has recovered,” or a Code 43 in Device Manager.

Likely causes: The driver hit a timeout (TDR), a faulty install, or GPU instability.

1. Reset the driver (Ctrl + Win + Shift + B) or reboot.
2. Check Event Viewer for TDR events and their timing.
3. If it recurs, do a clean driver reinstall (see the advanced DDU guide) and check GPU temps.

Verify: no recurrence over normal use and gaming. Recurring TDR with a stable driver points to GPU instability or overheating — advanced.

Symptom: The PC boots to a black screen after an update.

Likely causes: The update changed display/driver settings or broke the driver.

1. If you can reach Safe Mode, uninstall the recent display driver there.
2. Or use a System Restore point from before the update.
3. Reset display settings, then reinstall the driver from the vendor.

Verify: a normal display after the driver repair. If you can't reach Safe Mode at all, you may need offline driver removal — that's a recovery situation.

Symptom: Black screen right after a new driver install.

Likely causes: An incompatible or corrupt driver.

1. Boot into Safe Mode.
2. Uninstall the new driver cleanly (DDU for a full clean slate).
3. Reboot to the basic display, then install a known-good driver version.

Verify: a stable display on a working driver. If every driver version fails, the GPU or its output may be the issue — advanced.

Symptom: Boot or login lands on the wrong monitor, or the taskbar is on the wrong screen.

Likely causes: The OS set a different display as primary.

1. Display settings → select the intended display → “Make this my primary display.”
2. Confirm the same in the GPU control panel.

Verify: login and the taskbar are on the intended monitor. If the setting won't stick, it may be reset by a driver or by the BIOS output order.

Symptom: Text is too small or too large, or some apps look blurry.

Likely causes: A DPI scaling mismatch for that monitor.

1. Display settings → set the scale (100/125/150%).
2. If only one app is wrong, use per-app scaling for it.
3. Restart the app after changing its scale.

Verify: readable, non-blurry UI. Persistent blur after correct scaling can be a driver or GPU rendering issue.

Symptom: You want two independent screens or a mirror, and it's not doing what you expect.

Likely causes: The projection mode isn't set, or the displays aren't arranged.

1. Press Win + P to choose Extend or Duplicate.
2. Arrange the monitors in Display settings so windows move the right way.
3. Set per-monitor resolution and refresh.

Verify: you can drag a window between screens (extend) or see the mirror (duplicate). If Extend isn't offered, one display may not be fully detected.

Symptom: The dock works, then a monitor drops, or the refresh is capped.

Likely causes: The dock's bandwidth or USB version, or a power/DisplayPort-alt-mode issue.

1. Connect a monitor directly to the PC to compare against the dock.
2. Check the dock's spec (DisplayPort 1.4, USB-C PD/alt-mode) against your targets.
3. Try a different USB-C port and update the dock's firmware/driver.

Verify: the dock sustains all monitors at the intended refresh. If direct-attach works but the dock caps it, the dock is the bottleneck — a direct cable or a better dock is the fix.

Symptom: An adapter (DP→HDMI, USB-C→HDMI) is flaky.

Likely causes: Passive adapters have bandwidth and EDID limits; a failing adapter mis-negotiates the signal.

1. Note whether the adapter is active or passive.
2. Test a known-good adapter.
3. Check the adapter's maximum resolution/refresh and avoid long adapter chains.

Verify: a stable image on a good adapter. An adapter that only intermittently works is usually the culprit — replace it rather than chasing the PC.

Symptom: A 144Hz monitor only offers 60Hz.

Likely causes: Cable bandwidth, the driver, or the monitor's input/standard on that panel.

1. Use a DisplayPort or HDMI 2.0+ cable.
2. Set the refresh in the GPU control panel.
3. Confirm the monitor's own settings allow the high refresh, and that the GPU supports it.

Verify: 144/165Hz is available and stable. If it's capped at 60 on a top-spec cable, the monitor's input (e.g., that HDMI port on the panel) or the GPU may limit it.

Symptom: Washed-out colors, HDR won't enable, or a black screen when HDR is on.

Likely causes: HDR misconfiguration, a cable that can't carry the HDR signal, or a driver/GPU issue.

1. Turn HDR off first to confirm the base display works.
2. Set a proper SDR-to-HDR tone and check the cable (HDMI 2.0+/DisplayPort 1.4).
3. Update the driver and test in a known HDR app.

Verify: correct colors with HDR on, and the display stays on. If enabling HDR blackouts the display, the link may not carry the HDR signal — use a higher-spec cable or disable HDR.

Symptom: Windows lists the display, but it's black.

Likely causes: The monitor is on the wrong input, is asleep, or the signal is weak.

1. Check the monitor's input and power, and wake it (it may be in standby).
2. Try a different cable.
3. Confirm the correct GPU output is driving it.

Verify: the detected display shows the desktop. A display the OS sees but that stays black on the right input and cable suggests a weak or failing signal path.

Symptom: The laptop's own display is black after wake.

Likely causes: The OS or driver failing to reinitialize the internal panel, or a power-setting conflict.

1. Update the graphics driver.
2. Disable “fast startup” in power options.
3. Adjust the display power settings and test with wake timers off.

Verify: the display wakes reliably. If it persists independent of the driver, the panel or its backlight may be degrading — that's hardware.

Symptom: A daisy-chained monitor on an MST hub stops showing.

Likely causes: MST has bandwidth, refresh, and resolution limits, and a single link failure can drop downstream displays.

1. Identify which monitor dropped (upstream vs downstream).
2. Reduce refresh/resolution to fit MST bandwidth.
3. Try connecting the dropped monitor directly, and check the hub's spec.

Verify: all MST displays are stable within spec. If MST can't sustain your setup, use direct connections or a higher-bandwidth hub — MST drops are usually bandwidth or EDID, not the GPU.

Symptom: The maximum resolution or refresh is lower than you expect, or no signal at high settings.

Likely causes: The cable's standard caps the achievable signal.

1. Check the cable's rating (HDMI 1.4 vs 2.1, DisplayPort 1.2 vs 1.4).
2. Match the cable to the target (e.g., 4K144 needs DisplayPort 1.4 or HDMI 2.1).
3. Replace with a higher-spec cable and re-test.

Verify: the target resolution and refresh are achievable. If a top-spec cable still caps the signal, the GPU or the monitor port is the limit.

Symptom: The second screen mirrors the first instead of extending the desktop.

Likely causes: The projection mode is set to Duplicate.

1. Press Win + P → Extend.
2. Arrange the displays in Display settings.
3. Set independent resolution and refresh for each.

Verify: an independent extended desktop. If Extend isn't available, one display isn't being fully detected.

Symptom: It needs a physical re-plug to show a picture.

Likely causes: A loose or weak connector, a failing port, or an EDID negotiation that fails until reset.

1. Reseat firmly and check for a loose port or worn connector.
2. Try a different port.
3. Note whether it's the cable or the port that needs the reset.

Verify: it stays connected without re-plugging. Diagnostic: needing a physical reset to negotiate points to the physical link (connector, cable, or port) — a port that needs constant re-negotiation may be failing.

Symptom: Colored specks or blocks appear under 3D load but not at the desktop.

Likely causes: GPU instability — core, VRAM, power, or heat — that only shows under load.

1. Confirm the artifacts are load-only (they vanish at idle).
2. Run a GPU stress test to reproduce them reliably.
3. Check temperatures under load and remove any overclock or undervolt.

Verify: artifacts are gone at stock clocks and normal temps. Load-only artifacts are a strong GPU-instability signal — don't keep using it for important work until it's resolved.

Symptom: You see artifacts and don't know which device is producing them.

Likely causes: Both a GPU and a monitor can produce artifacts, but they behave differently when you move the setup.

1. Test the monitor on a known-good PC — if the artifacts stay, it's the monitor.
2. Test a known-good monitor on your PC — if the artifacts stay, it's the GPU.
3. Change the cable — if the artifacts stay, it's not the cable.

Verify: a clean display on the good device, and artifacts on the bad one. This move-the-artifact test is the definitive way to blame the GPU versus the monitor.

Symptom: Texture-specific or blocky artifacts, usually under 3D load.

Likely causes: Failing GDDR or VRAM timing.

1. Confirm the artifacts are 3D/texture-specific and load-dependent.
2. Run a VRAM test that exercises the memory.
3. Compare the pattern with core-artifact patterns (specks vs texture corruption).

Verify: a VRAM test that reports errors confirms VRAM failure. Confirmed VRAM errors mean replacement, not repair.

Symptom: Performance drops, fan noise, artifacts, or shutdowns under load.

Likely causes: Poor cooling — dust, old thermal paste, or a failing fan — causing the GPU to throttle.

1. Monitor GPU temperature under load (a temp reader or the vendor tool).
2. Compare it to the GPU's normal maximum and note any throttling.
3. Clean dust, check the fan, and consider repasting if the card is old.

Verify: temperatures are in range and there's no throttling. A GPU hitting thermal limits needs cooling work — see the overheating guide.

Symptom: Crashes, artifacts, or blackouts under load on a tuned GPU.

Likely causes: An unstable custom clock or voltage.

1. Reset the GPU to stock clocks (the vendor control panel or the tuning tool).
2. Confirm stability at stock.
3. If you retune later, test each step under load.

Verify: the GPU is stable at stock clocks. If it's unstable even at stock, the overclock isn't the only problem — the GPU or power may be involved.

Symptom: Repeated “display driver stopped responding and recovered” messages.

Likely causes: The GPU taking too long to respond — instability, heat, power, or a driver.

1. Check Event Viewer for TDR events and their timing.
2. Rule out heat and any overclock.
3. Do a clean driver install; treat raising the TDR timeout as a diagnostic, not a fix.

Verify: no TDR events under load. Recurring TDR with a stable driver and good temps points to GPU instability or power delivery.

Symptom: Blackouts, no POST with the GPU fitted, or instability under load.

Likely causes: An insufficient or failing PSU, a loose or damaged power connector, or a supply that can't deliver the peak current.

1. With the power off and unplugged, reseat all GPU power connectors.
2. Look for melted or discolored connectors.
3. Confirm the PSU meets the GPU's wattage; test with a known-good PSU if you have one.

Verify: stable operation under load with proper power. A suspect power supply is a safety concern — get it checked or replaced rather than keeping pushing it. Never open the PSU.

Symptom: No display on the GPU's ports, or intermittent behavior, after moving the PC.

Likely causes: The card shifted or wasn't fully seated.

1. Power off and unplug the PC; discharge a bit and use an anti-static precaution.
2. Remove the GPU and reseat it firmly until the retention clip holds.
3. Check the slot for debris and reconfirm the card is level.

Verify: a stable display on the GPU's ports. If it's firmly seated and still fails, the slot or the GPU may be the issue — see the next guide.

Symptom: The GPU works intermittently or not at all, even when properly seated.

Likely causes: A failing or electrically degraded slot that runs the card at a lower link width or drops it.

1. Check the recognized PCIe link width and speed in the GPU tool or Event Viewer (e.g., x16 running as x1).
2. Try another slot if the board has one.
3. Test the GPU in another PC to separate card from slot.

Verify: full link width and stable operation. A card recognized at reduced width hints at the slot — a failing slot may mean a motherboard issue, best left to a professional assessment.

Symptom: Displays routing to the wrong adapter, no image, or games using the weaker GPU.

Likely causes: A system with both iGPU and dGPU, where the output or the per-app GPU isn't what you expect.

1. Identify both adapters in Device Manager.
2. Set the preferred GPU in the vendor control panel or Windows graphics settings.
3. Connect the monitor to the physical output of the adapter you want driving it.

Verify: the intended adapter drives the display and the games. If the dedicated GPU is disabled or failing, you may be running on the iGPU — check that adapter's health.

Symptom: No image on the GPU's ports, and you want to test the integrated graphics.

Likely causes: A failing discrete GPU — the motherboard's iGPU output bypasses it, which isolates it.

1. On a CPU with integrated graphics, connect the monitor to the motherboard port.
2. If the desktop appears, the CPU/board/RAM/power are fine and the discrete GPU is suspect.
3. Recheck the discrete GPU's power and seating.

Verify: a working iGPU image isolates the discrete GPU. If even the iGPU port is blank, the problem is upstream (CPU, board, RAM, or power), not the discrete GPU.

Symptom: POST beeps for a GPU error, or no display even on the GPU's ports and the system may not fully boot.

Likely causes: The GPU isn't initializing — a faulty card, no power, a slot problem, or a BIOS setting.

1. Check the POST codes or beeps for a GPU error.
2. Confirm the GPU has power and is seated.
3. Test a known-good GPU, and reset the CMOS/BIOS to defaults.

Verify: the known-good GPU posts and shows a display. A confirmed dead GPU (no signal even with power, while the iGPU works) means replacement.

Symptom: Displays on the wrong GPU, blackouts, or one GPU being ignored.

Likely causes: Multiple GPUs create output-routing and driver conflicts.

1. Identify all GPUs in Device Manager.
2. Set the primary output in the BIOS or GPU settings.
3. Disable the unused GPU if you don't need it, and update drivers for both.

Verify: displays route to the intended GPU and are stable. Persistent conflicts with correct settings may need a specific multi-GPU driver mode or a hardware change.

Symptom: No display that changes with BIOS settings, or that appeared after a BIOS update.

Likely causes: A BIOS setting (primary display, iGPU/dGPU priority, CSM) or a bad BIOS update affecting output.

1. Enter the BIOS (you may need the iGPU port to see it).
2. Set the correct primary display and reset to defaults.
3. Update or roll back the BIOS if a recent update broke it.

Verify: the display returns with the correct BIOS setting. If you can't access the BIOS and there's no display on any port, the board, CPU, or power may be the issue.

Symptom: Recurring driver resets or blackouts with no obvious trigger.

Likely causes: TDR, driver, or device events that Event Viewer logs with timing.

1. Open Event Viewer → Windows Logs → System.
2. Filter for display and GPU source events and note the timing (load vs idle) and code.
3. Correlate the events with when the problem happens.

Verify: the log pattern matches the symptom (repeated TDR = GPU/driver; repeated device removals = the physical link). The log tells you which layer to pursue — driver, device, or GPU.

Symptom: A warning icon or a code on the GPU in Device Manager.

Likely causes: A driver or hardware fault that Device Manager reports as a code.

1. Open Device Manager → Display adapters and note any warning and its code (Code 43 means the device reported a problem).
2. Check the GPU's properties and events for detail.
3. Use the code to guide the next step (driver reinstall for some, hardware check for Code 43).

Verify: the code is resolved (no warning) after the fix. A persistent Code 43 with a clean driver often indicates a hardware fault — that's a replacement assessment.

Symptom: Driver corruption, black screens, or instability that a normal reinstall didn't clear.

Likely causes: Leftover driver files conflicting with a fresh install.

1. Boot into Safe Mode.
2. Run Display Driver Uninstaller (DDU) to remove all GPU driver files.
3. Reboot and install the latest vendor driver.

Verify: a clean install with no leftover conflicts and stable behavior. If a clean install doesn't help, the issue is likely hardware, not the driver.

Symptom: You want to confirm whether a GPU is stable.

Likely causes: Instability that idle use doesn't reveal but sustained load does.

1. Run a reputable GPU stress tool for a sustained period.
2. Watch for artifacts, crashes, throttling, and temperatures.
3. Compare idle versus load behavior.

Verify: a stable, artifact-free, in-temperature run is a pass; artifacts or crashes are a fail. Safety: don't run extreme loads on a GPU you suspect is failing for long periods. A failed test confirms instability.

Symptom: Load-only texture artifacts that suggest the memory, not the core.

Likely causes: Failing VRAM that errors under memory load.

1. Run a VRAM testing tool that exercises the memory.
2. Note any reported errors and the pattern.
3. Compare the results with the artifact behavior you've seen.

Verify: no VRAM errors means the memory is likely fine; errors mean VRAM failure. A failing VRAM test means the GPU needs replacement.

Symptom: No display, and you need to know which component is dead.

Likely causes: Both a dead GPU and a dead monitor produce “no image,” but isolation separates them.

1. Test the monitor on a known-good PC.
2. Test a known-good monitor on your PC.
3. Swap the cable and check any POST codes.

Verify: the faulty device fails in multiple known-good contexts. This is the definitive isolation — replace the confirmed-dead component rather than guessing.

Symptom: Random, load-triggered artifacts that are hard to catch.

Likely causes: Intermittent instability — power, heat, VRAM, or the core — that's easy to miss.

1. Log the conditions: which app, the load level, and the temperatures.
2. Stress-test to try to reproduce it reliably.
3. Remove any overclock, check power connectors, and check temps.

Verify: a reproduced and explained cause; if it stays unreproducible, reduce risk (stock clocks, good cooling) and re-test after changes. Intermittent, unexplained load artifacts are a warning sign — plan to test further or replace rather than ignore them.