How to fix the WIN32K_CRITICAL_FAILURE (0x164) blue screen in Windows

WIN32K_CRITICAL_FAILURE, bug check 0x164, means Win32k, the kernel part of Windows that draws windows and handles input, found a state it could not survive and stopped the PC. Most often a graphics driver or an app that hooks into drawing is behind it. Roll back or cleanly reinstall the graphics driver first.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What WIN32K_CRITICAL_FAILURE (0x164) means

Microsoft's bug check reference says only this: the WIN32K_CRITICAL_FAILURE bug check has a value of 0x00000164, and it indicates that Win32k has encountered a critical failure. Win32k is the kernel mode part of the Windows graphical subsystem. It holds the window manager, the GDI drawing engine and the bridge to DirectX.

Since Windows 10, win32k.sys loads two helpers, win32kbase.sys and win32kfull.sys. That is why the stop screen or a crash tool may name any of the three. They are genuine Windows files, so the file named on the screen is the place where the fault was caught, not the program that caused it.

Why Win32k crashes: the causes, most common first

Win32k serves every program that opens a window, so the crash follows whatever handed it bad data. Crash analysis tools used on Windows forums describe 0x164 as possibly caused by the graphics driver. Real dumps also name the app that made the last call, such as a game streaming client.

Find the cause in the crash dump

Microsoft's only advice for 0x164 is to run the !analyze debugger command. It takes ten minutes and tells you which fix to start with, so do it if the PC still starts. Windows writes a small dump for every crash.

1. Open File Explorer and go to C:\Windows\Minidump. Each file is named by the date of the crash.
2. Install Microsoft's debugger: open Terminal and run winget install Microsoft.WinDbg.
3. Start WinDbg as administrator, select File > Open dump file and open the newest .dmp file.
4. Type !analyze -v in the command box and press Enter. Wait until the analysis ends.
5. Write down Arg1 under WIN32K_CRITICAL_FAILURE (164), then the lines PROCESS_NAME and IMAGE_NAME further down.

Microsoft's public list of Arg1 values stops at 0x10. Newer builds use more: dumps posted on the NVIDIA forum show 0x21 FREEING_INVALID_MEMORY and 0x1B USER_HANDLE_DOUBLE_FREE, with GeForceNOW.exe as the process. WinDbg prints the name of the type even when the public list does not.

How to fix the WIN32K_CRITICAL_FAILURE blue screen

Start with Fix 1 unless the dump or the timing points elsewhere. Fixes 2 and 3 cover crashes tied to one app or one update. Fix 4 is for a PC that no longer starts. Fixes 5 to 7 are the general repairs, in order of cost.

Fix 1. Roll back or cleanly reinstall the graphics driver

15 minutesLow riskCrashes happen in games, video playback or with several monitors, or they began after a graphics driver update.

Win32k hands every drawing call to the graphics driver through DirectX. A driver that returns a broken surface or region is the most common reason Win32k stops the PC with 0x164.

1. Right-click Start and select Device Manager.
2. Expand Display adapters, right-click your graphics card and select Properties.
3. Open the Driver tab. If the crashes began after a driver update and Roll Back Driver is available, select it, choose a reason and select Yes.
4. If the button is greyed out, download the newest driver for your exact card from NVIDIA, AMD or Intel, or from your laptop maker's support page.
5. Install it with the clean install option the installer offers, or select Uninstall Device first and then run the new installer.
6. Restart the PC and use it the way it used to crash. Step by step with screenshots: Update, roll back or reinstall a driver

Fix 2. Update or remove the app that was running when Windows crashed

10 minutesLow riskThe crash happens only while one program runs, or the dump's PROCESS_NAME names a program.

Win32k crashes in the middle of a call from a running program. In the GeForce NOW case on the NVIDIA forum, a newer version of the app stopped the 0x164 crashes on the same Windows build.

Programs that often sit close to Win32k are game streaming clients, game and chat overlays, screen recorders, remote desktop and remote support tools, and window or wallpaper tweakers. One of them can pass Win32k a handle it already freed, which is what the 0x1B and 0x21 types describe.

1. Note the app named in PROCESS_NAME, or the app you had open at each crash.
2. Update it to its newest version from its own website or store.
3. If it still crashes, turn off its overlay or capture feature in its settings and test again.
4. If that does not help, uninstall it for a test: Uninstall a program or app in Windows
5. If Arg1 was 0xA or 0xB, open Settings > Personalization > Fonts, select fonts you installed recently and select Uninstall.
6. If Arg1 was 0x5, update or reinstall the touchpad, pen or touch screen driver as in Fix 1.

Fix 3. Undo the latest Windows update or leave the Insider preview

15 minutesLow riskThe first crash came shortly after a Windows update, or the PC runs an Insider preview build.

A new build changes Win32k itself. On the NVIDIA forum, 0x164 crashes started on Canary build 27858 and Dev build 26120.3964 and did not happen on the build before.

1. Open Settings > Windows Update > Update history (on Windows 10: Settings > Update & Security > Windows Update > View update history).
2. Compare the date of the newest update with the date of the first crash.
3. If they match, select Uninstall updates and remove that update. Step by step: How to uninstall a Windows update
4. Pause updates for a week so it does not return before a fixed version arrives.
5. On an Insider build, open Settings > Windows Update > Windows Insider Program and turn on Stop getting preview builds, then send the dump through Feedback Hub.

Fix 4. Repair Windows from the recovery environment when it crashes on every start

30 minutesRead the warningThe stop code appears during startup, the desktop never loads, or the PC stays in Automatic Repair.

When Win32k fails before sign-in, Windows itself cannot load its own window system. The repair has to run from the recovery environment, which uses its own copy of Windows.

1. Turn the PC on and, when the logo appears, hold the power button until it shuts down. Do this twice; the third start opens Automatic Repair.
2. Select Advanced options > Troubleshoot > Advanced options.
3. Run Startup Repair (called Quick machine recovery on newer Windows 11 builds). Step by step: Run Startup Repair
4. If that fails, select Uninstall Updates > Uninstall latest quality update.
5. If that fails too, select System Restore and pick a point from before the first crash: Undo recent changes with System Restore
6. If you can reach Startup Settings, start in Safe Mode and roll back the graphics driver as in Fix 1: Start Windows or a Mac in Safe Mode

When every option in the recovery environment fails, create a Windows 11 USB drive with the Media Creation Tool on another PC. Boot from it and choose Repair your computer instead of installing. In a Microsoft Q&A boot loop case with 0x164, that is what got the PC working again.

Fix 5. Repair damaged Windows system files with DISM and SFC

20 minutesNo riskArg1 is 0x3, the crash happened during startup, or SFC has never run on this PC.

Win32k depends on many system files and API sets. Type 0x3 means a critical one is missing, and a damaged copy of win32kbase.sys or win32kfull.sys would also stop it.

DISM fetches clean copies of Windows components first, then SFC replaces damaged system files with them. Step by step with screenshots: Run DISM and SFC to repair Windows system files

In Terminal (Admin), one after the other:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

If Windows does not start, run SFC offline from the recovery environment's Command Prompt. Check the letter of the Windows drive with dir first, because it is often not C: there.

In the recovery Command Prompt (replace C: with the Windows drive):

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Fix 6. Rule out unstable hardware: memory, overclock and disk

60 minutes or moreLow riskStop codes change from crash to crash, NTFS_FILE_SYSTEM appears beside 0x164, or nothing above helped.

Win32k keeps its objects in memory. Bad RAM or an unstable overclock can corrupt them, and Win32k then finds a handle or region that makes no sense and stops.

1. Reset every CPU and GPU overclock to default, and turn off the memory profile (XMP or EXPO) in the BIOS for the test.
2. Test the RAM with the tool built into Windows: How to test your RAM with Windows Memory Diagnostic
3. Check the system disk for errors, especially if NTFS_FILE_SYSTEM also appeared: Check a disk for errors (chkdsk)
4. Update the BIOS and chipset driver from your PC or motherboard maker's support page.
5. If you added hardware before the crashes began, remove it and test again, as Microsoft's stop code checklist advises.

Hardware faults that Windows survives often leave a LiveKernelEvent in Reliability Monitor before a blue screen. Our guide to the LiveKernelEvent 124 error explains how to read those entries.

Fix 7. Reinstall Windows and keep your files

60 minutes or moreRead the warningEvery fix above failed and the dumps keep naming Win32k files with no clear app or driver behind them.

A reinstall replaces every Win32k file and the whole driver store at once. It removes a cause that the dumps could not name, while your personal files stay.

1. Back up your files and note the apps you will need to install again.
2. Open Settings > System > Recovery (on Windows 10: Settings > Update & Security > Recovery).
3. On Windows 11, select Reinstall now under Fix problems using Windows Update for an in-place repair that keeps files and apps, if your version shows it.
4. If that is missing or did not help, select Reset PC, then Keep my files and Cloud download.
5. After the reset, install the graphics driver from the card maker first, then your apps one at a time. Full method: Reinstall Windows without losing files

Still crashing: what to collect and whom to ask

Win32k belongs to Microsoft, but the bug usually sits in a driver or app that calls it. Collect the facts once, then send them to the vendor that the dump points at. On Microsoft Q&A, independent advisors ask for the Minidump files before they can say more.

• The three newest .dmp files from C:\Windows\Minidump, zipped.
• The Arg1, PROCESS_NAME and IMAGE_NAME lines from !analyze -v.
• Your Windows edition and build from Settings > System > About.
• Your graphics card and driver version from Device Manager.
• What you were doing at each crash: a game, a video, waking the PC, startup.

How to keep WIN32K_CRITICAL_FAILURE from coming back

Windows 10 left support on 14 October 2025. A PC that stays on it gets Win32k security and stability fixes only through Extended Security Updates, so moving to Windows 11 keeps those fixes coming.

Frequently asked questions

What is win32k.sys?

Win32k.sys is a genuine Windows kernel driver, stored in C:\Windows\System32. It is the kernel mode part of the window system: it manages windows, menus, mouse and keyboard input and the GDI drawing engine, and it passes graphics work to DirectX. On Windows 10 and 11 it loads two helpers, win32kbase.sys and win32kfull.sys. Do not delete or replace it. If you suspect damage, run DISM and SFC as in Fix 5.

What does win32k critical failure mean?

It means Win32k, the part of Windows that draws windows and handles input, checked its own data and found something it could not safely continue with. Rather than draw garbage or corrupt memory, Windows stops with bug check 0x164 and restarts. The cause is usually outside Win32k: a graphics driver, an app that hooks into drawing, a damaged font or system file, or unstable memory. The dump's Arg1 tells you which kind.

What is error 0x164 or 0x00000164?

0x164 is the number of the WIN32K_CRITICAL_FAILURE bug check, and 0x00000164 is the same value written with eight digits. You see the number in Event Viewer, in Reliability Monitor and in crash tools such as WinDbg, while the stop screen shows the name. Both point to the same problem and the same fixes. Search for the name or the number, the answer is this page.

Is WIN32K_CRITICAL_FAILURE different on Windows 11?

The code and its causes are the same on Windows 11 and Windows 10. What differs is the screen: on Windows 11 24H2 and later the stop screen is black instead of blue, and the recovery environment offers Quick machine recovery in place of Startup Repair on newer builds. Windows 11 also gets new Win32k code in every feature update, so crashes that start after an update are more common there.

Why do I get win32k critical failure on startup?

A crash before the desktop appears means Win32k failed while Windows loaded its window system, the graphics driver or a startup app. The usual reasons are a broken graphics driver, a bad update, or damaged system files. Let Windows open Automatic Repair, then try Startup Repair, uninstalling the latest update and System Restore, in that order, as in Fix 4. Safe Mode loads a basic display driver, which helps you remove a faulty one.

Can a game or GeForce NOW cause the 0x164 crash?

Yes. Any program that draws on screen calls Win32k, and a bug in that program or in its overlay can trigger the stop code. In a case on the NVIDIA forum, the GeForce NOW app crashed Windows 11 preview builds with 0x164, and a newer app version fixed it. If the dump's PROCESS_NAME names a game, launcher or streaming client, update that program first, then the graphics driver.

Is WIN32K_CRITICAL_FAILURE a sign of a virus?

Not usually. The stop code comes from Windows itself, and win32k.sys, win32kbase.sys and win32kfull.sys are signed Microsoft files. Malware that injects into other programs can make them crash, but nothing ties 0x164 to malware in particular. If you also see pop-ups, unknown programs or a disabled antivirus, run a full scan with Microsoft Defender. Otherwise, follow the driver and app fixes on this page.

Can bad RAM cause win32k critical failure?

It can, though it is not the most common cause. Win32k keeps its windows and drawing objects in memory, so a bit flip from faulty RAM or an unstable overclock can turn one into garbage. Signs of hardware are stop codes that change from crash to crash, crashes in many different programs, or errors in Windows Memory Diagnostic. Turn off XMP or EXPO for a test and run the memory test as in Fix 6.

I don't speak English. What should I do about this screen?

This page is about the stop code WIN32K_CRITICAL_FAILURE (0x164) in Windows, also asked as "como resolver?", "что делать" or "lỗi này sửa sao". In short: update or roll back the graphics driver first, then update the app you had open, then undo the latest Windows update. If the PC does not start, open the recovery environment and use Startup Repair. A browser translation of this page shows every step in your language.