Overscan, Underscan, and Garbled Images: Fixing Display Geometry Problems

Overscan is a display condition where the edges of the video image extend beyond the visible screen area, so content near the borders — taskbars, window edges, tickers — appears cut off. It shows up most often when an HDTV is used as a computer monitor, because televisions inherit a broadcast-era habit of enlarging the picture slightly past the panel’s edges. Its opposite, underscan, shrinks the image inside the panel and leaves a black border all the way around. Both are geometry problems fixed with scaling settings — on the TV, in the graphics driver, or both — not with new hardware.

What overscan is and why TVs still do it

In the analog broadcast era, the outer fringe of a transmitted picture often carried noise, timing artifacts, and ragged edges. Television makers solved this cosmetically: zoom the image a few percent so the messy border lands past the edge of the glass where nobody sees it. Viewers lost roughly 3–5% of the picture on every side and never noticed, because TV content kept anything important inside a “safe area.”

Digital signals made the practice obsolete, but many HDTVs still overscan by default for compatibility. That’s harmless for movies and irrelevant for broadcasts — and immediately obvious the moment a computer desktop appears, because desktops put critical pixels exactly where overscan crops: the taskbar along the bottom, the menu bar along the top, close buttons in corners. The symptom reads as “the edges of my screen are cut off” or “I can’t see my taskbar on the TV.”

The fix lives primarily in the TV’s own picture menu. Look for the aspect or picture-size setting and choose the mode that maps the input pixel-for-pixel — vendors name it Just Scan, Screen Fit, 1:1, Dot by Dot, or simply an “overscan off” toggle, often labeled per-input. Secondarily, the GPU (graphics processing unit) driver utility (NVIDIA Control Panel, AMD Software, Intel Graphics Command Center) offers an overscan/underscan compensation slider that resizes the output to fit the visible area when the TV lacks a proper setting.

Underscan: the black border problem

Underscan is the mirror image: the rendered picture is smaller than the panel, so the desktop floats inside a black frame and doesn’t fill the screen. You’ll meet it when a laptop drives an HDTV over HDMI and either the TV’s scaling mode letterboxes the input or the graphics driver has overscan compensation applied (shrinking the output to dodge overscan that isn’t actually happening), or the output resolution simply doesn’t match the panel’s native resolution.

Two fixes cover it, and they’re the pair worth remembering together:

1. On the TV: set the picture/aspect mode to the pixel-perfect option (Just Scan / Screen Fit / 1:1) so the panel displays the input without shrinking or enlarging it.
2. In the graphics driver: open the GPU control panel’s scaling controls and adjust the underscan/overscan slider until the desktop edges meet the screen edges, with the output resolution set to the TV’s native resolution (typically 1920×1080 or 3840×2160).

Neither fix involves cables or hardware — a black border is a scaling disagreement, and either end of the link can concede. (If the TV shows no picture at all rather than a bordered one, that’s a different problem — start with input sources and no-signal checks.)

Overscan vs underscan at a glance

Attribute	Overscan	Underscan
What you see	Image edges cut off past the visible screen	Black border surrounding a shrunken image
Image vs panel	Picture larger than the visible area	Picture smaller than the visible area
Classic trigger	HDTV’s broadcast-legacy zoom applied to a PC input	Scaling compensation or non-native resolution over HDMI
Primary fix	TV picture mode: Just Scan / Screen Fit / 1:1	Same pixel-perfect TV mode
Secondary fix	GPU driver overscan compensation slider	GPU driver scaling slider + native resolution
Hardware fault?	No — settings only	No — settings only

Garbled image after picking an unsupported mode

A different geometry failure: a user manually forces a resolution and refresh rate combination the monitor can’t properly handle, and the screen turns into a distorted, garbled mess with horizontal lines — sometimes with the monitor flashing an “input not supported” warning, sometimes just chaos. The display hardware isn’t damaged; it’s being fed timing it cannot synchronize with.

Two valid recovery paths, and exam questions like to ask for both:

• Wait out the revert timer. Windows displays a confirmation dialog after a mode change and automatically rolls back to the previous settings after roughly 15 seconds with no response. If the change just happened, simply not touching anything restores the working mode.
• Boot into a low-resolution fallback and reconfigure. If the bad mode stuck, boot into Safe Mode or use Windows’ low-resolution video option from the recovery/startup settings menu. These start the display in a basic mode every monitor accepts; from there, set a resolution and refresh rate the monitor’s specifications actually support (its native resolution and a listed rate such as 60 Hz), then reboot normally.

What doesn’t fix it: replacing the cable or monitor, reinstalling the OS, or repeatedly power-cycling while the invalid mode persists. The signal is wrong, so the settings must change. If the symptom is rhythmic flashing rather than a scrambled image, work the monitor flickering diagnostic tree instead — refresh-rate trouble sits at the junction of both problems.

Blurry text on VGA at the wrong resolution

One more geometry-adjacent classic: a VGA-connected monitor shows blurry, fuzzy text even though cable and connections are fine, and the resolution is set higher than the monitor’s specifications recommend. VGA is analog, so there’s no hard failure when the mode is wrong — the monitor gamely stretches or resamples whatever arrives, and every pixel lands slightly smeared. LCD panels compound this: they have exactly one native resolution where each signal pixel maps to one physical pixel, and any other setting forces interpolation that softens text most of all.

The correct action is to set the resolution back to the monitor’s recommended/native specification — not to replace a cable that’s already known-good, and not to crank sharpness controls that only mask the mismatch. Sharp text returns the moment the source resolution matches what the panel was built to show. Native resolution is one of the core panel attributes covered in what monitor specifications actually mean.

How the 220-1201 exam tests this

• Term identification: a description of image edges extending past the visible screen and getting cut off, typically on an HDTV used as a monitor — the answer is overscan. Know underscan, letterboxing, and dead pixels as distractor concepts.
• Choose-two fixes for a black border: laptop-to-HDTV over HDMI with the desktop not filling the screen. The credited pair: change the TV’s picture/aspect mode to the pixel-perfect setting, and adjust scaling (or set native resolution) in the GPU driver. Cable swaps and OS reinstalls are the decoys.
• Choose-two recovery paths from a garbled mode: after an unsupported resolution/refresh combination is applied, valid fixes are letting the automatic revert restore prior settings and booting into Safe Mode or low-resolution video mode to select a supported combination.
• Wrong-resolution blur: fuzzy VGA text with good cabling and an above-spec resolution → set the recommended/native resolution. The exam wants you to resist blaming healthy hardware.

Like most display troubleshooting, these items land in the exam’s heaviest domain — the 220-1201 study guide shows how the domains weight out. Choose-two items punish half-remembered pairs — the A+ Core 1 question bank is the place to rehearse them.

Quick reference

• Overscan = image larger than the visible screen, edges cut off; a broadcast-era TV behavior that mangles PC desktops.
• Underscan = image smaller than the screen, black border all around; a scaling/resolution mismatch.
• First stop for both: the TV’s pixel-perfect picture mode — Just Scan, Screen Fit, 1:1, or Dot by Dot.
• Second stop: the GPU driver’s overscan/underscan scaling slider, with output at the display’s native resolution.
• Garbled screen with horizontal lines after a manual mode change = unsupported resolution/refresh combination, not broken hardware.
• Recover via Windows’ ~15-second automatic settings revert, or Safe Mode / low-resolution video mode, then apply a supported mode.
• Blurry VGA text at above-spec resolution → return to the monitor’s recommended/native resolution.
• Geometry problems are settings problems; replace hardware only after configuration is proven correct.