Screen flickering on Windows 11 has two completely different causes that produce symptoms that can look identical to the user. Knowing which type you have changes everything about the fix. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
Diagnosis in 30 seconds: Open Task Manager (Ctrl+Shift+Esc). Does Task Manager flicker along with everything else? If yes — everything on screen flickers including Task Manager — it’s an incompatible display driver or hardware issue. If no — Task Manager stays stable while other things flicker — a specific application or shell component is causing it.
This distinction matters because the fixes are completely different. Task Manager flickering = driver or hardware problem. Task Manager stable = application, Windows Explorer, or shell issue.
When Task Manager flickers (driver/hardware path)
Fix 1: Update the display driver
The most common cause. Either the driver is outdated, it was replaced by a generic Microsoft version during a Windows update, or a recent driver update introduced a bug. Download the current driver from:
- NVIDIA: nvidia.com/drivers
- AMD: amd.com/support
- Intel: go to the laptop manufacturer’s support page, not Intel’s generic installer
Don’t use Windows Update or Device Manager’s automatic search for this — they often install generic or older drivers. Install the manufacturer’s current version, restart, and test.
If flickering started immediately after a driver update: roll it back. Device Manager → Display Adapters → right-click GPU → Properties → Driver → Roll Back Driver.
Fix 2: Refresh rate mismatch
Setting a refresh rate that the monitor can’t handle at the current resolution causes consistent flickering or visual artifacts. Settings → System → Display → Advanced display → Refresh rate → ensure it matches what the monitor actually supports. Monitors list their supported refresh rates in their specifications or OSD menu.
For monitors connected via HDMI: some HDMI cables only support 60Hz at 4K. A monitor that should run at 144Hz shows at 60Hz maximum via certain cables, and forcing 144Hz in Settings causes flickering. Either use a DisplayPort cable (which has higher bandwidth) or accept the cable’s limitation.
Fix 3: Cable and connection
A marginal HDMI or DisplayPort cable — one that passes most signals but not consistently — causes exactly this flickering pattern. The connection works most of the time but drops signal intermittently. Swap the cable. Use a different port on the GPU. Try both. A £5 cable swap has fixed many “display driver” investigations.
Also: HDMI connectors can work loose over time. Pressing the connector firmly into the port sometimes stops flickering immediately — confirming a physical connection issue rather than a driver problem.
Fix 4: Hardware acceleration setting
Settings → System → Display → Graphics → Change default graphics settings → Hardware-accelerated GPU scheduling. Toggle it. Some display configurations work better with this enabled; others flicker specifically because of it. Toggle, restart, test — it takes two minutes to confirm whether this is the variable.
When Task Manager is stable (application/shell path)
Fix 5: The application causing it
If flickering correlates with a specific application being open — only appears in Chrome, only in games, only in video editing software — that application’s rendering is the issue. Common causes: hardware acceleration in the browser (same fix as above, disable hardware acceleration in Chrome/Edge settings), outdated application, or an application that requires a specific GPU driver version.
For Chrome and Edge: Settings → System → uncheck “Use hardware acceleration when available” → Relaunch → test.
Fix 6: Windows Explorer and shell issue
If the flickering affects the desktop, taskbar, and file windows but not Task Manager — and isn’t limited to one application — Windows Explorer is the flickering source. This typically traces to an incompatible startup application or shell extension.
Test: Task Manager → Startup apps → disable all startup apps → restart. If flickering stops, one of the disabled startup apps was causing it. Re-enable them in pairs to narrow it down. Also check ShellExView (NirSoft, free) for any newly installed shell extensions that might be causing Explorer instability.
Fix 7: Windows update
Windows updates sometimes introduce display bugs that affect specific GPU and monitor combinations. If flickering started immediately after an update: check Windows Update history → look for the display-related update that installed → Settings → Windows Update → Update history → Uninstall updates → remove it. Also check if there’s a newer cumulative update available that may have already fixed the regression — often faster than rolling back.
Laptop-specific: power management and screen flickering
Laptops with hybrid graphics (Intel + NVIDIA or AMD Radeon) can flicker when switching between the integrated and discrete GPU. This happens when an application triggers the switch and the transition causes a brief black flash or flicker. Windows 11 manages this automatically, but driver updates sometimes make the switching more aggressive or poorly timed.
Settings → System → Display → Graphics → set specific applications to “Power saving” (integrated GPU) rather than “High performance” (discrete) to reduce the number of GPU switches during normal use.
For the display driver reinstall process with DDU when simple updates don’t resolve flickering, our display driver crash guide covers the clean reinstall approach that eliminates driver remnants. If flickering is accompanied by display driver crash notifications (TDR events), that guide’s GPU stability diagnostics apply here too. Microsoft’s Windows 11 display troubleshooting covers the HAL (Hardware Abstraction Layer) display settings and the DWM (Desktop Window Manager) that manages compositing, which is the underlying component in most shell-related flickering scenarios.
HDR and high refresh rate combinations
Enabling HDR on Windows 11 while using a high refresh rate monitor sometimes causes flickering or color flashing, particularly on displays connected via HDMI 2.0 (which has limited bandwidth for HDR at high refresh rates). HDR at 4K 120Hz requires HDMI 2.1 or DisplayPort 1.4; HDMI 2.0 can only carry 4K HDR at 60Hz reliably.
Test: Settings → System → Display → Windows HD Color → toggle HDR off. If flickering stops, the combination of your cable/port and the HDR settings is creating bandwidth issues. Solutions: disable HDR at high refresh rates, use DisplayPort instead of HDMI, or reduce the resolution when HDR is needed.
Overclocked monitors
Some monitors can be overclocked beyond their factory-rated refresh rate through GPU driver control panels or monitor OSD menus. A monitor running at 165Hz that’s only rated for 144Hz may work fine most of the time but flicker under certain rendering conditions. Return the refresh rate to the monitor’s rated specification in Settings → System → Display → Advanced display and test stability. If flickering stops at the rated rate but returns at the overclocked rate: the overclock is unstable for that specific panel.
Multiple monitors and the DWM interaction
Desktop Window Manager (DWM) manages how Windows composes multiple monitor outputs. When monitors have different refresh rates — say, 144Hz primary and 60Hz secondary — DWM has to reconcile the rendering for both. This mismatch sometimes causes flickering on the higher-refresh-rate monitor, particularly in the desktop area and when applications span both monitors.
Test: disconnect the secondary monitor and check whether primary monitor flickering resolves. If it does: the refresh rate mismatch is affecting DWM compositing. Matching the refresh rates by changing the secondary monitor to 144Hz (if it supports it) or reducing the primary to 60Hz (less ideal but eliminates the mismatch) resolves this specific case.
Display port frequency vs monitor native frequency
Monitors report their native frequency to Windows through EDID (Extended Display Identification Data). Occasionally EDID data is corrupt or incorrectly formatted, causing Windows to apply settings the monitor doesn’t actually support. Custom resolution utility (CRU, free) can edit EDID data and force correct frequency reporting, but this is an advanced fix — most users won’t need it. The sign that EDID is the issue: Windows offers refresh rates that the monitor manual says aren’t supported, and using them causes flickering.
Flickering only in full-screen applications
Full-screen games and applications that run in exclusive full-screen mode bypass DWM entirely and communicate directly with the GPU. When the GPU driver has issues with this direct mode — which sometimes occurs with specific games or after driver updates — flickering appears only in full-screen while windowed mode is stable.
Test: if a game has windowed or borderless windowed options, try those. Borderless windowed uses DWM rather than exclusive full-screen and often eliminates driver-specific full-screen flickering. Alternatively: NVIDIA Control Panel → Manage 3D settings → Vertical sync → Force On. Forcing VSync prevents the GPU from rendering frames faster than the monitor’s refresh rate, which can cause screen tearing and flickering in exclusive full-screen when frame rates exceed the refresh rate significantly.
GPU voltage and stability
On desktop machines with overclocked or unstable GPUs: graphical instability including flickering is a sign of insufficient GPU voltage or an unstable overclock. This is different from display driver flickering — it manifests as graphical corruption alongside flickering rather than just a simple refresh issue. MSI Afterburner can reduce GPU core clock and memory clock to factory defaults, eliminating overclock instability as a variable. If flickering resolves at stock speeds, the overclock configuration needs adjustment for stability.
Software rendering mode as a temporary diagnostic
Forcing Windows into software rendering mode (using the CPU for display rather than the GPU) is a useful diagnostic that confirms whether the GPU is causing the issue. Boot into Safe Mode (which uses basic display without the GPU driver) → if flickering is absent in Safe Mode, the GPU driver is confirmed as the problem. Safe Mode uses only the basic Microsoft display driver, which is stable but limited to low resolutions and no hardware acceleration.
DWM crash and restart cycle
When DWM (Desktop Window Manager) crashes and restarts — which can happen due to application crashes, driver bugs, or memory issues — it produces a brief black screen or visual glitch that users often report as “screen flickered.” Unlike persistent flickering, a DWM crash is a one-time event that may not recur. Check Event Viewer → Windows Logs → Application → look for “dwm.exe” errors to confirm whether DWM is crashing and restarting rather than experiencing ongoing refresh issues. If DWM crashes are logged: updating the GPU driver and checking application compatibility are the appropriate responses, as DWM crashes are almost always caused by these two factors.
Adaptive sync (G-Sync/FreeSync) and compatibility
G-Sync and FreeSync reduce screen tearing by synchronising the monitor’s refresh rate with the GPU’s frame output. When these features are enabled on hardware that doesn’t fully support them — a G-Sync monitor with a non-NVIDIA GPU, a FreeSync monitor at frame rates outside its sync range, or a monitor using adaptive sync over HDMI rather than DisplayPort — flickering at certain frame rate ranges is a common result.
Test: disable G-Sync or FreeSync in the GPU control panel (NVIDIA Control Panel → Display → Set up G-Sync → uncheck; AMD Radeon Settings → Display → FreeSync → off) and test stability. If flickering resolves, the adaptive sync implementation is the cause. Check whether the monitor requires DisplayPort for adaptive sync (many do, and HDMI adaptive sync is less reliable), whether the GPU supports adaptive sync on that port, and whether the game’s frame rate is within the monitor’s sync range (listed in specifications as the VRR range, e.g., 48–144Hz).
Clean GPU driver reinstall with DDU
When driver updates and rollbacks haven’t resolved persistent flickering: a complete clean reinstall removes all driver files and registry entries before installing fresh. Display Driver Uninstaller (DDU, from guru3d.com) is the standard tool for this.
- Download DDU and the new GPU driver installer (have it ready before starting)
- Boot into Safe Mode (DDU recommends running in Safe Mode to avoid Windows reinstalling drivers during the process)
- Run DDU → select GPU manufacturer → “Clean and restart”
- After the clean restart (in normal mode), install the downloaded GPU driver
This is more involved than a standard update but eliminates the possibility of conflicting driver remnants that simple updates leave behind. Many “fixed by DDU” flickering reports exist specifically because multiple driver update iterations leave incompatible files that normal installation doesn’t clean up.
Going back to the diagnostic: did Task Manager flicker? If yes → driver/hardware path (DDU reinstall, cable, refresh rate, adaptive sync). If no → application/shell path (startup apps, specific application hardware acceleration, Explorer). These two paths don’t overlap much, so confirming which one applies at the start keeps the troubleshooting focused and efficient. Our guide on Packet Loss on Windows 11 covers an adjacent issue.
One scenario worth noting that confuses the diagnostic: a second monitor where the GPU isn’t using dedicated VRAM for its display (particularly common in mixed GPU setups) can cause the primary monitor’s DWM compositing to flicker when the secondary monitor renders content. This appears as “primary monitor flickering” but is actually DWM having trouble compositing two monitors with different rendering paths. Testing with only the primary monitor connected clarifies whether the second monitor is involved in the flickering, which would redirect troubleshooting toward multi-monitor configuration rather than the primary monitor’s hardware or driver. See also Screen Resolution Keeps Changing in Windows 11 for a related case.
