Skip to content
PCDecoder
0x0000013CINVALID_IO_BOOST_STATEStop codeRarely reported

INVALID_IO_BOOST_STATE (0x13C): what it means and how to fix it

Updated Nov 7, 2026 · Checked against Microsoft documentation · How this page is made

Quick answer

Stop code 0x0000013C occurs when an operating system thread terminates while an input/output boost state remains active instead of resetting to zero. A faulty device driver or an incompatible hardware component typically triggers this condition. Checking Device Manager for device errors and rolling back recent driver updates resolves the issue on most systems.

What it means

Windows relies on threads to handle execution tasks across the kernel and device drivers. During input and output operations, the operating system can apply an I/O boost to prioritize work and prevent hardware bottlenecks. Once a thread finishes its work and exits, Windows expects that thread's boost state or throttle count to return to zero. The INVALID_IO_BOOST_STATE bug check carries the hexadecimal value 0x0000013C. Windows triggers this stop code when a thread exits while still holding an active, non-zero I/O boost state. Halting the operating system prevents data corruption that could occur if subsequent tasks run with inaccurate thread scheduling priorities. ### Crash Parameters. When this stop code appears, Windows logs four debugging parameters. Parameter 1 shows the memory pointer to the specific thread that had the invalid boost state. Parameter 2 displays the active boost state or throttle count that failed to clear. Parameter 3 and Parameter 4 are reserved by Windows for internal use. ### Underlying Causes. Kernel-mode device drivers cause most 0x13C blue screens. When a driver interacts with storage devices, peripherals, or network interfaces, it must properly manage I/O request packets. If a driver terminates unexpectedly or fails to clear its boost counter before exiting its thread, the kernel detects the discrepancy immediately. System testing tools can also provoke this condition. Running Driver Verifier on Windows versions 20150 through 25126 produces an invalid state error if the core system kernel ntoskrnl is selected for monitoring. Newly attached hardware or corrupted disk structures can also disrupt normal driver communications, leading to Uncleared boost states.

Common causes

  • A device driver exits a worker thread without resetting its I/O boost counter to zero.
  • Newly installed device drivers or system services conflict with Windows thread scheduling.
  • Driver Verifier monitors ntoskrnl on Windows versions 20150 through 25126.
  • Recently attached hardware components introduce communication errors into the device stack.
  • Malware or file system corruption damages kernel modules or driver configurations.

How to fix it

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

  1. Check Device Manager for driver errors

    Use this step first to find hardware devices reporting active driver problems.

    1. Open Device Manager from the Start menu or the Quick Link menu.
    2. Expand each hardware category to locate devices marked with a yellow exclamation point.
    3. Right-click any marked device and choose Properties.
    4. Review the Events tab to see details about driver load failures or device crashes.
    5. Select Update driver on the Driver tab, or download and install the current driver package from the hardware maker.
    Did this fix it?

  2. Remove recently added hardware and drivers

    Use this fix if crashes began right after plugging in new hardware or updating drivers.

    1. Disconnect any newly connected external devices such as adapters, external drives, or expansion cards.
    2. Check the manufacturer website to verify if compatibility patches exist for your hardware.
    3. Open Settings, navigate to Installed apps, and uninstall any third-party driver software or services added recently.
    4. Restart the computer to confirm whether the stop code stops appearing.
    Did this fix it?

  3. Inspect the System Log in Event Viewer

    Use this when you need to identify which driver or service triggered the crash.

    1. Open Event Viewer by searching for it in the Windows search bar.
    2. Expand Windows Logs in the left sidebar and select System.
    3. Look through the log for critical errors recorded in the exact time window of the blue screen.
    4. Identify the driver file or system service named in the error event details.
    5. Update or remove the software associated with that file name.
    Did this fix it?

  4. Reset Driver Verifier settings

    Use this if Driver Verifier was enabled for testing or if you use Windows builds 20150 to 25126.

    1. Open Command Prompt by right-clicking it and selecting Run as administrator.
    2. Enter the command verifier /reset and press Enter to clear all verification settings.
    3. Restart the computer to restore standard driver loading behavior.
    4. If testing must continue on Windows builds 20150 through 25126, open verifier, choose custom settings, and unselect ntoskrnl, or upgrade Windows past build 25126.
    Did this fix it?

  5. Run a complete virus scan

    Use this if you suspect malware may have altered disk structures or core files.

    1. Open your installed virus detection software.
    2. Verify that the scan configuration includes checks for the Master Boot Record.
    3. Run a full system scan across all storage drives.
    4. Quarantine or remove any threats detected by the scan, then restart Windows.
    Did this fix it?

Is it just you?

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

Checked Nov 4, 2026. Refreshed automatically every few days.

Sources

Frequently asked questions

What does stop code INVALID_IO_BOOST_STATE mean?

The stop code 0x0000013C means a Windows kernel thread terminated while its I/O boost state or throttle count was still active. Windows requires this value to be exactly zero whenever a thread exits.

Can Driver Verifier cause bug check 0x13C?

Driver Verifier can trigger invalid state errors on Windows versions 20150 through 25126 if ntoskrnl is selected for testing. Running verifier /reset in an elevated Command Prompt or updating past build 25126 resolves that condition.

How do I find out which driver caused error 0x13C?

Open Event Viewer to examine critical entries in the System Log from the time of the crash, or load the memory dump into WinDbg and run the command !analyze -v. In the debugger, Parameter 1 points to the faulting thread and Parameter 2 reveals the remaining throttle count.

More stop codes decoded