Few blue screens are as alarming as INACCESSIBLE_BOOT_DEVICE. Your PC powers on, the Windows logo flickers, and then everything stops on that grim blue panel. The message is blunt: Windows cannot reach the drive it needs to boot from. The good news is that this error is usually fixable, and in many Nigerian cases it is not even a sign of a dead drive — it is a confused boot configuration that a few recovery steps will sort out.
This guide walks you through the fixes in the right order, from the quickest checks to the more serious possibilities. If your machine refuses to boot at all rather than throwing this specific error, start with our broader guide on what to do when a PC will not boot. And if the failure began moments after the lights went out, our piece on recovering a PC that will not boot after a power cut is the more direct companion to this one.
What INACCESSIBLE_BOOT_DEVICE actually means
When Windows starts, it expects to find a specific drive, in a specific mode, holding the boot files it loaded last time. INACCESSIBLE_BOOT_DEVICE appears when that expectation is broken. The drive might be physically present but invisible to Windows, the storage mode might have changed, or the boot files themselves might be damaged. The error does not tell you which of these it is — that is what the diagnostic order below is for. Work through it from the top and you will almost always land on the cause without guessing.
Start in BIOS: detection and boot order
Before touching Windows, confirm the hardware is even visible. Restart and enter BIOS/UEFI (usually Delete or F2 during startup). Then check two things:
- Is the boot drive detected? Look for your NVMe or SSD listed under storage or boot devices. If it appears, good. If it does not appear at all, this is no longer a software problem — it is a seating or hardware fault, and our guide on an NVMe that disappears from BIOS covers that path in detail.
- Is it first in the boot priority? A BIOS reset or a flat CMOS battery can shuffle the boot order so the PC tries a USB stick or a secondary drive first. Set your Windows drive to the top of the list, save, and reboot.
Check the storage controller mode (AHCI vs RAID)
This is one of the most common hidden causes. Windows is installed against a particular storage mode — almost always AHCI on modern builds. If that mode gets switched, Windows can no longer talk to the drive the way it learned to, and you get this exact blue screen.
- A recent BIOS update can reset the SATA configuration back to a default that differs from your install.
- A BIOS reset after a power event can flip the mode between AHCI and IDE or RAID.
- The fix: enter BIOS, find the SATA or storage configuration, and set it back to AHCI. If you genuinely installed Windows in RAID mode, set it back to RAID instead. Save and reboot.
Repair corrupt boot files — the Nigerian power-cut culprit
Here is where local conditions matter most. If NEPA cuts the power while Windows is part way through an update, the boot configuration data (the BCD) can be left half written and corrupt. The next boot then fails with INACCESSIBLE_BOOT_DEVICE. This is one of the leading causes we see, and it is very fixable.
- Create or borrow a Windows installation USB, boot from it, and choose Repair your computer rather than Install.
- Run Startup Repair first. It is automatic and resolves a large share of post-power-cut cases on its own.
- If Startup Repair cannot finish, open the Command Prompt from the recovery menu and rebuild the BCD manually, then reboot.
- To stop this happening again, put the PC on a UPS or inverter so a power cut never interrupts an update. Our guide on PCs that will not boot after a power cut goes deeper on prevention.
Roll back a bad driver or recent update
If the error started right after a Windows Update or a new storage driver, the driver itself is the suspect. Windows is loading something it cannot use to reach the boot drive.
- Boot into Safe Mode through the recovery menu's startup settings.
- Uninstall the recent update or roll back the storage driver to the previous version.
- Reboot normally and confirm the error is gone before applying any updates again.
When the drive itself is failing
If BIOS struggles to detect the drive intermittently, or the error keeps returning after every fix, the drive may be dying. Do not keep fighting it — protect your data first.
- Learn the warning signs in our guide on how to tell if a hard drive is failing.
- If you can still reach the drive, image or clone it onto a healthy one before it gives out entirely — our Windows-to-new-NVMe clone walkthrough shows the safe way to do it.
- Once your data is safe, replace the failing drive and restore from the clone or a fresh install.
Frequently Asked Questions
Will I lose my files fixing this error? Usually not. The first four fixes — BIOS detection, AHCI mode, Startup Repair, and driver rollback — leave your data untouched. You only risk data loss if the drive is physically failing, which is why imaging it early matters.
Why did this happen right after the power went out? A power cut during a Windows update can leave the boot files half written and corrupt. This is genuinely one of the most common causes we see in Nigeria, and Startup Repair from a Windows USB resolves a large share of them.
I changed a BIOS setting and now it will not boot — what do I undo? The most likely culprit is the SATA or storage mode. Go back into BIOS and set it to AHCI (or RAID if that is how Windows was installed), then confirm your boot drive is detected and sitting first in the boot order.
The One Thing to Remember
Work the order, do not panic. INACCESSIBLE_BOOT_DEVICE almost always traces to one of five things — BIOS not seeing the drive, a changed storage mode, corrupt boot files, a bad driver, or a failing drive — and you find the cause by checking them top to bottom rather than reinstalling Windows in frustration. In Nigeria, suspect the power-cut-and-corrupt-BCD path early, because Startup Repair fixes it more often than not.
Still staring at a blue screen, or not sure your drive is healthy enough to trust? Tell us what happened and we will help you recover it on our contact page — and if it turns out the drive is on its way out, our configurator will help you spec a reliable replacement build that shrugs off the next NEPA outage.