Monitor Says "Out of Range" or "Not Supported" Despite a Signal? Panel Limits, EDID, Driver Custom Modes & Safe-Mode Recovery Diagnosis Guide

| HK GPU Fix

Monitor Says "Out of Range" or "Not Supported" Despite a Signal? Panel Limits, EDID, Driver Custom Modes & Safe-Mode Recovery Diagnosis Guide

Key Takeaways

When a monitor shows 'out of range' or 'not supported', the panel has received a signal but refused its timing. The rescue is a fix from a working second monitor, or a lower standard mode, first, then a single-monitor direct test to find which link set the rejected mode.

First, Read the Message Literally: A Signal Arrived, and the Panel Refused It

The words on screen are the diagnosis, and they are worth reading literally before anything is unplugged. "Out of range", "not supported", "input not supported", "mode not supported" and their equivalents are not the same message as "no signal". A "no signal" message means the panel is receiving nothing it can recognise as an input at all: no cable connection, no output from the source, or a signal so broken that the panel cannot even detect it. An "out of range" message means something importantly different: a signal is arriving, the panel can see that a signal is there, and it has decided that the timing of that signal falls outside what its scaler can display.

That distinction is the whole foundation of this guide, and it is also what separates this guide from its neighbours. A guide about a monitor showing no signal at all deals with detection failure: cables, outputs, inputs and power. A guide about a screen that goes black intermittently, while otherwise working, deals with a signal that drops after it has been accepted. A guide about a 4K display locked at 60Hz when 144Hz was expected deals with a mode that was accepted but capped, usually by bandwidth, not rejected outright. A guide about a television refusing 4K at 120Hz or cropping the picture deals with television-specific handling, overscan and television input limits. A guide about generic plug-and-play detection, where modes are simply missing from the settings list, deals with a mode that was never offered. This guide deals with the opposite situation: a mode that was sent, and was refused, and the panel is telling you so in plain language.

The practical consequence is encouraging. A rejected mode is usually a settings problem, not a dead panel and not a dead graphics output. Somewhere in the chain — the operating system, the graphics driver, a custom mode, a game, or a second display's settings carried over to the wrong screen — a timing was chosen that this particular panel cannot show. The task is to get the picture back with a timing the panel does accept, and then to find which link in the chain chose the rejected one, so that it is not chosen again.

Two further distinctions belong at the start, because they prevent the most common wasted effort. First, an "out of range" message during normal desktop use and an "out of range" message that appears only when a particular game launches are the same panel behaviour with different suspects: in the first case the desktop mode itself is the suspect, and in the second the game's own resolution or refresh setting is the suspect, while the desktop mode may be perfectly fine. Second, an "out of range" message on one monitor of a multi-monitor setup does not indict the whole system. It indicts the mode assigned to that monitor, and the healthy monitor beside it is an asset: it can be used to see the settings and correct the rejected mode, which is far easier than working blind.

How a Panel Decides Whether a Mode Is Acceptable

A monitor is not a passive screen that shows whatever arrives. Inside every monitor is a scaler, a chip that takes the incoming signal and converts it into the exact pattern of pixels the panel itself uses. The panel has a native resolution — the fixed grid of physical pixels built into it — and a set of timings its scaler is designed to accept. A display mode is not just a resolution number. It is a bundle of parameters: the horizontal and vertical pixel counts, the refresh rate, the blanking intervals (the silent gaps between lines and frames during which the panel prepares for the next line or frame), the pixel clock (how fast pixels are sent), the scan type, and the timing standard used to compute all of these.

When a signal arrives, the scaler checks the bundle against its own limits. If the resolution is higher than the scaler can process, if the refresh rate is higher than the panel can sustain at that resolution, if the pixel clock exceeds what the scaler or the input can carry, or if the blanking intervals follow a variant the scaler does not recognise, the scaler refuses the signal and the panel displays its rejection message instead of a picture. The message is the scaler's polite refusal, not a symptom of damage.

This is why two monitors can react differently to the same computer. A mode that one panel accepts without complaint can be refused by another panel with a lower scaler limit, a lower maximum refresh rate, or a narrower set of accepted timings. Swapping monitors does not change the computer's output; it changes the judge. A mode that is "supported" is therefore always supported by a particular panel, never supported in the abstract, and a setting that worked on a previous monitor is no evidence that it will work on the current one.

It is also why a mode can be refused even when its headline numbers look modest. A resolution and refresh rate that seem unremarkable can still carry a timing variant — an unusual blanking interval, a reduced-blanking variant the scaler does not implement, or a manually entered custom timing — that the scaler rejects. The headline numbers are not the whole mode. Two modes can share the same resolution and refresh rate and differ in timing details, and the panel can accept one and refuse the other. When a mode is refused, the investigation must therefore look beyond the resolution and refresh numbers to how the mode was constructed.

EDID: How the Computer Learns What the Panel Accepts

Left to itself, a computer does not guess which modes a panel accepts. It asks. Every modern monitor carries a small data block called EDID, Extended Display Identification Data, stored in the monitor itself and read by the graphics driver over the display cable when the monitor is connected or detected. EDID describes the panel: its native resolution, the range of refresh rates it supports, the standard timings it accepts, and identifying information about the model. The operating system and driver then build the list of offered modes from that description, and modes outside the described range are normally not offered at all.

This system works well when the whole chain reports honestly, and it fails in instructive ways when any link in the chain misreports. A faulty cable, a low-quality adapter, a docking station, a KVM switch, or a video splitter can corrupt, block, or substitute the EDID data. When the driver cannot read the panel's EDID, it falls back to a generic description — a safe, minimal set of modes that may not include the panel's native resolution, or may include a mode the panel does not actually accept. When an adapter or switch substitutes its own EDID, the driver may offer modes belonging to a different device entirely. In both cases the user sees a settings list that looks authoritative and is in fact wrong, and a mode chosen from that list can be refused by the real panel.

EDID problems also explain a pattern that otherwise looks like a haunted machine: a mode that works when the monitor is connected directly, but is refused when the same monitor is connected through a dock, adapter, or switch. Nothing about the panel or the computer has changed. The reporting chain has changed, and with it the list of modes the driver believes are safe. The same logic applies to a monitor that works on one input but not another: different inputs on the same monitor can carry different EDID data or different scaler limits, so a mode accepted on one input can be refused on another input of the same physical panel.

There is a temptation, once EDID is understood, to override it: to force a mode the panel's EDID does not list, using a driver custom-resolution feature or an EDID override tool. That temptation should be resisted unless the exact timing is known to be within the panel's real limits, because it removes the one guard that normally prevents rejected modes. An override that forces a timing the scaler cannot handle produces exactly the message this guide addresses, and it can do so in a way that persists across restarts, because the forced mode is now part of the driver's stored configuration rather than a one-off choice. If a rejected mode appeared after an EDID override or a custom mode was created, that override is the prime suspect, and removing it is the remedy, not creating a further override to compensate.

Driver Custom Modes: The Most Common Self-Inflicted Cause

Graphics drivers offer a custom resolution feature for legitimate reasons: a panel whose EDID is incomplete, a professional workflow that needs an unusual timing, or a display whose native timing is not in the standard list. The feature allows a mode to be constructed by hand: resolution, refresh rate, and timing parameters entered directly, or computed from a timing standard such as CVT (Coordinated Video Timings) or GTF (Generalized Timing Formula). These standards are recipes for computing blanking intervals and pixel clocks from a resolution and refresh rate, and different recipes produce different timings for the same headline numbers.

The risk is that a custom mode bypasses the EDID guard described above. The driver will offer, and send, a mode that the panel never claimed to accept. If the panel's scaler accepts it, the result is a working picture and the user may never know the mode was custom. If the scaler refuses it, the result is the rejection message, and the user may not remember that the mode was custom, because the settings list now shows it alongside standard modes with nothing to distinguish it.

Custom modes also create a persistence trap. A custom mode that is set as the active desktop mode remains the active mode across restarts, so the rejection message can greet the user at every boot, including before the login screen, which makes the machine look as though it has failed entirely. In reality the machine is almost certainly running normally behind the message; it is simply sending a mode the panel refuses, and the user cannot see the desktop to change it. That is precisely the situation the rescue steps below are designed for: getting back to a standard, accepted mode by a route that does not require seeing the rejected desktop.

A related trap is the per-game mode. Many games store their own resolution and refresh settings independently of the desktop. A game that was configured on a different monitor, or configured with a custom mode, can launch into a timing the current panel refuses, even though the desktop itself is fine. The symptom pattern identifies this case clearly: the desktop is visible, the game launches, the screen goes to the rejection message, and quitting or switching away from the game restores the desktop. The desktop mode is innocent; the game's stored mode is the suspect, and the fix belongs in the game's settings or configuration, reached by one of the rescue routes below.

Ordered Diagnostic Flow

Work through these steps in order. The order matters: the early steps restore a visible picture with the least disruption, and the later steps identify which link chose the rejected mode, so that the rescue does not have to be repeated.

  1. Read the exact message and note when it appears. Write down the exact wording, and whether it appears at boot, at the login screen, on the desktop, only when a particular game or application launches, or only on one monitor of a multi-monitor setup. The timing of the message is the first discriminator: a message at boot points to the stored desktop mode, a message only in one game points to that game's stored mode, and a message on one monitor only points to that monitor's assigned mode. Do not skip this note-taking; later steps depend on it.
  2. If a second monitor is available and working, use it. On a multi-monitor system where one display shows the rejection message and another shows the desktop, open the display settings on the working display and change the affected monitor's mode to a lower, standard one — for example, its native resolution at a standard refresh rate, or, if the native mode is itself the suspect, a clearly standard mode such as 1920 × 1080 at 60Hz. If the picture returns, the diagnosis is confirmed: the previous mode was rejected, and the remaining question is only which link chose it. If no second monitor is available, continue to the next step.
  3. Use the low-resolution rescue route. When no display shows a usable picture, the operating system provides a recovery route that starts the display in a minimal, standard mode. On Windows this is reached through the recovery environment: restart into recovery, open the startup settings, and choose the low-resolution video option, which starts the system at a basic resolution and refresh rate that essentially every panel accepts. From that visible desktop, open display settings and set a standard mode, then restart normally. The purpose of this step is only to regain visibility; it is not a permanent configuration, and the mode set from the rescue desktop should be a standard one, not a recreation of the rejected custom timing.
  4. Once a picture is visible, test the single-monitor configuration. Disconnect all displays except the affected one, connect it directly to the computer with a single cable, bypassing any dock, adapter, switch, or splitter, and set a standard mode. If the picture holds on a direct connection, the reporting chain — the dock, adapter, or switch — is the suspect, and the EDID discussion above applies. If the picture is still rejected on a direct connection with a standard mode, the suspect narrows to the stored mode, the driver state, or the panel's own limits, and the next steps apply.
  5. Step up one variable at a time. From the recommended mode, confirm stability first, then change one variable at a time: the resolution first, or the refresh rate first, never both together. After each change, watch for the system's confirmation countdown and only keep the change once the picture is confirmed normal. If a step is refused immediately, that step is the boundary: record it, return to the previous stable mode, and do not keep retrying at the boundary.
  6. Remove custom modes and EDID overrides. Open the graphics driver's control panel and inspect the custom resolution list. If any custom mode exists, especially one matching the rejected resolution and refresh rate, delete it, and remove any EDID override that was applied. Then set a standard mode from the ordinary settings list and restart. If the rejection disappears after this step, the custom mode or override was the cause. Do not recreate the custom mode to "test" it unless the panel's real limits are known from its own documentation; recreating it will simply reproduce the message.
  7. Check the monitor's own information page. Most monitors have an information page in their own menu, showing the mode they are currently receiving. If the monitor shows a mode outside its accepted range, that confirms the refusal story. Compare it with the panel's accepted modes, which are listed in the monitor's own specifications. The comparison is the diagnosis: the sent mode against the accepted list. If the sent mode is on the accepted list and still refused, that is a different and rarer situation, and it is time to stop guessing.
  8. Test the cable and the input. Try a different cable of the same type, and try a different input on the monitor if one is available. A cable or input that corrupts EDID can produce a wrong mode list and a rejected mode, and this step is cheap relative to the confusion it resolves. Note the result carefully: if the mode list changes when the cable or input changes, the reporting chain was contributing, even if the picture itself seemed to be the problem.
  9. Test the game or application separately, if the message appears only there. Launch the game in a windowed mode if its launcher or settings allow it, or reset its display settings from its configuration or launcher options, and set its resolution and refresh rate to a standard mode that matches the desktop. If the game then displays normally, its stored mode was the cause. Be aware that some games apply their stored mode at launch before any menu is visible, so a windowed launch or a configuration reset may be the only way to reach the settings.
  10. Check the driver state. If the rejection began immediately after a driver update, a driver settings change, or a monitor being re-detected, treat driver state as a suspect. Reset the driver's display configuration to defaults, or reinstall the driver cleanly so that stored custom modes and overrides are removed, and retest with a standard mode. A rejection that clears after a clean driver state, and does not return when only standard modes are used, points to stored driver configuration rather than to the panel or the cable.
  11. Test persistence and isolate the panel. Repeat the rejected mode deliberately, once, from a standard settings list, and note whether the rejection is consistent: the same mode, refused every time, on a direct connection, with a standard cable. A consistent refusal of a standard mode on a direct connection, after custom modes and overrides are removed and driver state is reset, is the pattern that points toward the panel's own scaler limits or a panel-side fault, and it is the pattern worth recording before seeking inspection. An inconsistent refusal — refused sometimes, accepted other times, or dependent on which adapter is in the chain — points away from the panel and back toward the reporting chain or driver state.
  12. Record before seeking inspection. Note the exact message wording, the exact mode that is refused (resolution, refresh rate, and whether it was a custom mode), the mode that works, the step at which refusal begins, the mode shown on the monitor's information page, the cable type and whether a dock, adapter, or switch is in the chain, whether the rejection appears at boot, on the desktop, or only in one game, and what changed just before the problem began (driver update, monitor change, custom mode creation, new adapter). These notes determine which layer an inspector tests first, and they prevent the inspection from starting over from the beginning.

Triage Table

Symptom patternMost likely layerOne discriminating testWhere to look next
Rejection message at boot and on the desktop, no picture at allStored desktop mode is a rejected custom or carried-over modeLow-resolution rescue route restores a pictureDelete custom modes and overrides, then set a standard mode
Rejection message only when one game launches, desktop is fineThat game's stored resolution or refresh settingWindowed launch or configuration reset lets the game displayGame display settings, set to a standard mode matching the desktop
Rejection message on one monitor only, other monitor fineMode assigned to that monitor, or its reporting chainChange that monitor's mode from the working displaySingle-monitor direct-connection test, then cable and input
Rejection appears only through a dock, adapter, or switchEDID reporting through that deviceDirect connection with a single cable: picture returnsAdapter, dock, or switch EDID handling; try another cable or input
Mode list looks wrong: native resolution missing, or odd modes offeredEDID not read correctly, or substituted by an adapterDirect connection changes the offered mode listCable, input, adapter, then driver state
Rejection began right after a driver update or settings changeStored driver configuration or a new custom modeClean driver reset with standard modes only: rejection clearsDo not recreate the custom mode without the panel's documented limits
Same standard mode refused every time on a direct connectionPanel scaler limits or a panel-side faultPersistence test after custom modes removed and driver resetNotes from step 12, then inspection
Rejection only on one input of the same monitorThat input's scaler limits or EDID dataAnother input accepts the same modeUse the accepting input, or a mode that input accepts

Boundary Cases

A monitor that shows the rejection message only during startup, before the operating system loads, deserves separate handling. The startup screens use a basic mode chosen by the firmware, and a rejection at that stage, followed by a normal desktop once the operating system loads, points to the firmware's chosen mode rather than to any desktop setting. The rescue route still applies if the desktop never appears, but a rejection confined to the startup screens, with a normal desktop afterwards, is a different pattern from a rejected desktop mode and should not be chased through desktop settings.

In the older analogue-signal era, out-of-range messages were often about sync frequencies; in the current digital-signal era timing problems remain, but their presentation and causes differ, so old experience should not be applied directly to new interfaces.

Some monitors show the currently received frequency figure alongside the rejection message. That figure is useful — recording it helps judge which parameter is over the limit — but different brands display it differently, and the absence of a figure does not mean the problem is different.

Projectors and televisions follow the same scaler logic but with their own limits, and a mode accepted by a computer monitor can be refused by a television or projector, and vice versa. Television inputs in particular may accept a mode only on certain inputs, or may apply their own processing that changes the effective timing. When a television is involved, the television-specific input limits and its own picture settings belong in the investigation alongside the computer's mode list, and a mode that works on a monitor is not evidence that it should work on the television.

In a multi-monitor environment, one monitor refusing while another displays normally does not mean the refusing monitor is necessarily faulty. The system may apply the same mode to two panels of different capabilities, and the less capable panel refuses while the more capable one displays normally. The correct approach is to set each monitor's mode separately, not to treat the two monitors as having the same capability.

A docking station that worked for months and then begins producing rejected modes is not necessarily failing. Dock firmware updates, driver updates, and a change of cable can each alter the EDID chain, and the investigation should ask what changed in the chain before concluding that the dock itself has failed. The direct-connection test in step 4 exists precisely for this situation: it separates the dock's contribution from the panel's and the computer's.

High refresh rate panels deserve a note about expectations. A panel advertised with a high maximum refresh rate may only sustain that rate at certain resolutions, over certain inputs, or with certain timing variants. A mode that pairs the maximum resolution with the maximum refresh rate is therefore not automatically valid, even though both numbers appear in the panel's description. The valid combinations are the ones the panel's EDID lists and its scaler accepts, and the test is always the panel's actual response, not the combination of two headline numbers.

A virtual machine or remote desktop environment is different again: the display mode is decided by the virtual display driver, not directly by a physical panel, so the causes of a rejection message differ from those for a local physical monitor, and this guide's flow should not be applied directly to a virtual environment.

Finally, a word about persistence across restarts. A rejected mode that returns at every boot is not evidence that the panel has deteriorated. It is evidence that the rejected mode is stored somewhere — in the desktop configuration, in the driver's custom mode list, or in a game's settings — and is being re-sent at every start. The rescue route plus the deletion of the stored mode breaks that loop. If the loop is not broken, every restart will reproduce the same message, however healthy the panel is.

A laptop whose own screen is fine but whose external monitor refuses follows the same logic. The internal panel working proves the graphics system can produce a picture. The external refusal is about the external mode or the external connection path, not about the laptop as a whole.

Misconceptions Rebutted

An "out of range" message does not mean the monitor is broken. It means the panel received a signal and refused its timing. A broken panel more commonly shows no picture at all, a distorted picture, or a persistent fault across all modes and inputs. A panel that displays a crisp rejection message is demonstrating that its scaler, its on-screen display, and its input detection are all working; what it is refusing is one particular timing.

An "out of range" message does not mean the graphics card has failed. A failed graphics output more commonly produces no signal at all, or artefacts across every mode. A graphics output that can send a signal the panel recognises well enough to refuse by name is communicating. The fault, if any, is in which mode was chosen, not in the ability to send a signal.

A higher resolution or refresh rate is not automatically better, and selecting the highest numbers in the list is not a safe default. The only safe default is a mode the panel's EDID lists and its scaler accepts. Choosing the maximum values without checking whether that combination is valid for this panel is one of the fastest routes to the rejection message, especially when the maximum resolution and maximum refresh rate cannot be combined.

A new cable will not fix a rejected custom mode. A cable can fix a corrupted EDID chain, and step 8 tests for that, but if the rejected mode is stored in the driver or in a game, no cable change will alter it, because the same stored mode will be sent over the new cable. Cable and stored mode must be separated before spending on either.

Deleting the driver will not, by itself, fix a rejected mode stored in a game's configuration. Driver state and game settings are separate stores. A clean driver reset addresses the driver's store; a game's stored mode must be reset through the game. When the rejection appears only in one game, the driver is the wrong place to look, however tempting a reinstall may be.

A mode that worked on a previous monitor does not prove it should work on this one. Panels differ in scaler limits, accepted timings, and input handling, and the previous monitor's acceptance is no evidence about the current panel. Each panel must be judged by its own EDID and its own response.

The low-resolution rescue route is not a repair in itself. It restores visibility so that a standard mode can be set. If the rejected mode is left stored and the machine is simply restarted, the message will return. The rescue is complete only when a standard, accepted mode has been set and the rejected custom mode or override has been removed.

What to Note Before Seeking Inspection

If the rejection persists through the flow — the same standard mode refused every time, on a direct connection, with a standard cable, after custom modes and overrides are removed and driver state is reset — then an inspection is reasonable. Before seeking one, note the exact message wording, the exact refused mode, the mode that does work, the cable and input used, whether a dock, adapter, or switch is in the chain, whether the rejection appears at boot, on the desktop, or only in one game, and what changed just before the problem began. A consistent refusal under those controlled conditions is the pattern that points toward the panel's own limits or a panel-side fault, and it is the pattern an inspector needs to see first.

HK GPU Fix is at Room 1209, Dali Plaza, Shek Mun. The telephone number is 2186 8010 and WhatsApp is 6558 6806. There is no Mong Kok shop and no door-to-door service. Any inspection is subject to a written quotation after inspection, within the site's published three-tier range of HK$400–2,800. Do not assume a failed panel before inspection: the flow above separates a stored custom mode, a reporting-chain fault, a game setting, and a driver state problem from a persistent panel-side refusal, and only the last of those points toward inspection.

FAQ

What does "out of range" actually mean?

It means the monitor received a signal but refused its timing. The resolution, refresh rate, or timing variant falls outside what that panel's scaler accepts. It is different from "no signal", which means nothing recognisable is arriving at all.

Why does the message appear on this monitor but not my previous one?

Because panels differ in scaler limits and accepted timings. A mode one panel accepts can be refused by another, even when the computer and cable are unchanged. A mode is supported by a particular panel, never in the abstract.

I cannot see anything to change the setting. How do I get a picture back?

Use the low-resolution rescue route: restart into the recovery environment, open the startup settings, and choose the low-resolution video option. That starts the system in a basic mode nearly every panel accepts. From there, set a standard mode and restart normally, and remove any custom mode that caused the rejection.

Could a dock, adapter, or switch be causing this?

Yes. Those devices sit in the EDID reporting chain, and if they corrupt, block, or substitute the panel's EDID data, the driver can offer modes the real panel does not accept. Connect the monitor directly with a single cable: if the picture returns, the device in the chain is the suspect.

The desktop is fine, but one game shows "out of range" when it launches. Is my graphics card failing?

Almost certainly not on that evidence. The game's own stored resolution or refresh setting is the suspect, not the desktop mode and not the hardware. Launch the game windowed if possible, or reset its display settings, and set a standard mode that matches the desktop.

Should I create a custom resolution to force the mode I want?

Only if the exact timing is known to be within the panel's real limits from its own documentation. A custom mode bypasses the EDID guard that normally prevents rejected modes, and a forced timing the scaler cannot handle produces exactly this message, persistently, across restarts.

The highest resolution and highest refresh rate are both listed. Why is their combination refused?

Because the maximum resolution and the maximum refresh rate may not be combinable on that panel, or only over certain inputs or with certain timing variants. The valid combinations are the ones the panel's EDID lists and its scaler accepts, not the pairing of two headline numbers.

When should I seek inspection instead of continuing to adjust settings?

When the same standard mode is refused every time on a direct connection with a standard cable, after custom modes and overrides are removed and driver state is reset. That consistent pattern, recorded with the exact refused mode and the mode that works, is what points toward the panel's own limits or a panel-side fault.

Related articles

Related services

If you need Chip-level GPU repair, see these service pages: