Monitor Keeps Going Black for a Second Then Comes Back: The Definitive Fix Guide (2026)

Your computer monitor briefly goes black for a second and then returns to normal. The power LED stays on. Everything seems fine — until it happens again 10 minutes later. Or 2 minutes. Or every 30 seconds during a game.

This is one of the most common and most frustrating display problems in PC troubleshooting. The most frequent cause is a faulty or inadequate display cable — replacing it with a VESA-certified cable resolves roughly 30% of all cases based on confirmed fixes across thousands of forum threads. But this problem has over two dozen distinct causes spanning cables, GPU drivers, monitor firmware, power delivery, adaptive sync, Windows settings, electromagnetic interference, and even your office chair.

Most troubleshooting guides cover only surface-level fixes. This guide covers everything — including the obscure methods that actually work when nothing else does.

How to Diagnose the Cause Before Trying Random Fixes

The single most important step is determining what category of problem you’re dealing with. A brief blackout can come from four fundamentally different sources, and the fix differs for each one.

Watch the Power LED During the Blackout

This is the fastest diagnostic you can do:

LED turns amber/orange: The monitor lost the input signal. Points to a cable, GPU, or handshake issue.
LED stays green but screen goes dark: The GPU is still sending a signal but something internal (driver crash, monitor processing glitch) interrupted the display.
LED turns off entirely: The monitor itself lost power momentarily — a hardware problem like failing capacitors or an insufficient power adapter.

Try Opening the Monitor’s OSD Menu During the Blackout

Press the physical menu button on the monitor the instant the screen goes dark. If the OSD (On-Screen Display) appears over the black screen, the backlight works and the issue is signal loss from the computer side. If the OSD doesn’t appear, the problem is inside the monitor — its power board, backlight driver, or T-Con board.

Check Windows Event Viewer

This is the diagnostic step most people skip, and it’s the most revealing. Open eventvwr.msc immediately after a blackout. Navigate to Windows Logs → System and look for Event ID 4101 from source “Display.”

If you see “Display driver stopped responding and has successfully recovered” timestamped at the moment of the blackout, you’ve confirmed a TDR (Timeout Detection and Recovery) event — the GPU driver crashed and Windows recovered it. The source name reveals your GPU vendor:

nvlddmkm = NVIDIA
atikmpag or atikmdag = AMD
igdkmd64 = Intel

If no Event ID 4101 appears during blackouts, the GPU driver didn’t crash. The problem lies elsewhere — cable, monitor, power, or signal negotiation.

Monitor GPU Behavior with HWiNFO64

For intermittent blackouts that are hard to reproduce, enable sensor logging at 500ms intervals in HWiNFO64 and go about your normal use. After a blackout, check the log for:

GPU core clock drops (e.g., from 1800 MHz to 210 MHz during active use)
Temperature spikes above 90°C before the event
Power draw hitting the TDP limit
“Performance Limit” flags showing thermal/power/voltage throttling

Clock drops correlate with driver resets. Temperature spikes indicate thermal throttling is causing signal loss.

Run Your Monitor’s Built-in Self-Test

Disconnect all video cables from the monitor. Most monitors enter a self-test mode automatically:

Dell: Cycles through solid color screens (gray, red, green, blue, black, white)
Samsung: Access via Support → Self Diagnosis in the OSD
Other brands: Check your manual for “BIST” (Built-In Self-Test)

If the monitor flickers or blacks out during self-test with no cable connected, the monitor hardware is defective.

Fix 1: Replace Your Display Cable (Fixes ~30% of Cases)

A bad cable is the number-one confirmed fix across all major tech forums. This isn’t just “make sure the cable is plugged in” advice — cable quality matters enormously at modern bandwidth demands.

Why DisplayPort Cables Fail More Than HDMI

DisplayPort 1.4 HBR3 runs at 32.4 Gbps across four lanes, demanding exceptional signal integrity. Passive DP cables are reliable only up to about 2 meters at high bandwidth. Beyond that length, cables become antennas for electromagnetic interference.

One user documented blackouts correlating precisely with a space heater cycling, a printer powering on, and a phone charger being plugged in — all picked up by a 20-foot DP cable running 4K at 144Hz with 10-bit color. Switching to a 3-foot cable eliminated every blackout.

The DisplayPort Pin 20 Defect

Pin 20 (DP_PWR) should not connect source to sink power, but VESA found a high number of non-certified cables are improperly wired, creating a short circuit condition that causes intermittent blackouts and can even damage GPUs. Only VESA-certified cables guarantee correct pin configuration.

What to Buy

DisplayPort: Look for “VESA Certified” or “DP8K Certified” cables. Keep length under 2 meters for high refresh rates.
HDMI: Look for “Premium High Speed HDMI Certified” (HDMI 2.0) or “Ultra High Speed HDMI Certified” (HDMI 2.1).
Budget: $10–15 for a quality certified cable. This is the highest-value troubleshooting purchase you can make.

Don’t Forget Adapters

Passive DP-to-HDMI adapters cap out at 4K30 and cause blackouts at higher refresh rates. Active adapters contain conversion chips with their own firmware bugs. Dell officially acknowledged that DP-to-HDMI dongles cause black screens when resuming from sleep. Most DP-to-HDMI cables are also unidirectional — connecting them backwards produces no signal at all.

The PCIe Riser Cable Trap

If your GPU is vertically mounted with a riser cable, this is a prime suspect. Gen 4 GPUs in Gen 3 riser cables fail because the motherboard auto-negotiates Gen 4 speed that the riser can’t sustain. The fix is forcing PCIe Gen 3 in BIOS — but you may need to temporarily install the GPU directly to access BIOS settings.

Fix 2: Disable Multiplane Overlay (The 30-Second Registry Fix Nobody Talks About)

Multiplane Overlay (MPO) is a Windows compositor feature that causes flickering and blackouts on both AMD and NVIDIA systems. NVIDIA officially published this fix, and it has 10–15 confirmed success reports across guru3D, Reddit, and Neowin — making it one of the highest-impact obscure fixes for this problem.

How to disable it:

Press Win + R, type regedit, press Enter
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm
Right-click → New → DWORD (32-bit) Value
Name it OverlayTestMode
Set the value to 5
Reboot

That’s it. This single registry edit has resolved persistent blackouts that survived cable swaps, driver reinstalls, and even GPU replacements.

Fix 3: Address GPU Driver Crashes (The Real Cause Behind Most “Random” Blackouts)

Understanding TDR Events

When the GPU fails to complete an operation within 2 seconds (the default timeout), Windows kills the display driver, resets the GPU, and restarts the driver. This produces a black screen lasting 1–5 seconds followed by recovery. If recovery fails, you get a blue screen with stop code VIDEO_TDR_FAILURE.

NVIDIA-Specific Issues

NVIDIA’s 572.x driver branch (launched early 2025 with RTX 50 series) caused widespread black screen issues across RTX 30, 40, and 50 series GPUs. Game developers publicly recommended rolling back to driver 566.36. NVIDIA released multiple hotfixes, with 572.65 specifically fixing DisplayPort boot blackouts with certain monitors.

What to do: If you’re on an NVIDIA GPU experiencing blackouts, try rolling back to the last known-stable driver for your card generation. Check NVIDIA’s release notes — they document known monitor compatibility issues.

AMD-Specific Issues

AMD driver timeouts are frequently triggered by GPU power state transitions — specifically when the GPU switches from low-power to high-power states (launching a game, starting a video). AMD Adrenalin drivers 22.7.1+ caused hardware acceleration conflicts with Chrome and Discord. Driver 22.5.1 is widely regarded as a stability baseline for older AMD cards. AMD also acknowledged that their Enhanced Sync feature causes intermittent black screens during gameplay and video playback — disable it in Adrenalin settings.

Intel Arc-Specific Issues

Intel Arc has the most immature driver stack. Intel officially acknowledges black screen issues and recommends driver version 31.0.101.4502 or newer. Reducing refresh rate from 144Hz to 120Hz resolved blackouts for some Arc users. The Arc B580 has a documented bug where BIOS Legacy mode re-enables on warm boot, causing display loss.

The Proper DDU Clean Install

A regular driver update installs over old files. A DDU clean install removes everything first:

Download the target GPU driver and DDU (Display Driver Uninstaller)
Disconnect from the internet (prevents Windows auto-installing generic drivers)
Boot into Safe Mode
Run DDU — select options to remove vendor folders, PhysX, and Vulkan RT
Click “Clean and Restart”
After rebooting into normal Windows, install the downloaded driver
Reconnect the internet

Important: After DDU, DisplayPort may fail to handshake with the basic display adapter. Temporarily switch to HDMI, or press Win + Ctrl + Shift + B to force a graphics driver restart.

Disable Hardware Acceleration in Problem Apps

Chrome, Discord, Spotify, OBS, and Teams all offload rendering to the GPU, and buggy implementations cause driver conflicts. AMD systems are particularly susceptible. Quick diagnostic test:

Chrome: Settings → System → uncheck “Use graphics acceleration when available”
Discord: Settings → Appearance → Hardware Acceleration → off
Edge/Firefox: Similar settings in their respective menus

If blackouts stop after disabling hardware acceleration in a specific app, you’ve found your trigger.

Fix 4: Tame Power Management Settings

PCI Express Link State Power Management

This is one of the most impactful hidden causes. Windows transitions the PCIe link between active, standby, and fully off states to save power. Waking from the off state takes up to 64 microseconds, and if the transition fails, the display drops.

To disable: Control Panel → Power Options → Change plan settings → Change advanced power settings → PCI Express → Link State Power Management → Off

Multiple users report that changing this single setting permanently resolved their blackouts, especially blackouts occurring at idle or low GPU load.

GPU Power Management Mode

NVIDIA Control Panel defaults to “Optimal Power,” which aggressively downclocks the GPU during low-load states. When load suddenly increases, the GPU must ramp back up, causing a brief signal renegotiation — black screen for 1–2 seconds.

Fix: NVIDIA Control Panel → Manage 3D Settings → Power Management Mode → Prefer Maximum Performance

ASUS’s official FAQ lists this as Fix Method 1 for gaming blackouts on their PG, XG, and VG monitor series.

Windows Fast Startup

Fast Startup preserves driver states from the previous session. Corrupted GPU driver states carry over, causing blackouts that don’t occur after a full restart.

To disable: Control Panel → Power Options → “Choose what the power buttons do” → Uncheck “Turn on fast startup”

The Ultimate Performance Power Plan

This bundles all power fixes into one setting. Open an elevated command prompt and run:

powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61

Then select “Ultimate Performance” in Power Options. It disables Link State Power Management, USB selective suspend, and prevents processor throttling.

Fix 5: Adjust Adaptive Sync Settings (G-Sync / FreeSync / VRR)

Why Adaptive Sync Causes Blackouts

When the frame rate drops below the monitor’s VRR minimum, the display transitions to Low Framerate Compensation (LFC). If this transition isn’t smooth, a black frame flashes. G-Sync Compatible monitors (FreeSync panels running NVIDIA G-Sync) are disproportionately affected because LFC behavior doesn’t always match the monitor’s FreeSync range.

Quick Fixes

Disable G-Sync/FreeSync entirely as a test. If blackouts stop, adaptive sync is the cause.
Set G-Sync to “Full Screen Only” instead of “Windowed and Full Screen” in NVIDIA Control Panel. In windowed mode, the Windows compositor fights with G-Sync for control of frame timing.
Use a frame rate limiter (RTSS or in-game) to cap FPS 3–5 frames below your monitor’s maximum refresh rate. This prevents the GPU from hitting the ceiling where VRR edge-case bugs live.

The CRU Fix (Advanced but Highly Effective)

Custom Resolution Utility (CRU) lets you adjust your monitor’s VRR range. This is confirmed effective by 20+ users across forums:

Raise the minimum (e.g., 48Hz → 55Hz) to prevent low-FPS blackouts
Lower the maximum by 1–3Hz (e.g., 144Hz → 141Hz) to eliminate edge-case instabilities

Several users confirmed that reducing maximum refresh rate by just 1Hz via CRU stopped their blackouts entirely.

OLED and VA Panel Users

These panel technologies produce different brightness levels at different refresh rates. When VRR dynamically adjusts, brightness shifts create visible flicker in dark scenes. ASUS officially acknowledges this as inherent to OLED VRR technology. Mitigations include limiting the VRR range to a narrow window (e.g., 90–144Hz instead of 48–144Hz).

Fix 6: Monitor OSD Settings Most People Never Check

DisplayPort Deep Sleep

This monitor-level power saving feature fully disconnects the monitor from the GPU’s perspective when entering standby. Brief deep sleep events cause momentary blackouts.

Fix: In your monitor’s OSD, look under System, Power, Setup, or General for “DP Deep Sleep” or “Deep Sleep Mode” and disable it. The power savings are negligible (fractions of a watt).

Dell monitors are the most frequently affected — the S2721DGF, U2723QE, and P2715Q all have well-documented deep sleep wake failures.

Change the DisplayPort Version

This high-impact fix solves problems no other fix can. Multiple Dell monitor users resolved persistent blackouts by switching from DP 1.2 to DP 1.1 in the OSD. The trade-off is reduced maximum bandwidth, but for 1080p or 1440p at moderate refresh rates, it’s sufficient and rock-stable.

Conversely, some monitors work better after switching to DP 1.4 from 1.2, since DP 1.4 adds Forward Error Correction that can stabilize marginal links.

Auto Source Select / DP Auto Switch

This feature periodically scans all input ports for active signals, triggering unnecessary link renegotiations that cause 2–5 second blackouts every few minutes. Disable it in the OSD. One BenQ user described it as resolving months of failed troubleshooting.

DDC/CI

Applications like Twinkle Tray, Dell Display Manager, f.lux, and ClickMonitorDDC send DDC/CI commands that trigger brief re-handshakes or even put monitors into unrecoverable deep sleep. Disabling DDC/CI in the monitor OSD eliminates this. The trade-off is losing software brightness control.

Fix 7: Update Monitor Firmware (The Fix Nobody Knows Exists)

Monitor firmware updates fix bugs that no other troubleshooting can address — and most users never update their monitor firmware because they don’t know it’s possible.

Real examples:

ASUS PG32UCDM: White artifacts and signal loss from firmware MCM101 through MCM106, completely fixed in firmware MCM110
Samsung Odyssey G7: Firmware update specifically targeting DisplayPort flickering
Dell docking stations (WD19, WD22TB4): Intermittent blanking caused by Display Stream Compression bugs, fixed in dock firmware 01.00.36

How to update:

Dell: Download utility from dell.com/support for your model. Connect via USB upstream cable.
LG: Use the OnScreen Control software to check and install updates.
Samsung: Check samsung.com/support for your model number.
ASUS: Use VLI FW Update Tool from their support page.

Fix 8: Reduce Bandwidth Demands on a Marginal Connection

Color Depth

Switching from 10-bit to 8-bit color reduces bandwidth by 25%. At 3840×2160 at 144Hz, 10-bit RGB requires approximately 35.8 Gbps — exceeding DP 1.4’s 25.9 Gbps and requiring Display Stream Compression. If DSC isn’t working correctly, the link is unstable.

To change: NVIDIA Control Panel → Change Resolution → Output color depth → 8 bpc

Alternatively, change Output Color Format from RGB to YCbCr 4:2:2 (reduces bandwidth by ~33%).

Refresh Rate

Drop from 144Hz to 120Hz. If blackouts stop, the issue is bandwidth — your cable, port, or connection can’t sustain the higher rate. 120Hz is usually a comfortable compromise.

Fix 9: The Obscure Causes That Actually Solve It When Nothing Else Works

Static Electricity from Office Chairs

This sounds absurd but is well-documented. DisplayLink officially documents it, and The Register published an article on the phenomenon. When someone stands up or sits down, the gas piston generates an EMI spike picked up by video cables, especially DisplayPort. Fixes include cables with ferrite cores, better-shielded cables, or standing up more slowly.

Electromagnetic Interference from Nearby Devices

Heater cycles, printer power-on surges, laptop charger connections, ceiling lights on dimmers, and LED desk lamps with faulty switching transformers all generate EMI that disrupts display signals. One user eliminated blackouts by purchasing a UPS with line conditioning. Shorter cables are inherently less susceptible.

Ground Loops

When the PC and monitor are plugged into different electrical circuits, the difference in ground potential creates interference. Test: Plug both devices into the same power strip. If blackouts stop, ground loop confirmed.

Insufficient Monitor Power Adapter

A degraded power adapter that can’t supply enough current at full brightness causes blackouts identical to signal issues. An iFixit thread documented an LG monitor blacking out after 2 seconds — replacing the original 1.3A adapter with a 3.42A adapter fixed it permanently.

PSU 12V Rail Problems

Using a single “pigtail” PCIe power cable (one cable splitting into two 8-pin connectors) instead of two separate cables from the PSU causes voltage drops under load. Use two discrete cables for any GPU drawing over 200W. Monitor the 12V rail with HWiNFO64 — drops below 11.4V are out of ATX spec and cause instability.

TDR Registry Tweaks

Give the GPU more time to recover from brief stalls. At HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\GraphicsDrivers:

Create DWORD: TdrDelay = 10 (default is 2 seconds)
Create DWORD: TdrDdiDelay = 10 (default is 5 seconds)

These keys don’t exist by default — you must manually create them. Adobe and D5 Render recommend setting TdrDelay to 60 for heavy GPU workloads. Note: Windows and GPU driver updates can reset these values.

BIOS Settings

CSM (Compatibility Support Module): Intel Arc B580 has a documented bug where CSM auto-enables on warm boot. Try toggling CSM off.
Above 4G Decoding / Resizable BAR: These change how the CPU addresses GPU VRAM and can cause black screens if your GPU VBIOS doesn’t support them properly.
PCIe Generation: Downgrading from Gen 4 to Gen 3 has stabilized some RTX 50-series cards.

KVM Switch EDID Issues

Budget KVM switches don’t properly emulate EDID (Extended Display Identification Data), causing Windows to rearrange windows and default to low resolution when switching. EDID emulator dongles ($15–40) maintain persistent display identification.

Windows Update Regressions

Specific Windows updates have caused widespread display issues. Correlate blackout onset with recent updates via Settings → Windows Update → Update history. If a recent update coincides, uninstall it from the same menu.

The Complete Fix Sequence (Most to Least Likely)

Work through these in order. Each step eliminates a category of cause, optimized by probability based on thousands of confirmed reports:

Replace your display cable with a VESA-certified cable under 2 meters. (~30% fix rate)
Disable Multiplane Overlay via registry edit. (30 seconds, surprisingly high fix rate)
Set GPU power management to maximum performance and disable PCI Express Link State Power Management.
In monitor OSD: Disable Auto Source Select, DP Deep Sleep, and DDC/CI. Try changing DP version.
DDU clean install your GPU driver, targeting a known-stable version.
Disable adaptive sync (G-Sync/FreeSync) as a test.
Reduce color depth from 10-bit to 8-bit, or lower refresh rate.
Update monitor firmware from the manufacturer’s support page.
Check Event Viewer for TDR events and apply TDR registry tweaks if present.
Investigate environmental causes: EMI, ground loops, power adapter, PSU rails.
Check BIOS settings: CSM, Resizable BAR, PCIe generation.
Check recent Windows updates for regressions.

When to Accept It’s a Hardware Problem

If you’ve exhausted all software and configuration fixes:

Test with a completely different monitor on the same PC. If blackouts continue, it’s the GPU or PSU.
Test your monitor on a completely different PC. If blackouts continue, it’s the monitor.
If the monitor’s built-in self-test shows flickering with no cable connected, the monitor’s power board or backlight driver is failing — usually due to aging capacitors.
If blackouts only happen under GPU load and temperatures exceed 90°C, clean dust from the GPU heatsink and ensure adequate case airflow.
If HWiNFO64 shows 12V rail voltage dipping below 11.4V under load, your PSU needs replacement.

FAQ

Q: My monitor goes black when I open a specific website or video. A: This is almost always an HDCP (copy protection) handshake renegotiation. Protected content triggers HDCP authentication, causing a brief blackout. Switching from HDMI to DisplayPort (or vice versa) often helps, as HDCP implementations differ between protocols.

Q: The blackout only happens when I alt-tab out of a game. A: The GPU is switching between exclusive full-screen and desktop modes, renegotiating the display signal. Set the game to borderless windowed mode, or set G-Sync/FreeSync to “Full Screen Only.”

Q: Both monitors go black in my dual-monitor setup. A: Multi-monitor setups are prone to bandwidth-sharing issues. Mismatched refresh rates (e.g., 144Hz + 60Hz) force the GPU to handle two different timing domains. Try setting both monitors to the same refresh rate as a test. Also disable Hardware-Accelerated GPU Scheduling (HAGS) in Windows Display Settings.

Q: The blackout happens only when the room heater/AC/microwave turns on. A: Electromagnetic interference. Use shorter, shielded cables with ferrite cores, or plug the PC and monitor into a UPS with line conditioning.

Q: I’ve tried everything and the blackout still happens every 15–30 minutes. A: Methodically isolate: single monitor, new cable, different port on GPU, DDU clean driver install, disable all power management, disable adaptive sync, 8-bit color, 60Hz. If it still happens with all variables eliminated, test with a different GPU. If it stops, your GPU is the problem — even if it benchmarks fine, intermittent signal integrity issues can affect the display output without impacting compute performance.