You power on your PC, the fans spin up, the case lights come on, but your monitor just sits there showing “No Signal,” “No Cable Connected,” or simply a black screen. Sometimes the monitor works fine on HDMI but refuses to detect your GPU over DisplayPort. Other times the screen flickers back to life mid-session, or only wakes up after you unplug and replug the cable a few times. The pattern is maddeningly inconsistent, which is exactly why people assume the worst — a dead graphics card or a failed monitor.
The good news: in the overwhelming majority of cases, this is a cable, handshake, or power-state issue, not failed hardware. DisplayPort’s negotiation between GPU and monitor is more fragile than HDMI’s, and a handful of settings and physical checks resolve most instances in under fifteen minutes. Work through the fixes below in order — they’re arranged easiest first, so you’ll often stop before reaching the harder ones. If your screen is completely dead, you can borrow a TV or another monitor temporarily, or fall back to an HDMI cable just to get into Windows and adjust settings while you troubleshoot the DP connection.
Likely Causes
| Cause | How to confirm | Fix difficulty |
|---|---|---|
| Loose or partially seated DisplayPort cable | Unplug and firmly reseat both ends until the connector clicks into the latching port | Very easy |
| Wrong input source selected on the monitor | Press the monitor’s input/source button and cycle through inputs to see if DP appears | Very easy |
| Cable or adapter that doesn’t support your resolution/refresh rate | Swap in a VESA-certified DP cable; check whether the failure happens only at high refresh rates | Easy |
| GPU or monitor power-state handshake failure after sleep | Does the signal disappear only after the PC sleeps or the display turns off? Cold reboot (full shutdown, not restart) often restores it | Moderate |
| Outdated GPU driver or faulty driver install | Signal loss started after a driver update; Device Manager shows warnings under Display adapters | Moderate |
| Monitor firmware or DP version mismatch (e.g., DP 1.4 device on a port set to an older/incompatible mode) | Signal drops only when the monitor runs at its maximum refresh rate or with DSC enabled | Harder |
Fix 1: Reseat the Cable and Select the Right Input
What causes it
DisplayPort connectors use a latching mechanism, and it’s common for a cable to look plugged in while only partially seated — especially if the cable’s weight pulls on the connector or the latch tab has broken off. Monitors also sometimes stay stuck on the last-used input.
How to check
Power off the monitor, unplug the DP cable at both ends, inspect the connector for bent pins in the port, then plug it back in until you feel or hear the latch click. While it’s unplugged, press the monitor’s OSD input button (often labeled with an arrow or “Source”) and confirm which inputs exist. Power the monitor back on and manually select the DisplayPort input rather than Auto.
What to do
If reseating works but the problem recurs, check whether the cable sags or pulls at an angle. Route it with slack, or use a short cable-support tie near the connector. On monitors where the latch is broken, a gentle push-fit cable or a small piece of electrical tape holding the connector can stop micro-movement from breaking the handshake.
How to undo it
Nothing to reverse — just unplug the cable normally. Depress the latch (most DP connectors have a small button or lever on top) before pulling to avoid damaging the port.
Fix 2: Perform a Cold Boot and Power Drain
What causes it
GPUs and monitors cache handshake state. After sleep or a fast startup, the link can fail to retrain, leaving the monitor waiting for a signal that never arrives. Windows Fast Startup, which keeps the kernel in a hibernation-like state, makes this worse because a normal “Shut down” isn’t a true power-off.
How to check
Note whether the failure follows sleep or shutdown. If a restart fixes it but a shutdown doesn’t (or vice versa), the power state is involved.
What to do
Shut down Windows fully, flip off the PSU switch on the back of the case, then press and hold the case power button for 30 seconds to drain residual power. Unplug the monitor from wall power for 60 seconds at the same time. Flip the PSU back on and boot. To prevent recurrence, disable Fast Startup: open Control Panel > Power Options > “Choose what the power buttons do” > “Change settings that are currently unavailable,” then untick “Turn on fast startup (recommended)” and save.
How to undo it
Return to the same Control Panel page and re-tick Fast Startup if you rely on faster boots and can live with the occasional handshake glitch.
Fix 3: Swap or Replace the DisplayPort Cable
What causes it
Not all DP cables are equal. Cheap or uncertified cables pass 1080p fine but fail at higher bandwidths — a 4K 144 Hz or 1440p 240 Hz signal needs the full bandwidth of a VESA-certified cable. Adapters (especially DP-to-HDMI and Mini DisplayPort conversions) are a frequent failure point too, since DP outputs use a different signaling type than HDMI sources.
How to check
Borrow or buy a VESA-certified DisplayPort cable of the appropriate generation (look for “VESA Certified DisplayPort” markings and, for high refresh rates, a cable rated for DP 1.4 or HBR3). Test at your monitor’s native resolution. If the signal only drops when you set a high refresh rate or resolution, the cable is almost certainly the culprit. Also test the suspect cable on another PC or monitor to isolate it.
What to do
Replace the cable with a certified one of reasonable length — VESA recommends against passive cables longer than about 2 meters (roughly 6.5 feet) for full-bandwidth signaling; go shorter or use an active/optical cable for longer runs. Replace cheap adapters with active, powered ones and plug any adapter’s USB power lead in if it has one.
How to undo it
Swap the old cable back if you need to, though there’s usually no reason to. Keep the certified cable; it eliminates this variable permanently.
Fix 4: Test the Port and Lower the Link Rate
What causes it
Modern GPUs have multiple DP outputs, and monitors sometimes have two DP inputs with different behavior. Additionally, running the link at maximum speed (HBR3) can fail on marginal cables or older monitors, even when a lower link rate trains reliably.
How to check
Move the cable to a different DP output on the GPU and a different DP input on the monitor (if it has more than one). If one specific port works reliably, you’ve found a failing port. On NVIDIA cards, open NVIDIA Control Panel > Change Resolution, and check whether your native resolution/refresh appears. On AMD, open AMD Software: Adrenalin Edition > Display settings.
What to do
Permanently use the port combination that works. Many monitors expose a “DisplayPort” version setting in their OSD (often under System, Input, or a Service menu — commonly listed as DP 1.1/1.2/1.4). If your monitor shows “No Signal” at boot or after sleep, switching the OSD setting from DP 1.4 down to DP 1.2 (or up from 1.1 to 1.2) frequently stabilizes the handshake, at a possible small cost to maximum refresh rate. Change one setting at a time and test.
How to undo it
Return to the monitor’s OSD and set the DisplayPort version back to its original value, or move the cable back to the original ports.
Fix 5: Clean-Reinstall Your GPU Driver
What causes it
A botched driver update or leftover files from a previous driver can corrupt the GPU’s display-output initialization, particularly for DisplayPort link training at startup. If signal loss began right after a driver update, this is a prime suspect.
How to check
Open Device Manager (Win + X > Device Manager), expand Display adapters, and look for yellow warning triangles. Check the driver date in Properties > Driver — does it coincide with when the problems started? Also try booting into Safe Mode: if the display works there over DP, the driver stack is implicated.
What to do
Download the latest driver from your GPU vendor’s site (NVIDIA, AMD, or Intel). Run the installer and choose the clean-install/custom option, which removes previous settings. For stubborn cases, boot into Safe Mode, run Display Driver Uninstaller (DDU) from Wagnardsoft, select your GPU type, and click “Clean and restart.” Then install the fresh driver normally. During install, keep the “perform a clean installation” box ticked in the NVIDIA installer if offered.
How to undo it
Roll back via Device Manager > Display adapters > [your GPU] > Properties > Driver tab > “Roll Back Driver” (if available), or reinstall the previous driver version downloaded from the vendor’s archive.
Fix 6: Disable Deep Sleep / Adjust Monitor Power Settings
What causes it
Many monitors have a “Deep Sleep” or aggressive auto-standby mode. When the monitor enters deep sleep, some models take an unusually long time — 10 to 30 seconds or more — to retrain the DP link, or fail to wake at all without a power cycle.
How to check
Open the monitor’s OSD menu (buttons or joystick on the bezel), look under System, Power, or Energy settings for “Deep Sleep,” “Auto Standby,” or “Power Save.” If enabled, and the no-signal issue happens only after idle periods, this is likely your cause.
What to do
Disable Deep Sleep in the OSD. Then, in Windows, go to Settings > System > Power & battery > Screen and sleep and extend the “Turn off my screen when inactive” timer, or set it to Never while troubleshooting. If the issue disappears, re-enable screen-off timers gradually to find a workable middle ground.
How to undo it
Re-enable Deep Sleep in the same OSD location, and restore your preferred Windows screen-off timers under Settings > System > Power & battery.
Fix 7: Test With Integrated Graphics and Isolate the Hardware
What causes it
If every cable, port, and setting check has failed, either the GPU’s DisplayPort outputs or the monitor’s DP input may have failed. Integrated graphics (available on most consumer CPUs) let you determine which side is at fault.
How to check
Shut down, remove the discrete GPU (or leave it in but move the cable), and plug the DP cable into the motherboard’s video output. Enter the BIOS/UEFI if needed to enable iGPU output — commonly under Advanced > System Agent (Intel) or Advanced settings (AMD) — then boot into Windows. If the monitor works over the motherboard’s DP, the monitor and cable are fine and the graphics card is suspect. Conversely, test the monitor with another PC, a laptop with DP/USB-C DP Alt Mode, or a Dock.
What to do
If the GPU’s DP outputs are dead but it otherwise works, run your display over HDMI or USB-C on the same card, or use an active DP-to-HDMI adapter, and plan a card replacement or RMA. If the monitor’s DP input is dead but HDMI works, use HDMI and contact the manufacturer about repair — many brands cover DP input failure under warranty.
How to undo it
Reinstall the discrete GPU and move the cable back to the card’s outputs. Re-disable the integrated GPU in Device Manager (right-click the iGPU under Display adapters > Disable device) if you had enabled it, to avoid conflicts.
If Nothing Works
If you’ve worked through every fix and the DisplayPort input still refuses to train a signal, you’ve likely isolated a genuine hardware fault — either the GPU’s DP transmitter or the monitor’s DP receiver. Before declaring it dead: test the monitor’s DP input with a second source (a laptop with USB-C DP Alt Mode, another PC, a mini PC) and test the GPU’s DP output with a second monitor. If both fail in only one direction, the fault follows that device. Contact the manufacturer: monitor DP port failures are a recognized warranty category for brands like Dell, LG, ASUS, and Gigabyte, and GPU vendors will usually honor RMA for dead display outputs. In the meantime, an active DP-to-HDMI 2.1 adapter or a plain HDMI cable at a lower refresh rate will keep you working. As a last resort, a DP 1.4-capable USB-C/Thunderbolt graphics output from a dock can bypass the GPU’s DP ports entirely.
FAQ
Why does DisplayPort fail after sleep when HDMI works fine?
DisplayPort uses a more complex link-training handshake than HDMI, and both the GPU and monitor have to re-negotiate the link on wake. Power-saving features, Fast Startup, and Deep Sleep modes can interrupt that handshake. Disabling Fast Startup in Windows and Deep Sleep on the monitor resolves this for most people.
Can a bad DisplayPort cable really cause “No Signal”?
Yes — and it’s one of the most common causes. Uncertified or damaged cables may handle low resolutions but fail at the bandwidth needed for 1440p or 4K at high refresh rates. Always test with a VESA-certified cable, ideally under about 2 meters long for full-bandwidth signals.
Should I use DisplayPort or HDMI for gaming?
For high refresh rates at 1440p and above, DisplayPort generally offers more bandwidth headroom and supports features like DSC on more devices. HDMI 2.1 is competitive on modern cards and monitors, and it’s the better fallback if your DP connection is unstable. Both are fine for 1080p at 60–144 Hz.
My monitor says “No Signal” but the PC is clearly on — is my GPU dead?
Almost certainly not yet. A completely failed GPU usually prevents boot or causes artifact crashes, not just a missing signal. Work through cable reseating, cold boot with a power drain, input selection, and a different cable before suspecting the card. Testing with a different monitor or over the motherboard’s video output will give you a definitive answer.
