Fix IOCTL 0x4000000C Error on Windows 10/11

What Actually Triggers IOCTL 0x4000000C

You'll see this error mostly in disk management tools, like when you try to check drive health with wmic diskdrive get status or run a storage diagnostic. The short version: Windows sent a control code to a device driver, and the driver replied with nonsense or just gave up. The IOCTL code 0x4000000C maps to IOCTL_STORAGE_QUERY_PROPERTY in the storage stack — so it's almost always tied to a disk, USB, or storage controller driver not handling the query right.

I've seen this on Windows 10 22H2 and Windows 11 23H2 with external SSDs, internal NVMe drives, and even some USB flash drives. The trigger is often a driver that's stale, a cable that's flaky, or a device that's in a broken power state.

Fix #1: Quick Checks (30 seconds)

Don't skip this. Half the time it's a transient state.

1. Restart the computer. Not shutdown-and-start — a full restart. On Windows 11 with Fast Startup enabled, a shutdown doesn't reset the kernel pool that drivers use. A restart does. Hold Shift while clicking Restart if you want to be sure.
2. Check the cable. If you're using an external drive, unplug and reseat both ends. For internal drives, open the case and reseat the SATA or NVMe connection. Loose cables cause exactly this IOCTL failure.
3. Try a different USB port. If it's USB, avoid hubs. Plug directly into a port on the motherboard. USB controllers share bandwidth — a busy hub can drop IOCTL requests silently.

If the error persists, move to the moderate fix.

Fix #2: Update or Roll Back the Affected Driver (5 minutes)

This error screams “stale driver.” Here’s how to pinpoint the right one.

1. Press Win + X and open Device Manager.
2. Look for a device with a yellow exclamation mark. That's your culprit. Often it's under Disk drives, Storage controllers, or Universal Serial Bus controllers.
3. Right-click that device → Properties → Driver tab.
4. Note the Driver Version. Then click Update driver → Search automatically for drivers. Windows Update might find a newer one. If it says you're up to date, go to the manufacturer's site (Samsung, Western Digital, Intel) and grab the latest driver or firmware tool.
5. If the error started after a recent Windows Update, click Roll Back Driver instead. Windows 10 and 11 sometimes push generic drivers that don't handle IOCTL properly.

For example, I had this on a SanDisk Extreme Pro external SSD. The generic Microsoft driver from Windows Update broke it. Rolling back to the SanDisk driver fixed the 0x4000000C immediately.

Fix #3: Clear Stale Driver Cache and Reinstall (15+ minutes)

When updates and rollbacks fail, the driver cache itself might be corrupted. This is the nuclear option for the driver stack.

1. Open Device Manager again.
2. Right-click the problematic device → Uninstall device. Check the box that says Delete the driver software for this device. This purges the cached .inf and .sys files from C:\Windows\System32\DriverStore\FileRepository.
3. Restart the computer. Windows will try to reinstall the device automatically. If it picks the same bad driver, you'll need to intervene.
4. After restart, go to the manufacturer's website and download the correct driver manually. Install it with the downloaded .exe or via Update driver → Browse my computer for drivers → point to the extracted folder.

Why step 3 works: The DriverStore keeps multiple driver versions. Uninstalling with the checkbox forces Windows to forget the broken one. On next boot, it either uses a generic Microsoft driver (which at least won't cause the IOCTL error) or prompts you to supply one.

Fix #4: Check the Storage Controller Firmware (15 minutes)

If none of the above helped, the problem is deeper — the storage controller chip itself (often on the motherboard) has a buggy firmware that mishandles specific IOCTL commands.

1. Open Device Manager → expand Storage controllers.
2. You'll see something like “Intel Chipset SATA/PCIe RST Premium Controller” or “AMD SATA Controller”.
3. Right-click → Properties → Details tab → select Hardware Ids from the dropdown. Copy the value like VEN_8086&DEV_A382.
4. Search that hardware ID to find the exact chipset. Then go to your motherboard or laptop manufacturer's support page (Dell, HP, Lenovo, ASUS) and look for a storage controller firmware update. Some call it “IRST driver” (Intel Rapid Storage Technology) or “RAID driver.”

I fixed a persistent 0x4000000C on a Dell XPS 15 this way. The default Windows driver was fine, but the Intel IRST firmware had a known bug with NVMe query commands on that hardware revision. Updating the firmware to version 18.7.6 killed the error.

Fix #5: Run CHKDSK and SFC (5 minutes, but often unnecessary)

I'm putting this last because most people jump straight to chkdsk, but IOCTL 0x4000000C isn't a filesystem error — it's a driver communication error. Still, if the drive itself is failing, the driver may act up.

1. Open Command Prompt as Administrator.
2. Run chkdsk C: /f /r (replace C: with your problematic drive letter). This checks for bad sectors and fixes file system issues.
3. Then run sfc /scannow to repair system files.

If both pass clean, the drive hardware is probably fine, and you're back to driver or firmware as the root cause.

When to Give Up on DIY Fixes

If you've gone through fixes 1 through 4 and the error still appears every time you try a disk query, the hardware might actually be failing. Run a full diagnostic with the manufacturer's tool (like Samsung Magician, WD Dashboard, or SeaTools). If that passes, consider a clean Windows install — but only after backing up your data. A corrupt OS driver store can be faster to blow away than to fix.