Restart Your Graphics Card Without Rebooting

The screen has frozen or gone black. The music is still playing, and you are about to hold the power button. Before you do, there is a key combination that fixes a surprising share of these.

Windows will restart the display driver on its own, without touching anything you have open.

I looked up what Windows actually does when you press it. It turns out to be the same recovery the machine already runs by itself, several times a minute if it has to.

The shortcut, and what it is not

Three lines, and then the detail.

⚡ Documented by Microsoft on its blank screen troubleshooting page: "Press Windows + Ctrl + Shift + B to reset the graphics driver. You should hear a beep or see a screen flicker if successful."

⭐ That is four keys held together. Windows key, Ctrl, Shift, and B.

⛔ It does not reboot your PC. It does not close anything either. Your documents stay open and unsaved work stays unsaved.

⚠️ A beep or a flicker means it worked. Silence and no flicker means Windows did not act, which is itself information.

What Windows already does without asking you

This is the mechanism, and knowing it tells you when the shortcut will help.

Documented by Microsoft in its timeout detection and recovery documentation: "TDR is a feature in Windows that detects when the graphics card takes longer than expected to complete an operation. It then resets the graphics card to prevent the entire system from becoming unresponsive."

⭐ So Windows has been doing this for you all along. The shortcut just asks for it on demand.

⚡ Microsoft states what you see when it works: "The only visible artifact from hang detection to recovery is a screen flicker."

⚠️ And what it tells you afterwards, in its own words: it displays a message saying "Display driver stopped responding and has recovered."

Two seconds is the whole rule

The number behind every one of these.

Documented by Microsoft: "The default timeout period in Windows is two seconds."

⛔ If your graphics card cannot finish or hand back a task inside two seconds, Windows decides it is frozen. Not slow. Frozen.

⚡ Ours, and the registry here is bare. The delay value is not set at all. So the documented two second default is what applies here.

⭐ Yours is almost certainly the same. That value only exists if somebody put it there.

Ours: what the history on this machine says

A measurement, and this time it is a clean nil.

Ours, counted in the System log here. There are zero display driver recovery events on this machine.

⛔ So the recovery has never fired here. This page cannot show you one happening. It is described from Microsoft's documentation rather than reproduced.

⚡ Count yours. Terminal, one command:

Get-WinEvent -FilterHashtable @{LogName='System'; ID=4101} -MaxEvents 20

⭐ Every recovery Windows has performed comes back with a date. A list of them tells you a lot. Clustered around one game or one app, they name your culprit for you.

Five in a minute and the sixth is a blue screen

Almost nobody knows this, and it explains a crash people find baffling.

Documented by Microsoft, and it is worth reading twice: "the OS bug-checks the computer on the sixth (or more) GPU hang when it detects that five (5) or more GPU hangs and subsequent recoveries occur within one (1) minute."

⚠️ So Windows only tolerates so much. Five recoveries inside a minute, and it stops recovering. It blue screens instead.

⭐ That is why a game can flicker a few times and then crash the whole PC. The flickers were the warnings.

⛔ If you are seeing repeated flickers, the shortcut is not your fix. The stop code that follows is where the real answer is.

When the shortcut helps and when it does nothing

Four cases, sorted honestly.

⚡ A black or frozen screen with the PC still alive: try it. Sound still playing or the fan still working is your sign the machine is fine.

⭐ A screen stuck after waking from sleep: try it. This is the case it was really made for.

⛔ A completely dead machine with no sound and no lights: it will do nothing. Nothing is running to accept the keys.

⚠️ A picture that is present but wrong, like flickering or tearing, needs something else. Flicker has its own list of causes.

Do not change the timeout

The advice you will find, and why to leave it alone.

⛔ Raising the delay does not fix a graphics card that hangs. It only makes Windows wait longer before rescuing you.

⚠️ And the recovery that follows is what keeps your desktop alive. Turn that down and a hang becomes a hard freeze instead.

⭐ Ours, and marked as ours: the value is untouched on this machine and it should stay untouched on yours unless a piece of professional software specifically asks for it.

⚡ Fix the cause instead. A driver update, an overheating card, or one app that hangs every time.

Status: read against Microsoft's blank screen page and its TDR documentation, 26 August 2026, on Windows 11. Registry values and the event count were read here. ⛔ No recovery has ever fired here.

What does Windows + Ctrl + Shift + B actually do?

It restarts the display driver without restarting your PC. Microsoft documents it on its blank screen troubleshooting page. It says you should hear a beep or see a screen flicker if it worked. Nothing you have open closes, and unsaved work stays unsaved but intact.

Is it safe to press if nothing is wrong?

Yes. Your screen flickers for a moment. Everything else carries on. Windows performs the same reset by itself whenever the graphics card takes too long, so pressing it deliberately is not doing anything the machine does not already do on its own.

Why does my screen flicker and then blue screen later?

Because Windows only tolerates so many of these. Microsoft documents that five or more graphics hangs and recoveries inside one minute make the sixth one bug-check the machine instead. Those earlier flickers were your warning, and the stop code afterwards is where the real cause is.

Should I increase TdrDelay to stop this happening?

No, unless a specific professional application tells you to. Raising it only makes Windows wait longer before rescuing your desktop, and lowering the recovery behaviour turns a survivable hang into a frozen PC. Fix the driver or the heat instead.

The Short Version

• Windows + Ctrl + Shift + B restarts the display driver without a reboot.
• Microsoft documents it, and a beep or a flicker means it worked.
• Nothing closes and your unsaved work survives it.
• Windows already does the same reset by itself when the card takes too long.
• The limit is two seconds, and it is not set on most machines including this one.
• Count your own recoveries with the one-line command above.
• Five hangs inside a minute and Windows blue screens on the sixth.
• Raising the timeout is not a fix. It just delays the rescue.

Where to Next

Press the four keys next time the screen freezes but the PC is clearly alive. It costs you a flicker and it fixes more of these than it has any right to.

Then run the one-line command and count how many recoveries your machine has already done. Mine has done none. That is why this page quotes rather than shows.

If that list is long and clustered around one app or one game, you have found your cause without any guessing.

If the flickers end in a crash, stop treating the flicker and read the stop code instead. That is where the actual fault gets named.

If the shortcut has rescued you from something, say what you were doing at the time in the comments. I would like to know which situations it saves people from most.