You're in the middle of copying a large file to an external drive, or maybe you're running a game that loads assets from a second SSD. Then the screen freezes, and you get a blue screen with STATUS_BUS_RESET (0x8000001D). Or worse, the system just locks up and you reboot to find the drive missing in Explorer.
This error is Windows telling you that a device on an I/O bus (usually SATA, NVMe, USB, or even Thunderbolt) had to be reset because it stopped responding. The bus controller tried to kick it and that failed too. It's not a software bug in the usual sense—it's a hardware or driver communication breakdown.
What Actually Causes This
The I/O bus reset happens when a storage controller or USB host controller doesn't get a response from a device within a certain timeout. Windows resets the whole bus to recover. If that reset also fails, you get the bug check. The usual culprits, in order of frequency:
- Faulty cable or loose connection—SATA cables are cheap and fail silently. USB cables with broken shielding do the same.
- Power delivery issues—some external drives need more juice than a single USB port provides. Or your PSU is underpowered for multiple drives.
- Driver bugs—especially the storage controller driver or USB host controller driver that came with Windows.
- Failing drive or controller—the device itself is going bad.
- Aggressive power management—Windows puts a drive to sleep and it doesn't wake up in time.
I've seen this mostly on desktops with multiple drives and on laptops with a USB-C dock. It's rare on a single, well-connected internal drive. So that's your first clue: if you're using a dock or a hub, start there.
Fix It Step by Step
I'm going to list fixes from easiest to hardest. Do them in order. Most people stop at step 3 and it's solved.
Step 1: Check and Replace Cables
Shut down the machine. Unplug the drive that's causing trouble. Inspect the cable—look for bent pins, kinks, or frayed ends. Then swap it with a known good cable, preferably shorter. For internal SATA drives, use a different SATA port on the motherboard too. After you've swapped, boot up and see if the error reappears. You expect it not to for at least a few days.
Step 2: Update or Roll Back Storage Controller Drivers
Open Device Manager. You can get there by right-clicking the Start button and selecting Device Manager. Expand Storage controllers. Right-click your controller (like Standard SATA AHCI Controller or Intel Chipset SATA/PCIe RST Premium Controller) and choose Update driver.
Pick Search automatically for drivers. If Windows finds nothing, go to your motherboard or laptop manufacturer's website and grab the latest chipset and storage drivers. On a Dell, that's the Dell Support page. On a custom rig, it's the motherboard page.
If you recently updated the driver and the error started after that, roll it back instead. Go to the Driver tab and hit Roll Back Driver. You'll see a prompt. After applying, you'll need to reboot.
Step 3: Turn Off USB Selective Suspend and Link Power Management
This is a big one for external drives. Windows aggressively powers down USB ports and SATA links to save energy. That's fine for a mouse, not for a drive that's mid-transfer.
Open the old Control Panel (type control in the Run box, which you open with Win+R). Go to Power Options. Click Change plan settings next to your active plan, then Change advanced power settings.
Scroll to USB settings → USB selective suspend setting. Set it to Disabled. Click Apply and OK.
Also, open Device Manager again. Under Universal Serial Bus controllers, you'll see entries like USB Root Hub. Right-click each one, go to Power Management and uncheck Allow the computer to turn off this device to save power. Do that for all of them, including the ones under USB Host Controllers.
For NVMe drives, you want to disable ASPM (Active State Power Management) in the BIOS. Reboot and press Del or F2 to enter BIOS. Look for something like PCIe Link State Power Management or ASPM. Set it to Disabled. Save and exit.
Step 4: Check Disk Health and Run chkdsk
A failing drive can trigger a bus reset. Open a Command Prompt as administrator (right-click Start, choose Command Prompt or Terminal). Run:
wmic diskdrive get statusYou want to see OK for all drives. If you see Bad, you need to replace that drive.
Also run chkdsk C: /f (replace C: with the drive letter that's acting up). You'll be asked to schedule it for next reboot. Answer Y and restart. Let it run—it can take an hour on a large drive.
Step 5: Update BIOS/UEFI Firmware
Motherboard manufacturers fix bus controller bugs all the time. Check your board's support page and see if there's a BIOS update newer than the one you're running. You can see your current BIOS version by typing msinfo32 in the Run box and looking under System Summary → BIOS Version/Date.
Download and flash per the manufacturer's instructions. After flashing, enter BIOS and load defaults, then re-enable XMP/EXPO if you had it on. This rarely makes things worse, but it's not the first thing to try.
Step 6: Reseat or Replace the Device
If it's an internal drive, power off, unplug the drive, and reseat it firmly in the slot or bay. Check the drive's power connector—those SATA power connectors are notorious for not clicking all the way in. For external drives, try a different port on the machine (preferably a rear USB port on a desktop, as those are directly on the motherboard).
If it still crashes, the drive or the controller is at fault. I'd try the drive in a different machine. If it causes the same issue there, it's the drive. If not, it's your motherboard's controller.
Still Failing? Check These
If you've done all of the above and you're still staring at 0x8000001D, there's one more thing to try: turn off write caching for the specific drive. In Device Manager, expand Disk drives, right-click the problem drive, go to Policies, and uncheck Enable write caching on the device. This can help if the drive's cache is the issue.
Also, check the Windows Event Viewer. Open it by typing eventvwr.msc in Run. Go to Windows Logs → System. Look for events with source disk or stornvme around the crash time. Those will tell you which device or port is failing. The event log doesn't lie.
If the drive is under warranty, I'd RMA it at this point. A drive that consistently causes bus resets is a ticking time bomb. Back up your data now, before you lose it.
The real fix for most people is a combination of steps 1 and 3. I've fixed maybe a dozen machines with this exact error, and it was always a bad cable or power management. Don't overthink it. Do the simple stuff first.