INACCESSIBLE_BOOT_DEVICE is a Windows stop error (BSOD) that appears during startup when Windows loads but cannot communicate with the disk it is installed on. It is common after a Windows update, a storage-driver change, a BIOS setting change, or when moving a drive to new hardware.
The symptom
Windows begins to boot, then shows a blue screen: “Your PC ran into a problem and needs to restart. Stop code: INACCESSIBLE_BOOT_DEVICE.” The PC then restarts and hits it again, often in a loop.
Common causes
- A recent Windows update installed a faulty storage driver.
- The disk controller mode in BIOS was changed (for example AHCI ↔ RAID/IDE).
- Corrupted system files or a damaged Boot Configuration Data (BCD) store.
- A failing SSD/HDD or a loose cable.
Fix 1 — Uninstall the most recent update
From the Recovery Environment (force three failed boots to reach it), go to Troubleshoot › Advanced options › Uninstall Updates and remove the latest quality update. This resolves the most common cause.
Fix 2 — Check the BIOS disk mode
Enter BIOS/UEFI and find the SATA/NVMe controller mode. If it was recently switched to RAID or IDE, set it back to AHCI (or vice-versa to match how Windows was installed). A mismatch here is a classic trigger.
Fix 3 — Repair system files and the BCD
Open Advanced options › Command Prompt and run, one at a time:
chkdsk C: /f /r— checks and repairs the disk.sfc /scannow— repairs corrupted system files.dism /image:C:\ /cleanup-image /restorehealth— repairs the Windows image.bootrec /rebuildbcd— rebuilds boot data.
Fix 4 — Roll back the storage driver
If it started right after a driver update, boot into Safe Mode (Advanced options › Startup Settings › Enable Safe Mode), open Device Manager, expand Storage controllers, and roll back or uninstall the recently changed driver.
When you can't reach any of these menus
If the blue screen loops so fast you can never get into the recovery menu, boot from an external recovery USB instead. It loads its own environment, so you can run the same chkdsk, sfc and bootrec repairs against your Windows drive from a clean, stable session — or pull your files off if the disk is failing.
How our RecoveryUSB handles this
Our recovery environment boots independently of your Windows install, so a BSOD loop can’t stop you from reaching the repair tools. Run the guided disk and boot repair, or back your data up first — both are one menu away.
Get a RecoveryUSBSkip the trial and error — use a ready-made RecoveryUSB
Every RecoveryUSB ships pre-built and tested, with a step-by-step guide. Free fast worldwide shipping.
Shop Recovery USBsFrequently asked questions
What does INACCESSIBLE_BOOT_DEVICE actually mean?
Windows loaded far enough to need the boot drive, but the driver or configuration it uses to talk to that drive is wrong or damaged, so it stops with this error to avoid corrupting data.
Can I fix INACCESSIBLE_BOOT_DEVICE without losing data?
Usually yes. Uninstalling the bad update, fixing the BIOS disk mode, or repairing the BCD all keep your files intact. Data loss only becomes a risk if the drive itself is failing.
It loops too fast to open the menu — what now?
Boot from a recovery USB. It gives you a stable environment outside the failing boot process where you can run the same repairs or rescue your files.