Quick Answer: A “No Signal” message means the monitor itself is working fine — it has power and is actively displaying that message, which a genuinely dead panel can’t do. The problem is almost always upstream: a loose or wrong cable, a mismatched input source, or — on a freshly built or upgraded PC — the single most overlooked cause, a cable plugged into the motherboard’s video port instead of the graphics card’s, which most motherboards disable outright once a discrete GPU is installed. Per Dell’s own support documentation, the monitor’s power LED color tells you which situation you’re in: solid white or green means it has power and is looking for a signal, while amber, orange, or blinking means it’s powered but nothing is arriving.
It’s easy to assume a black screen with a “No Signal” overlay means something has failed. In reality, that message is good news — it’s proof the panel, its power supply, and its internal electronics are all working. Here’s what actually causes it and how to work through the fix list in the right order.
”No Signal” is not the same problem as a monitor that won’t turn on
- A truly dead monitor shows nothing at all — no message, no backlight, no power LED activity. If you’re dealing with that instead, our monitor won’t turn on guide covers power-supply and internal-fault troubleshooting specifically.
- “No Signal” means the panel is receiving power and is actively working — it’s rendering that exact message on its own, which requires functioning display electronics. The fault is somewhere between the source device and the panel, not inside the panel itself.
- If this only happens after the PC has been asleep, that’s a related but distinct issue — see our monitor won’t wake from sleep guide, which covers the specific standby-and-resume failure mode rather than a signal that never arrives in the first place.
The most common causes, in the order to check them
- The cable is in the motherboard’s port, not the graphics card’s. This is by far the most common cause on a new build or a GPU upgrade. Once a discrete graphics card is installed, most motherboards disable their own integrated video output entirely — a cable plugged into the board itself isn’t just misconfigured, it’s connected to a port sending nothing. Trace the cable back to where it physically enters the case and confirm it’s in the card, not the motherboard’s built-in port just above or below it.
- A loose, damaged, or wrong-version cable. Reseat both ends firmly first. If that doesn’t help, inspect the cable for creases or bent pins, and confirm the cable version actually supports your resolution and refresh rate — an older HDMI 2.0 cable pushed to a 4K/120Hz+ signal can drop to no signal rather than just looking degraded.
- The monitor’s input source doesn’t match the port in use. Cycle through the monitor’s OSD input-select menu (HDMI 1, HDMI 2, DisplayPort, USB-C) — plenty of “no signal” cases are just the monitor listening on the wrong port.
- An unsupported resolution, refresh rate, or VRR mode. A resolution or refresh-rate setting, or an enabled G-Sync/FreeSync mode the panel or an intermediate KVM/dock doesn’t support, can push the output outside what the monitor can display. Booting into Safe Mode forces a basic, universally supported resolution and is the fastest way to confirm this is the cause.
- A damaged or dirty port on either end. Inspect both the monitor’s port and the source device’s port for bent pins, dust, or corrosion.
- A graphics card that’s come loose, or a driver issue. Confirm the discrete GPU is fully seated and its power cables are connected, and try a clean driver reinstall rather than an in-place update — this is a frequently reported fix on NVIDIA’s own community forums after a driver update leaves one output (often DisplayPort while HDMI keeps working) with no signal.
Fix list, in order
| Cause | How to confirm it | Fix |
|---|---|---|
| Cable in motherboard port, not GPU | Trace the cable to where it enters the case | Move the cable to a port on the graphics card itself |
| Loose or wrong-version cable | Reseat both ends; check for visible damage | Firmly reseat, or swap in a certified cable rated for your resolution/refresh |
| Wrong input source selected | Open the monitor's OSD input menu | Cycle to the port actually in use (HDMI 1/2, DP, USB-C) |
| Unsupported resolution/refresh/VRR | Boot into Safe Mode (forces a basic resolution) | Lower resolution/refresh rate, or disable G-Sync/FreeSync |
| Damaged or dirty port | Visually inspect both ends for bent pins/debris | Clean gently, or use a different port |
| Loose GPU or driver fault | Check the card is seated and powered; note which port fails | Reseat the card, or do a clean driver reinstall |
Work down the list roughly in this order — the first three causes resolve the large majority of “No Signal” cases in under a few minutes, and the last two are worth ruling out only once the obvious connection issues are eliminated.
Cables worth keeping on hand to rule this out fast
Cable Matters Ultra High Speed HDMI 2.1 Certified Cable — Best for Ruling Out a Bad Cable
- Certified to the full HDMI 2.1 48Gbps spec, so it isn't the bottleneck if your GPU and monitor both support high-refresh 4K — a common blind spot with older or uncertified cables.
- Keeping one on hand means a "no signal" troubleshooting session starts with a known-good cable instead of guessing whether the one already in use is the problem.
- Works for the general no-signal fix list above, not just high-refresh gaming setups.
Cable Matters VESA-Certified DisplayPort 1.4 Cable — Best for DisplayPort-Specific No Signal
- VESA certification matters here specifically because DisplayPort no-signal issues are more often tied to an uncertified or underspec'd cable than HDMI ones are.
- A clean swap-in test when one port on a monitor works and another doesn't — isolates whether the fault is the cable or something further upstream (GPU, driver, port).
No Signal, by the numbers
- Solid white/green vs. amber/orange/blinking. Per Dell’s own monitor support documentation, the power LED color tells you which situation you’re in before you touch a single cable — solid means powered and looking for a signal, amber/orange/blinking means powered but nothing is arriving.
- Six distinct causes, in rough order of how often they’re the actual fault. From cable/port mismatches down to a loose GPU or driver fault — a genuinely broken monitor is the least likely explanation, not the first thing to suspect.
- One port working, the other not, is a documented driver-update side effect. NVIDIA’s own community forums have multiple threads describing a display output going to No Signal specifically after a driver update, most often resolved by a clean reinstall rather than an in-place upgrade.
The bottom line
A “No Signal” message is one of the least alarming things a monitor can show — it’s direct proof the panel and its power supply both work. Start with the cheapest, fastest checks (the right port, a firmly seated cable, the correct input source) before assuming anything is actually broken, and remember that a fresh build or GPU upgrade makes the motherboard-vs-graphics-card port mix-up the single most likely cause. If the monitor won’t power on at all instead, see our monitor won’t turn on guide, and if this only happens after standby, our monitor won’t wake from sleep guide covers that specific case. And if the monitor drops signal and shuts off repeatedly rather than showing a steady “No Signal” message, a loose cable or a power-saving timer is more likely than a source problem — see our monitor keeps turning off guide for that recurring pattern.