Fix STATUS_CANT_WAIT (0XC00000D8): I/O Blocking Error

Quick answer

Reboot your PC. If that fails, update your storage and graphics drivers, then run a memory test.

What's happening here?

STATUS_CANT_WAIT (error code 0XC00000D8) means a thread tried to wait for I/O in a context where blocking isn't allowed. This is a kernel-mode issue, usually from a buggy driver (like a RAID controller or NVMe driver) or bad memory. I've seen it most often on Windows 10 and 11 machines after a driver update or a hardware change. The system literally says "I can't pause for this disk operation right now" and crashes or hangs.

The key thing to understand: this isn't a user-application bug. It's deep in the system. So your first instinct should be to check drivers and hardware, not uninstall apps.

Fix steps

Reboot your PC. Sounds too simple, but I've seen this error pop up from a temporary driver state that a clean boot fixes. After the restart, check if the error repeats.
Update critical drivers. The usual suspects: storage controllers (AHCI, NVMe, RAID), graphics, and chipset. Go to your motherboard or OEM support site (Dell, HP, Lenovo) and grab the latest. Don't rely on Windows Update alone—it often gives you old versions. I recommend the Intel or AMD driver update utilities for chipset drivers.
Roll back recent driver updates. If the error started after a Windows Update or driver install, open Device Manager, right-click the device (likely under Storage controllers or System devices), go to Properties > Driver > Roll Back Driver. You'll need to pick a restore point if that option's grayed out.
Test your RAM. Bad memory can corrupt kernel threads. Use the Windows Memory Diagnostic tool—type mdsched.exe in the Run box (Win+R), choose "Restart now and check for problems." Let it run for a full pass (may take 30 minutes). If errors show up, replace the faulty stick.
Check for disk errors. Open an admin Command Prompt (right-click Start > Command Prompt (Admin)) and run chkdsk C: /f /r. It'll schedule a check on next reboot. Let it run—it can take hours on large drives. Bad sectors or disk controller issues can trigger 0XC00000D8.
Disable fast startup. This Windows feature can mess with driver initialization on some systems. Go to Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable > uncheck "Turn on fast startup (recommended)" > Save changes. Reboot and test.

Alternative fixes if the main ones fail

Run SFC and DISM. System File Checker can repair corrupted system files. In an admin Command Prompt, run sfc /scannow. Then run DISM /Online /Cleanup-Image /RestoreHealth to fix the component store. I've seen DISM fix driver corruption that SFC missed.
Uninstall third-party antivirus. Some security software (like old versions of McAfee or Norton) hooks into kernel I/O and can trigger this error. Uninstall it completely, then use Windows Defender as a temporary test. If the error stops, switch to a different AV vendor.
Check for overheating. Overheating CPUs or storage controllers can cause intermittent I/O failures. Use HWMonitor to check temps under load. Anything above 85°C on a CPU or 70°C on an NVMe drive is a red flag. Clean dust out of your case and ensure fans spin.
Update UEFI/BIOS. This is a last resort because it's risky (power outage during update = bricked PC). But some motherboard revisions fix compatibility issues with newer drivers. Check your motherboard or PC vendor's support page for a BIOS update.

Prevention tip

Don't use generic Windows drivers for critical hardware. Always download chipset and storage drivers directly from your motherboard maker (Intel, AMD, or OEM). Also, keep your RAM stable—if you overclock it, run MemTest86 overnight once a month. A little prevention saves you from hours of headaches later.

One more thing: if this error keeps happening despite all steps, you might have failing hardware. Replace the drive or motherboard. I've seen cases where a flaky SSD controller caused STATUS_CANT_WAIT every hour until swapped out.