Windows BSOD Error 0x00000069 — IO1_INITIALIZATION_FAILED Fix

What Does This Error Mean?

The 0x00000069 blue screen means Windows failed to initialize the I/O (input/output) subsystem during startup. The I/O subsystem is responsible for all communication between software and hardware devices like disks, USB ports, and keyboards. Without it, Windows cannot function and crashes immediately. This is almost always caused by corrupted system files, a failing storage drive, or a bad driver loaded at startup.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows Server

Common Causes

Core Windows I/O system files have been corrupted by a bad update, interrupted installation, or disk error
The hard drive or SSD that Windows is installed on has developed bad sectors or is starting to fail
A low-level storage driver or disk controller driver is corrupted or incompatible
A third-party disk encryption or disk management tool has corrupted I/O subsystem files
The system registry hive files have been damaged, preventing the I/O manager from loading correctly

How to Fix It

Boot into Windows Recovery Environment (hold Shift while clicking Restart, or press F11 at startup). Go to Troubleshoot > Advanced Options > Startup Repair and let it run.

Startup Repair is designed to fix exactly this type of initialization failure. It can detect missing or corrupted I/O subsystem files and replace them automatically.
From the recovery Command Prompt, run a disk check: chkdsk C: /f /r /x — This checks your Windows drive for bad sectors and file system errors.

CHKDSK takes 15 to 45 minutes depending on drive size. The /r flag finds and repairs bad sectors. A high number of bad sectors indicates a failing drive that should be replaced soon.
Run DISM from the recovery Command Prompt to repair the Windows image: DISM /Image:C:\ /Cleanup-Image /RestoreHealth

DISM repairs the system component store. If I/O subsystem files were corrupted, DISM will restore them from a clean source.
Check whether a third-party disk tool (VeraCrypt, BitLocker alternatives, or disk partition managers) was recently installed or updated. If so, try booting with that driver disabled or uninstalled.

Low-level disk software runs early in the boot process and can interfere with Windows I/O initialization. Boot into Safe Mode (if possible) to disable third-party startup services.
If the drive passes CHKDSK but the error persists, use System Restore from the recovery environment: Troubleshoot > Advanced Options > System Restore. Choose a restore point from before the problem started.

System Restore reverts Windows registry and system files to a known-good state without affecting personal files. It is often the fastest fix when a specific update or software installation caused the error.

When to Call a Professional

If Startup Repair and CHKDSK both fail to resolve this error, the storage drive may be physically failing. A technician can run advanced diagnostics on the drive to determine if it is failing and whether data can be recovered. If the drive is failing, replacing it and reinstalling Windows is the correct solution — attempting to keep using a failing drive risks permanent data loss.

Frequently Asked Questions

What does the I/O subsystem do in Windows?

The I/O (input/output) subsystem is the part of Windows that manages all communication between programs and hardware devices. Every time a program reads a file from disk, sends data to a printer, or receives keyboard input, the I/O subsystem handles it. It is one of the first things Windows initializes at startup because almost everything else depends on it. If it fails to start, Windows cannot proceed and immediately stops.

How do I know if my hard drive is failing?

Signs of a failing hard drive include: clicking or grinding noises from the drive, very slow file operations, files that become corrupted for no reason, and a high number of errors reported by CHKDSK. You can also download CrystalDiskInfo (free) to check the drive's S.M.A.R.T. health data. A 'Caution' or 'Bad' health status in CrystalDiskInfo means the drive should be replaced as soon as possible.

Can this error occur on a brand-new PC?

Yes, though it is uncommon. A new PC can show this error if the Windows installation was corrupted during the initial setup process, or if the storage drive has a manufacturing defect. New drives can also arrive with bad sectors in rare cases. Run CHKDSK to check the drive health. If bad sectors are found on a new drive, the drive is defective and should be returned under warranty.