Screen Flickering in Windows? Find If It's Driver or App
—
If your screen is flickering in Windows 11 or 10, open Task Manager (Ctrl+Shift+Esc) and watch it for ten seconds. If Task Manager itself flickers along with the rest of the screen, the cause is your display driver. If Task Manager stays rock steady while everything around it flickers, the cause is a single misbehaving app, not Windows and not your graphics card. Most flicker guides tell you to reinstall your graphics driver first. That guess is often wrong — Microsoft's own diagnostic starts somewhere else entirely, and it takes ten seconds to answer, no driver reinstall required.
This test has not changed since we first covered screen flickering not long after Windows 10 launched, and it hasn't needed to. It works because Task Manager is one of the few things you can put on screen that has nothing to do with whichever app is misbehaving — so if it flickers with everything else, the common factor is Windows drawing the screen itself, not the app underneath it.
It also means you don't need to know anything about your specific graphics card to run it. The test works the same whether you're on integrated graphics, a gaming laptop's dedicated GPU, or an older desktop card — Task Manager doesn't care what's underneath it, which is exactly why it's worth running before you touch a single driver setting.
Driver or app? The ten-second test, explained
Microsoft's own guidance narrows screen flickering down to exactly two causes: an incompatible app, or a display driver problem. Nothing else is on that short list, which is why the diagnostic can stay this simple. You are not looking for a symptom description — "it flickers when I scroll" or "it flickers randomly" tells you almost nothing on its own. You are looking for one binary fact: does the flicker follow Task Manager, or does it ignore it?
🙋♂️ Jake's Reality Check
"A guy dropped a laptop on my counter Tuesday because the screen kept strobing during a video call and he was too embarrassed to stay on camera. I don't know a driver from an app. Do I really need to know the difference before I can even start?"
Yes, but only for thirty seconds. You don't need to understand what a display driver is to run this test — you just need to open Task Manager and watch it. The answer tells you which of the next two sections to read, and you can skip the other one entirely.
A couple of things can trip the test up, and it's worth knowing them before you run it. If your whole desktop flickers only when you're near a window with bright sunlight behind a webcam, that's a camera exposure issue, not a screen issue — Task Manager won't help there. And if the "flicker" is really a brief black screen followed by everything reappearing, that's usually a driver crash-and-recover event rather than a flicker, and it points at the driver route regardless of what Task Manager does, because the whole GPU output briefly dropped.
| What you see | Likely cause | Where to go |
|---|---|---|
| Task Manager flickers along with everything else | Display driver | Windows 11 or Windows 10 driver section below |
| Task Manager stays steady, background flickers | One app | Isolating the app, below |
| Brief full black screen, then recovers | Driver crash-and-restart | Driver section, regardless of Task Manager |
| Only in fullscreen games or video | Refresh rate mismatch or overlay | Hard cases, below |
| Only on one of two monitors, or since plugging one in | Cable, port, or per-monitor refresh rate | Hard cases, below |
Windows 11: fixing a display driver flicker
If Task Manager flickered with everything else, the fix lives in the driver, not in any individual app. There are three routes, in the order to actually try them.
Route 1: check Windows Update for an optional driver update first
Open Settings > Windows Update > Advanced options > Optional updates > Driver updates. Microsoft distributes many display driver updates through this exact channel before you'd ever go looking for them manually, and it's the least error-prone way to update, because it only offers drivers Microsoft has already matched to your exact hardware. If nothing is listed there, that's useful information too — it means your driver isn't the thing Microsoft flagged, and you should move to Route 2.
Route 2: Device Manager, for a targeted update or a rollback
Press Win + R to open the Run box — a small dialog that launches a program or file by its short internal name instead of hunting through menus — and type devmgmt.msc. This still works exactly the same way in Windows 11 as it always has. Expand "Display adapters," right-click your GPU, and choose "Update driver." If the flickering started right after a driver updated itself — usually right after a Windows Update — right-click the same adapter, choose Properties, go to the Driver tab, and use "Roll Back Driver" instead. That button only appears if Windows kept the previous driver package. If you don't see it, Windows didn't retain an earlier version to fall back to, and Route 1 or Route 3 is your next move instead.
Route 3: go straight to the manufacturer if Routes 1 and 2 come up empty
Intel, AMD, and NVIDIA all publish their own driver download pages, and their versions are sometimes newer than what Windows Update offers, particularly right after a new GPU driver release. Look up your exact GPU model first — Device Manager's Display adapters entry will name it — and download from the manufacturer directly rather than a third-party download site.
✅ Why this is the one to use
Start with Route 1, not Route 3. "Ethan's take is that jumping straight to a manufacturer's site is the fastest way people make a flicker worse — they grab the wrong sub-model, or a driver built for a different Windows version, when Windows Update would have offered the exact right match automatically." Only fall back to the manufacturer when Windows Update genuinely has nothing.
The Windows 11 traps that slow this down
None of these change the fix. They just cost you time if nobody warns you first.
The right-click menu is condensed in Windows 11 — you'll see a short list of icons rather than the full menu you're used to. If you're looking for an option that used to be one click away and it isn't there, click "Show more options" (or press Shift+F10), and the classic full menu appears. It doesn't affect Device Manager itself, but it trips people up constantly on the desktop and in File Explorer while they're navigating around this fix.
Display settings themselves have mostly moved into Settings > System > Display, with Control Panel now acting as a fallback rather than the primary path. Control Panel still exists in Windows 11 and still opens, but new display and driver-adjacent settings are increasingly Settings-first. If a menu you remember from an older Windows version isn't where you expect, check Settings before assuming it's gone.
File Explorer's default landing page in Windows 11 is called "Home," not "Quick Access" — worth knowing if a guide tells you to navigate somewhere via Quick Access and you can't find that label anymore. It's the same place, renamed.
Windows 10: fixing a display driver flicker
The mechanics are identical to Windows 11 — same Device Manager, same rollback button, same Windows Update optional-updates path — the menus just look like the Windows 10 you already know. Open the Run box with Win + R, type devmgmt.msc, expand Display adapters, and update or roll back the driver exactly as described above. Where Windows 11 groups optional driver updates under Advanced options, Windows 10 lists them under Settings > Update & Security > Windows Update > View optional updates.
⚠️ What Windows 10's end of support actually breaks here
Windows 10 reached the end of free security updates on October 14, 2025. That date doesn't stop your display driver from updating — driver delivery through Windows Update and manufacturer sites keeps working regardless of ESU enrollment. What it does mean is that Windows 10 itself is no longer getting the security patches that used to arrive alongside those optional updates, so if you're troubleshooting a flicker on an unenrolled Windows 10 PC, you're doing it on a machine that's otherwise unpatched. That's a separate problem from the flicker, but it's worth knowing while you're already in Windows Update.
If you want to keep receiving Windows 10 security updates while you sort out hardware or budget for something newer, Microsoft's Consumer ESU program is still open for enrollment as of this writing — Settings > Windows Update > "Enroll now," and it's free if you sync your settings through Windows Backup, costs 1,000 Microsoft Rewards points, or a one-time roughly $30 otherwise. It requires being on the 22H2 update and signed in with a Microsoft account rather than a local one. None of that changes how you fix a flicker — it's just the honest bridge if the flickering laptop in front of you is also the reason someone's been putting off replacing it.
It's not the driver — isolating the app
If Task Manager stayed steady, the driver is fine, and closing the flickering app or reinstalling it is genuinely often enough to end it there. But "close the app" only helps once you know which app. Here's how to find it without guessing, and this part is identical on Windows 11 and Windows 10 — the tools involved haven't changed between the two.
Reliability Monitor: a timeline of what crashed and when
Press Win + R and type perfmon /rel. This opens Reliability Monitor, which plots a daily reliability score alongside a log of application failures, Windows failures, and warnings — and critically, it timestamps them. If your screen flickers a few times a day, cross-reference the times against this log. An app that logged a failure minutes before you noticed the flicker is your strongest suspect, and you don't have to remember which apps you had open — Reliability Monitor already recorded it.
Process of elimination, the low-tech version
If Reliability Monitor doesn't show anything conclusive, close background apps one at a time, starting with anything that draws its own overlay on top of your desktop or other windows — screen recorders, video call software, RGB lighting control apps, and older cloud-sync clients are the recurring offenders, because overlay rendering is exactly the kind of thing that goes wrong when an app hasn't been updated to match how the current version of Windows composites the screen. Wait a minute or two after each close before deciding it's fixed, since an intermittent flicker can go quiet on its own for a stretch.
A clean boot narrows it further
Type msconfig into the Run box, open the Services tab, check "Hide all Microsoft services," then click "Disable all." Go to the Startup tab, open Task Manager from there, and disable every startup item. Restart. If the flicker is gone, something you disabled was the cause, and you re-enable items in batches to narrow it down. If it's still flickering after all of that, the cause isn't a startup app at all, and it's worth revisiting whether Task Manager really stayed steady during your original test.
✅ Why this is the one to use first
Reliability Monitor before process of elimination, every time. Closing apps one by one is guesswork with extra steps if Windows already logged the exact failure and the exact minute. Save the manual method for when the log genuinely has nothing.
When it's neither: refresh rate, cables, and hardware
A small number of flickers are neither a driver problem nor an app problem, and the Task Manager test won't catch these because they're happening below the level where any software runs.
🙋♂️ Jake's Reality Check
"I ran the Task Manager test on a customer's laptop and honestly couldn't tell if it flickered or not — the whole screen looked kind of wrong, not a clean strobe. Am I doing it wrong?"
You're not doing it wrong — you're describing a different symptom. A clean on/off strobe is a driver or app flicker. A screen that looks subtly wrong, shimmery, or wrong-colored constantly rather than flashing is more often a refresh rate mismatch or a cable issue, and neither of those is what this test is built to catch.
Refresh rate mismatch
If the flicker only shows up in fullscreen games or video, check Settings > System > Display > Advanced display (Windows 11) or Settings > System > Display > Advanced display settings (Windows 10) and confirm the refresh rate matches what your monitor actually supports. A monitor set to a refresh rate it can't reliably hold will flicker specifically under full-screen load, when Windows hands more direct control of the screen to the app, and stay fine on the desktop the rest of the time. Dropping it one step — from 144Hz to 120Hz, for example — is a legitimate diagnostic step even if it's not where you want to leave it long-term.
Cable, port, and a genuinely useful test: swap the monitor
If the flicker only happens on one of two connected monitors, or started the moment you plugged a second monitor in, try a different cable and a different port before touching any driver settings — a loose or marginal HDMI or DisplayPort connection produces exactly this symptom and no software fix will ever resolve it. On a laptop with a flickering built-in screen, plugging in an external monitor is the fastest hardware-versus-driver test that exists: if the external monitor is perfectly steady while the built-in panel flickers, you're looking at a laptop display or cable problem, not a driver, and that's a hardware repair conversation, not a software one.
⚠️ What we can't fix from here
If the external-monitor test points at the laptop's own screen or its internal cable, no driver update or app fix will resolve it. That's a physical repair, and it's fair to say so plainly rather than sending someone through another round of driver reinstalls that were never going to work.
Edge cases: docking stations, Remote Desktop, and virtual machines
The Task Manager test assumes a fairly ordinary setup: one PC, one or two monitors plugged in directly. Add a dock, a remote session, or a virtual machine into the mix, and the same test can point you in the wrong direction if you don't know what to adjust for.
Docking stations and multi-monitor hubs
A docking station or USB-C hub sits between your GPU and your monitors, and it can introduce exactly the same symptom as a bad cable — a monitor connected through a dock is more likely to flicker than one plugged straight into your laptop's own port, simply because there's more hardware in the signal path. If a monitor flickers only when docked and not when connected directly, the dock itself is the suspect, not your driver.
🙋♂️ Jake's Reality Check
"My checkout PC is docked to two monitors, and the right one starts flickering about twenty minutes into every shift — right when I've got a line forming. I've already updated the driver twice."
"Ethan's rule here is simple: reinstalling a driver never fixes a dock," so stop updating it. Plug that monitor straight into the PC instead of through the dock for a shift and see if it clears up before you touch the driver a third time.
Remote Desktop and VDI sessions
Flickering inside a Remote Desktop or virtual desktop session is a different animal from flickering on your physical screen. Running Task Manager inside that remote window tells you about the remote machine's driver, not the one in front of you. If only the remote session flickers and everything else on your actual desktop is steady, the driver to check is on the remote or host machine — not your local PC.
Virtual machines
A flickering VM window is almost always the VM's own virtual display driver or its graphics acceleration setting, not your host PC's real GPU driver. Most virtualization software has a toggle for 3D or graphics acceleration inside the guest operating system — turning that off is worth trying before you go anywhere near a driver on the host machine.
Third-party driver cleaners: when they're actually worth it
Tools that do a full driver wipe before reinstalling exist because a straightforward "Update driver" in Device Manager sometimes leaves old driver files behind, and those leftovers can occasionally conflict with a fresh install in ways that look like a flicker that "should" have been fixed but wasn't. They're a real option, but they're also not the first thing to reach for. Try the built-in Update Driver and Roll Back Driver options first — they solve the overwhelming majority of driver-caused flickers without touching anything else on the system. Reach for a full driver cleanup tool only after a straightforward update or rollback genuinely hasn't worked, since a full wipe-and-reinstall takes longer and briefly leaves you with no display driver at all mid-process.
Stopping it from coming back
Once you've fixed it, the two most common ways it comes back are a fresh driver update through Windows Update reintroducing the same bug, and a reinstalled app bringing its overlay back with it.
🙋♂️ Jake's Reality Check
"Every time I finally get a machine quiet, something breaks it again a month later. Is that just how this goes?"
Pretty much, and that's fine. "Ethan says the point of this guide isn't to make flickering never happen again — it's that you'll already know exactly where to look the next time it does." Roll Back Driver is sitting in the same Device Manager tab it was the first time.
🕐 What changed since we first wrote this
- Then: this guide originally covered only Windows 10, not long after it launched, and the Task Manager test was the whole fix.
- Now: Windows 11 exists alongside it, and Windows 10 reached the end of free security updates on October 14, 2025 — still running, still fixable, just no longer patched unless enrolled in Consumer ESU.
- What that means for the steps above: the Task Manager test and the Device Manager fix are unchanged on both. The only new step is that Windows 11's menus are laid out a little differently, and we've flagged where.
Frequently asked questions
Does the Task Manager test still work if the flicker is very brief?
Yes, but give it longer than you think you need — watch for at least thirty seconds to a minute if the flicker is intermittent, since a single ten-second glance can miss an event that happens every ninety seconds.
Why does only my mouse cursor flicker, not the whole screen?
A flickering cursor specifically, with everything else steady, points at the same driver route as a full-screen flicker — cursor rendering is handled by the display driver too, and it's actually one of the more common early symptoms of a driver that's about to cause a bigger flicker elsewhere.
Can a bad Windows Update by itself cause screen flickering?
Yes, most often through the display driver update that sometimes rides along with a feature or cumulative update. If the flicker started the same day as an update, roll back the driver first before assuming anything else changed.
Is it safe to roll back a display driver on Windows 11?
Yes — Roll Back Driver only appears when Windows has kept the previous driver package, and using it simply restores that exact prior version. It doesn't touch anything else on the system.
My laptop only flickers on battery power — is that the same problem?
Not usually. That pattern points at a power-saving GPU switch (integrated graphics taking over from a dedicated GPU to save battery) rather than a driver fault. Check your power plan's graphics settings before chasing a driver fix for this specific symptom.
Does plugging in an external monitor rule out a laptop's built-in display driver?
Not entirely, but it's a strong signal. If both screens flicker identically with an external monitor attached, the driver is still the likely cause. If only the built-in screen flickers, you're probably looking at a hardware issue with that specific panel or its cable.
Can antivirus software cause screen flickering?
It can, if it draws its own overlay or notification pop-ups aggressively, though it's less common than conferencing or screen-recording apps. Reliability Monitor will usually catch a security app if it's genuinely the cause.
Why does the flicker only happen in fullscreen games or video?
This is the classic refresh rate mismatch pattern described above — fullscreen apps take more direct control of the display than the desktop does, which is exactly when an unsupported refresh rate setting tends to show itself.
Is screen flickering covered under warranty if it turns out to be hardware?
That depends entirely on your specific warranty terms and how old the device is — we can't tell you that from here. What we can tell you is that the external-monitor test above is exactly the evidence a manufacturer or repair shop will want to see before they'll act on a hardware claim.
Should I update the driver from Windows Update or the manufacturer's site?
Start with Windows Update's optional updates. It's the safest match for your exact hardware. Only go to the manufacturer's site directly if Windows Update has nothing to offer.
Can a Windows 11 upgrade cause flickering that Windows 10 never had?
It can, usually because the upgrade installed a new display driver version your GPU hadn't run before. Run the same Device Manager check described above — the fix doesn't change just because the OS did.
What if the flicker started right after I plugged in a second monitor?
Check that both monitors are set to refresh rates they actually support, and try a different cable on the newly connected one first — this is one of the most common triggers and it's rarely the driver's fault.
Should I use a third-party driver cleaner every time I update my GPU?
No. Reserve it for when Device Manager's own Update or Roll Back options haven't solved the problem. A full driver wipe is a bigger step than most flickers need.
Why does only one monitor flicker when it's connected through a docking station?
More hardware sits between your GPU and that monitor than on a directly connected one, which makes docked monitors more prone to this exact symptom. Try connecting straight to the PC before touching the driver.
Does a flickering Remote Desktop or VM window mean my own PC's driver is at fault?
No. A flicker confined to a Remote Desktop or virtual machine window points at the driver on the remote or host machine, or the VM's own virtual display settings — not the physical PC you're sitting at.
Does Windows 10 Consumer ESU include driver updates?
ESU covers security updates for Windows 10 itself. Display driver delivery through Windows Update's optional updates and through manufacturer sites is a separate channel and keeps working with or without ESU enrollment.
Revision note. Originally published December 25, 2016, for Windows 10 alone. Rewritten August 2026 to cover Windows 11 and Windows 10, and to add the diagnostic steps — Reliability Monitor, driver rollback, dock and VM edge cases, and the refresh rate and cable checks — that the original short version didn't have room for. The core test, watching Task Manager to tell a driver problem from an app problem, is exactly the one we described a decade ago, because it never stopped working. If a strobing screen has been making you afraid to leave a video call on, we hope the next ten minutes fix that for good.