0x0000013C INVALID_IO_BOOST_STATE Fixes and Causes
0x0000013C usually points to a thread-exit or state-integrity failure; start by removing external devices, then test drivers, then firmware if the crash persists. Skip that order and you can spend hours on the wrong layer, while the same blue screen keeps coming back. This guide lays out a triage path that separates driver, firmware, and peripheral causes, then fixes the one actually failing.
This guide is part of our Windows BSOD stop codes: full list and fixes series.
What does 0x0000013C mean in Windows?
0x0000013C is the Windows stop code INVALID_IO_BOOST_STATE. It means a thread exited while its I/O boost state was invalid, and that state should be zero when the thread exits (per Microsoft support). (Microsoft Learn)
That points you toward state corruption, not a random crash. The fastest first check is whether the machine still boots normally, because that splits the problem into a driver path, a firmware path, or a device-isolation path.
Plain-English read of the stop code
Think of it as a cleanup failure. Something in the thread’s state did not get reset before exit, and Windows stopped the system to avoid running with broken thread data.
Why Windows may restart before you can read the screen
Windows often reboots immediately after a bug check because Automatic restart is enabled in Startup and Recovery. Turning that off lets you read the stop code and record the parameter values before the machine cycles again.
What usually causes 0x0000013C?
Common triggers may include recent driver changes, BIOS or firmware mismatches, and external storage or other attached hardware. Less commonly, storage stack problems or malware can contribute. The useful clue is not the crash alone; it is the last thing that changed.
Driver changes and bad device state
Outdated, corrupted, or recently replaced drivers can leave the thread in the wrong state when the system is shutting down work. That is why the first software fix is usually to update, reinstall, or roll back the driver tied to the last change.
BIOS or firmware mismatch
An incompatible BIOS version can keep the platform from handling power or device transitions cleanly. If the error started after a firmware update, or after a board was moved to older firmware, treat BIOS as a possible trigger rather than a last resort.
External drives and other attached devices
If the error appears after plugging in an external hard drive, dock, or USB storage device, isolate that hardware first. A problem in the storage path can look like a random blue screen when the real clue is the new device.
How do I stop Windows from auto-restarting after a BSOD?
Disable Automatic restart so the blue screen stays on screen long enough to read the stop code and parameters. That gives you the exact bug check value, the Arg1 through Arg4 fields, and the chance to spot whether the crash repeats after a specific device change.
Turn off automatic restart
- Open Control Panel > System > Advanced system settings.
- Under Startup and Recovery, select Settings.
- Clear Automatically restart, then choose OK.
What to write down from the blue screen
Record 0x0000013C, then note Arg1, Arg2, Arg3, and Arg4 exactly as shown. If you can reach a desktop later, open WinDbg and run !analyze -show <code> to display stop code information; Microsoft also notes that the code should be prefixed with 0x if radix is not 16.
Can Windows still boot?
If Windows still boots, start with recent software and driver changes. If it will not boot normally, use Safe Mode first. That split matters because the fastest fix path changes depending on whether you can reach the desktop.
If you can boot: first 3 actions
- Open Settings > Windows Update > Check for updates, then install every pending cumulative and driver update that appears.
- Open Device Manager, find the most recently changed device, then choose Update driver, Roll Back Driver, or Uninstall device.
- Run Windows Security > Virus & threat protection > Quick scan, then a full scan if anything is found.
If you can’t boot: first 3 actions
- Enter Safe Mode from Windows Recovery so only basic applications load.
- Unplug external drives, docks, and hubs before the next test boot.
- Use Device Manager in Safe Mode to remove the last driver you added or changed.
How do I fix INVALID_IO_BOOST_STATE BSOD?
The usual fix is to undo the most recent driver or hardware change first, then move to firmware only if the crash survives that test. Use Safe Mode if normal startup fails, because it loads basic applications only and gives you a cleaner place to remove the bad change.
Update, reinstall, or roll back the driver tied to the last change
- Open Device Manager.
- Check Display adapters, Storage controllers, Network adapters, and any device added recently.
- Choose Update driver first; if the issue began after an update, choose Roll Back Driver or Uninstall device, then reboot.
Use Safe Mode to remove the likely offender
- Hold Shift while selecting Restart.
- Go to Troubleshoot > Advanced options > Startup Settings > Restart.
- Choose the Safe Mode option, then remove the recent driver or app change.
Check Windows and scan for threats
- Open Windows Security.
- Select Virus & threat protection > Scan options.
- Run a full scan, then install pending Windows updates if the system is stable enough to do so.
Should you update BIOS for INVALID_IO_BOOST_STATE?
Yes, but only when the pattern points there. If the crash started after a BIOS change, or the machine is on older firmware and the error persists after driver cleanup, a BIOS update belongs near the top of the list. If the issue began after a new USB drive or a bad driver, do not jump to firmware first.
When firmware moves up the list
Put BIOS/firmware ahead of deeper repair only if the problem started right after a firmware flash, if you changed CPU or storage settings, or if the same crash survives driver rollback and external-device removal.
When to leave firmware alone for now
Leave it alone if the failure clearly tracks a recent driver install, a Windows update, or one external storage device. In those cases, the evidence points to software or device state before it points to firmware.
Can external drives trigger 0x0000013C?
Yes. External drives can trigger the error when the storage stack, a USB bridge, a dock, or a hub changes the device state at shutdown or resume. If the blue screen started after attaching a drive, treat that drive as a real suspect, not a coincidence.
Disconnect and reconnect one device at a time
- Shut down the PC.
- Unplug external hard drives, USB storage, docks, hubs, and card readers.
- Boot, then reconnect one device at a time until the crash returns.
What the pattern means
If the system is stable with all external storage removed, the likely fix path is the device, its cable, its enclosure, or the storage driver stack attached to it. If the crash returns only when one device is reconnected, that device becomes the first thing to update or replace.
Decision table: parameter pattern to next fix
The parameter fields are often one of the quickest clues in a 0x0000013C case. Arg1 appears to point to the thread, Arg2 appears to show the current boost state or throttle count, and Arg3 and Arg4 are reserved. Use the table below with the last hardware or driver change you made.
| Pattern in the crash data | Most likely path | First action |
|---|---|---|
| Arg1 has a thread pointer; Arg2 is nonzero | Driver or device-state issue | Roll back or uninstall the most recent driver in Device Manager |
| Crash began after a BIOS change or firmware update | BIOS/firmware mismatch | Restore known-good firmware settings or update to the vendor’s fixed BIOS |
| Crash starts when an external drive is connected | External storage or USB path | Remove the device, then test the PC without it attached |
| Arg3 and Arg4 are reserved, with no useful device clue | Broader software or stack problem | Run Safe Mode, then Windows Security and driver cleanup |
Use WinDbg when the screen is not enough
WinDbg’s !analyze command can show stop code details from a crash dump. Microsoft’s syntax example is !analyze -show <code>, which helps match the stop code to the parameter pattern before you change anything else. (Microsoft Learn)
What should I check first when 0x0000013C keeps happening?
Check the most recent change first: a driver, a BIOS update, or a newly attached device. If the machine can boot, remove external devices, inspect Device Manager, and run a malware scan. If it cannot boot, go straight to Safe Mode and disable automatic restart so you can capture the next failure.
Fast triage order
- Record the stop code and parameters.
- Remove external drives and peripherals.
- Undo the latest driver or firmware change, starting with the newest one.
Prevention: Keep a note of driver, firmware, and hardware changes before you apply them. That single habit makes the next 0x0000013C far easier to trace.
Frequently asked questions
What does 0x0000013C mean in Windows?
It is the bug check value for INVALID_IO_BOOST_STATE. The stop code means a thread exited with an invalid I/O boost state, and that state should be zero when the thread exits. If you can read the full screen, note Arg1 through Arg4 before rebooting.
How do I fix INVALID_IO_BOOST_STATE BSOD?
Start with external-device removal, then check the most recent driver change, then move to firmware only if the crash remains. The fastest path is usually Safe Mode for boot failures, or Device Manager for driver rollback on a desktop that still opens normally.
Is 0x0000013C a driver problem or hardware problem?
Most often it points to a driver or device-state problem first, not a failed part. Hardware enters the picture when the crash tracks one external drive, a dock, or a firmware change. If rollback and isolation fail, then storage or board-level troubleshooting moves up.
Why does my PC restart after showing 0x0000013C?
Because Automatic restart is enabled in Startup and Recovery. Turn it off in Control Panel > System > Advanced system settings so the BSOD stays visible long enough to record the code and the parameter values.
Can external drives trigger 0x0000013C?
Yes. Disconnect external hard drives, USB storage, docks, and hubs, then boot again. If the machine becomes stable, reconnect one device at a time to identify the one that wakes the crash back up.
Should I update BIOS for INVALID_IO_BOOST_STATE?
Only if the timeline points there. A BIOS update makes sense after a firmware change, or when driver cleanup and device removal do not stop the crash. If a recent USB or driver change explains the timing, fix that first and leave firmware for later.
