STATUS_DISK_RESET_FAILED (0xC000016B) – Fix in 5 Steps

Quick answer: The culprit is almost always a dying drive, a loose SATA cable, or a corrupted storage driver. Unplug and reseat the drive's cables first – that fixes 40% of these cases.

The error 0xC000016B (STATUS_DISK_RESET_FAILED) shows up when Windows tries to reset a disk after a timeout or I/O error, and the reset fails. You'll see this during a black screen at boot, or as a blue screen with DISK_RESET_FAILED. I've seen it on Dell OptiPlex 3070s, HP ProDesks, and custom builds with cheap power supplies. The drive itself is usually the problem – but not always.

Fix Steps

1. Reseat the cables. Power down, unplug the SATA data cable and power cable from both the drive and the motherboard. Wait 10 seconds, plug them back in firmly. Boot up. If you hear a click or the drive spins up immediately, this was it.
2. Test with another cable. Swap the SATA cable with a known-good one. The data cable is the most common failure point after the drive itself. Don't bother testing the power cable unless you have a multimeter – just swap the SATA slot on the motherboard first.
3. Check the drive health. Boot from a USB with GParted Live or Windows installer. Open a command prompt and run chkdsk /f C: (replace C: with your system drive letter if it's different). If CHKDSK hangs or reports a ton of bad sectors, the drive is dying. Use CrystalDiskInfo (portable version) to check SMART attributes. If the Reallocated Sectors Count is over 10, or Current Pending Sector Count isn't zero, replace the drive now.
4. Update or roll back the storage driver. In Device Manager, expand Storage controllers. Right-click your controller (usually Standard NVM Express Controller or Intel SATA controller) and select Update driver. If the error started after a driver update, roll it back instead. I've had this error fixed by switching the driver to the generic Microsoft driver.
5. Disable the drive's write cache. In Device Manager, right-click the problem drive under Disk drives, go to Policies. Check Turn off Windows write-cache buffer flushing. Then reboot. This stops Windows from waiting on flush commands that the drive can't complete. It's a band-aid, not a fix – replace the drive soon.

If the main fix fails

If steps 1-5 don't work, try these:

• Boot in Safe Mode with Networking. If the error disappears in Safe Mode, the culprit is a third-party driver or a recent Windows update. Use sfc /scannow then dism /online /cleanup-image /restorehealth from Safe Mode.
• Disconnect extra drives. Unplug all non-boot drives. One bad secondary drive can cause the system to hang and generate this error. Boot with only the OS drive connected.
• Replace the SATA cable for the boot drive even if it looks fine. I've replaced cables that looked perfect and fixed the error instantly.
• Check the motherboard SATA port. Move the boot drive to a different SATA port. If the error moves with the port, you've got a bad port – use a different one.

Prevention tip

Set up SMART monitoring in BIOS (enabled by default on most boards). On Windows, run wmic diskdrive get status monthly. Replace any drive that reports Bad, Caution, or has a spinning rust age over 4 years – before it fails. Also, never cheap out on power supplies. A failing PSU can kill drives slowly and cause this exact error.