Skip to content
PCDecoder
0x00000093INVALID_KERNEL_HANDLEStop codeWidely reported

INVALID_KERNEL_HANDLE (0x93): what it means and how to fix it

Updated Oct 19, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

The INVALID_KERNEL_HANDLE stop code indicates that Windows kernel code or a driver attempted to close an invalid or protected handle using NtClose. A problematic third-party driver or service is the most frequent trigger. Updating or rolling back recent drivers is the best initial fix.

What it means

Windows uses references called handles to track open system resources such as files, devices, and memory objects. When drivers and kernel-level components finish working with a resource, they inform Windows by calling a function named NtClose to release that handle.

The INVALID_KERNEL_HANDLE stop code (0x00000093) occurs when kernel code—such as a hardware driver, network redirector, or background server component—tries to close a handle that is invalid. A handle is considered invalid if it points to a resource that does not exist or has already been closed. The crash also happens if code attempts to close a handle that Windows has specifically flagged as protected from closure.

Parameter Details

When this crash occurs, Windows records diagnostic parameters on the blue screen:

  • If the second parameter is 0, code attempted to close a protected handle.
  • If the second parameter is 1, code attempted to close or reference an invalid handle.
  • If the fourth parameter is 1, bad handle detection was enabled, and a driver attempted to reference an invalid kernel handle.

Windows deliberately triggers a stop error under these conditions to safeguard system stability. Allowing kernel code to close the wrong handle could corrupt open files, crash unrelated hardware devices, or leave the operating system in an unpredictable state.

Common causes

  • A device driver passed an invalid or previously closed handle to NtClose.
  • Kernel code attempted to close a handle marked as protected.
  • A driver referenced an invalid kernel handle while bad handle detection was active.
  • A corrupted driver or conflicting system service mishandled resource management.

How to fix it

Safest and most likely fixes first. Readers' answers to "Did this fix it?" reorder this list over time.

  1. Update or roll back recent device drivers

    Use this fix if the blue screen started appearing after installing new hardware or updating an existing driver.

    1. Right-click the Start menu icon and select Device Manager.
    2. Expand the category containing your most recently updated device, such as Display adapters or Network adapters.
    3. Right-click the specific device and select Properties.
    4. Select the Driver tab.
    5. Click Roll Back Driver if the option is available, or click Update driver to check for a newer release.
    Did this fix it?

  2. Install pending Windows updates

    Use this fix to obtain bug fixes from Microsoft for core kernel components and certified driver updates.

    1. Open Settings from the Start menu.
    2. Select Windows Update, or Update & Security on older releases.
    3. Click Check for updates.
    4. Allow Windows to download and install all available updates.
    5. Restart your computer when prompted.
    Did this fix it?

  3. Scan system files with System File Checker

    Use this fix to repair corrupted core system drivers and system libraries.

    1. Type cmd into the taskbar search box.
    2. Right-click Command Prompt in the results and choose Run as administrator.
    3. Type sfc /scannow and press Enter.
    4. Wait for the verification phase to reach 100 percent.
    5. Restart your PC if the tool reports that it found and repaired damaged files.
    Did this fix it?

  4. Boot into Safe Mode to remove conflicting software

    Use this fix if the crash happens repeatedly during normal startup, preventing you from using the desktop.

    1. Hold the Shift key while clicking Restart in the Start power menu.
    2. Choose Troubleshoot on the recovery screen.
    3. Select Advanced options, then choose Startup Settings.
    4. Click Restart.
    5. Press 4 or F4 to start Windows in Safe Mode.
    6. Open Installed apps in Settings and uninstall recently added software or drivers that may be causing conflicts.
    Did this fix it?

Is it just you?

13 Microsoft Q&A threads discuss this. Most recent activity:

Checked Oct 13, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What is a kernel handle in Windows?

A kernel handle is an internal reference number that Windows assigns to open resources like files, hardware devices, or system objects. Drivers and kernel programs use handles to interact with those resources.

Is error 0x93 the same as 0x00000093?

Yes. Windows stop codes are written in hexadecimal notation, and 0x93 is simply a shortened representation of 0x00000093.

Can bad RAM cause an INVALID_KERNEL_HANDLE crash?

While the error is primarily a software bug where code calls NtClose improperly, failing memory can occasionally corrupt handle values stored in RAM and lead to this crash.

More stop codes decoded