How to Reset a Graphics Driver (Win+Ctrl+Shift+B and Beyond)

The screen goes black after the laptop wakes, the audio keeps playing and the cursor is gone. Before anyone holds the power button, there is a four-key combination that restarts the display stack in about a second and keeps every window open. This guide covers how to reset a graphics driver that way, what Windows does on its own when the GPU hangs, how to read the event it leaves behind, and when a reset is hiding a problem that needs a reinstall or a part.

What Win+Ctrl+Shift+B Does

Press the Windows key, Ctrl, Shift and B together. The screen goes dark for a moment, the PC beeps once, and the desktop redraws. Microsoft's keyboard shortcut list describes it in one line: "Wake up the device when the screen is blank or black."

Under that line, Windows restarts the graphics driver stack. The display driver reloads, the GPU's state is reset and the desktop is drawn again from scratch. Open applications stay open. Unsaved work stays where it was. Nothing is closed and nothing is installed.

What the shortcut does not do matters just as much. It doesn't change the driver version, it doesn't clean anything up, and it doesn't touch whatever caused the hang. If the screen goes black again in ten minutes, the shortcut bought you ten minutes.

When the Shortcut Is the Right First Move

Reach for it when the picture is wrong but the machine is clearly alive: a black screen after sleep or after pulling a dock, with audio or disk activity still running; a frozen desktop after a game or a GPU-heavy app; coloured static, torn tiles or a half-dead panel; an external monitor that vanished after a cable swap. In each case the GPU or its driver has stopped drawing, and a reset is the cheapest test.

The result tells you something either way. In June 2026 an r/pcmasterrace poster described modded Minecraft dropping to one frame per second every few minutes, with temperatures normal, no overclock and older and newer drivers both tried. Only a driver reset brought the machine back, and three replies reported the same fault with no cause found. That is the shortcut working as a bandage:

The opposite outcome is just as useful. A Lenovo laptop in another thread glitched every 7 to 15 minutes on its built-in panel, the shortcut fixed it every time, and an external monitor never showed the fault. A reset that keeps working on one panel and never on another is describing a cable or a screen, not a driver:

If the picture comes back and stays back, you're done. If it comes back and goes again, keep reading, because Windows has already been doing this reset for you and leaving notes.

What Windows Does on Its Own

Windows has a built-in version of the same recovery called Timeout Detection and Recovery, or TDR. Microsoft's TDR documentation (updated November 2025) describes the mechanism: the GPU scheduler inside Dxgkrnl.sys hands the GPU a task, and if the GPU can't finish or interrupt it within two seconds, Windows decides the GPU is frozen.

What follows is the reset. The driver is told to reinitialise, the video memory manager purges every allocation, the driver resets the GPU hardware and the desktop is restored. The only visible artifact, in Microsoft's words, is a screen flicker. Then Windows shows the message "Display driver stopped responding and has recovered" and writes the same line to the event log.

Applications don't all survive it. Programs that handle device removal, which Microsoft describes as well-written DirectX 9Ex and DirectX 10 and later apps, carry on. Older DirectX programs may render black until you restart them.

There is a limit. By default, five GPU hangs with recoveries inside one minute mean the sixth hang bug-checks the machine with VIDEO_TDR_TIMEOUT_DETECTED, stop code 0x117. That is the moment a flickering screen turns into a blue screen, and it's why a machine that "keeps fixing itself" needs a look before it stops fixing itself.

Read the Event Before You Fix Anything

Every automatic recovery leaves a record. Open Event Viewer, go to Windows Logs, then System, and filter the source Display for Event ID 4101. The message names the driver that hung, which is the first real clue: nvlddmkm is NVIDIA, amdkmdag is AMD, igdkmd64 is Intel integrated graphics.

PowerShell pulls the last 30 days in one line:

powershell
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Display'; Id=4101; StartTime=(Get-Date).AddDays(-30)} |
  Select-Object TimeCreated, Message

Read the pattern, not the single entry. One 4101 a month is a long GPU job tripping the two-second limit and is worth nothing more than a note. Several a day, clustered around one application or one time of day, point at that application's rendering path, hardware acceleration in a browser, or an overclock. A 4101 followed by a 0x117 bug check is the five-in-a-minute rule firing, and the machine needs a clean driver before it needs anything else. The symptom that never shows up on an external display isn't in this log at all, because it isn't a driver.

Restart the Driver From Device Manager

The shortcut is a quick reset. The next rung fully unloads the driver and loads it again. Open Device Manager, expand Display adapters, right-click the GPU and choose Disable device. Wait for the screen to settle, then right-click again and choose Enable device. Expect a longer blackout than the shortcut gives you, and a resolution change while the basic display driver fills in.

The same thing scripts cleanly. The PnpDevice module in PowerShell exposes Get-PnpDevice -Class Display, and Disable-PnpDevice followed by Enable-PnpDevice on the instance ID does what the right-click does. On a machine you reach over a remote tool, that pairing is safer than the keyboard shortcut, which needs the keys to arrive at the console session.

Two things this rung is not for. If the taskbar or File Explorer is what's stuck while the picture itself is fine, the fix is to restart Windows Explorer, not the GPU. And if the display driver is the one that has stopped responding every hour, reloading the same files changes nothing.

Clean Reinstall When the Reset Keeps Coming Back

A driver that hangs on a schedule needs replacing, not restarting. Start with the vendor's package for the exact GPU and the exact OS build, and use the installer's own clean option: NVIDIA's custom install has a "Perform a clean installation" checkbox and AMD's Adrenalin installer has a factory reset option, both of which wipe the previous profile and settings before installing. On a laptop, take the package from the laptop maker when the GPU is a hybrid Intel-plus-discrete setup, because the two drivers are tuned to each other.

When the vendor installer can't get a clean slate, Display Driver Uninstaller does the removal. Wagnardsoft describes DDU as a utility that completely uninstalls AMD, NVIDIA and Intel graphics drivers "trying to remove all leftovers (including registry keys, folders and files, driver store)". The practice that has held up for years: boot to Safe Mode, run DDU for the vendor you're replacing, and stop Windows Update from pushing its own driver in the gap before you install the one you chose. Our guide on updating drivers covers that update policy and the rollback path.

Then test with the event log, not with your eyes. A clean reinstall that still produces 4101s at the same rate has cleared the driver from the suspect list, and the next names on it are thermals, the power supply, the cable and the card.

Admin365's two-minute walkthrough shows the shortcut and the Device Manager restart on a Windows 11 desktop, for anyone who wants to see the flicker before trying it on a user's machine:

TdrDelay Is a Dial, Not a Fix

Search for the 4101 message and the top advice is a registry edit. The keys live under HKLM\System\CurrentControlSet\Control\GraphicsDrivers, and Microsoft's TDR registry reference lists them: TdrDelay (the timeout, default 2 seconds), TdrDdiDelay (how long threads get to leave the driver before a 0x116 bug check, default 5), TdrLimitCount and TdrLimitTime (the five-in-60-seconds rule) and TdrLevel, where 3 is the default recovery and 0 switches detection off.

The same page carries a warning in bold: "End users shouldn't manipulate these registry keys." The keys exist for driver developers testing their own code.

Here is why the warning is right for a help desk. Raising TdrDelay from 2 to 8 doesn't stop the GPU from hanging. It makes every hang four times longer before Windows steps in, and it lowers the 4101 count, which is the number you were using to find the fault. Setting TdrLevel to 0 removes the recovery altogether, so the next hang is a hard freeze and a power button. The one defensible case is a workstation running long GPU compute jobs that legitimately exceed two seconds, and even there the change belongs in the device's documentation with a date and a reason.

Across a Fleet

One machine with a flaky display driver is a ticket. Twenty is a driver version, and the fix is policy. Three things keep it that way.

Count the events, per device, per week. The Get-WinEvent line above returns the number in seconds, and a list sorted by count puts the right machine at the top instead of the loudest user. OpenFrame can run that script across a client's devices and collect each machine's output, so the list builds itself.

Pin one driver version per GPU model and move it on a ring. Intune's driver update policies support automatic or manual approval, per Microsoft's documentation, so a new graphics driver can wait on a test group before it reaches the fleet. The driver update guide covers the Intune and Group Policy side.

Keep firmware in the picture. A laptop that resets its display driver every few minutes on battery is as often a BIOS update away from fixed as a driver away, because power management lives there.

The Short Version

Press Win+Ctrl+Shift+B first; it costs a flicker and keeps every window. Then read Event 4101 in the System log and count, because Windows has been resetting the driver on its own at a two-second timeout and writing it down each time. A driver that hangs on a schedule gets a clean reinstall, with DDU if the installer can't clear the leftovers. A fault that survives a reinstall and a different driver version is hardware. TdrDelay is a dial that makes the freeze longer and the count smaller, so it goes last and gets documented. When the reset turns into a stop code, the blue screen guide picks up from there.

FAQ

Does Win+Ctrl+Shift+B close my programs?

No. The shortcut restarts the display driver stack and redraws the desktop. Open applications and unsaved work are untouched. Some older DirectX programs may show a black window until you restart them, which is the same behaviour Microsoft describes for an automatic TDR recovery.

Why does the PC beep when I press it?

The beep is Windows confirming that the reset ran, and it plays even when the screen stays black for a moment. If you hear the beep but the picture never returns, the GPU or the cable to the monitor is the next suspect, not the driver.

Is it bad for the GPU to reset the graphics driver often?

The shortcut triggers the same kind of driver restart that Windows performs on its own when a GPU task overruns its two-second limit. The cost is a flicker and any application that doesn't survive a device reset. The risk isn't the reset itself; it's using it to ignore a 4101 count that keeps climbing.

What does "Display driver stopped responding and has recovered" mean?

Windows waited two seconds for the GPU to finish a task, decided it was frozen, reset the driver and restored the desktop. Each recovery is logged as Event ID 4101 under the Display source. One is normal. Many in a day call for a clean driver reinstall, and five inside a minute end in a 0x117 blue screen.