AskTechGurus Get help now →

PC Hardware & Performance

INACCESSIBLE_BOOT_DEVICE after changing the storage mode in BIOS

INACCESSIBLE_BOOT_DEVICE

After switching the drive mode between RAID and AHCI in the BIOS — common on new Dell and HP laptops — Windows won't boot and shows a blue screen.

What you’re seeing

  • A blue screen with the stop code INACCESSIBLE_BOOT_DEVICE immediately after a BIOS setting was changed.
  • The laptop booted fine until the SATA operation or storage mode was switched between RAID (Intel RST/VMD) and AHCI.
  • Windows installation media or imaging tools could not see the drive, which is why the setting was changed in the first place.
  • Changing the setting back may or may not restore normal startup.

Common causes

Every environment is different, but these are the causes our engineers find most often:

  • Windows loads only the storage driver that matches the mode it was installed under, so switching modes leaves it without a driver for its own boot drive.
  • Many new business laptops ship with Intel RST or VMD enabled, which requires a specific driver that generic Windows media does not include.
  • A reimage or fresh install was performed in one storage mode and the BIOS was later changed to the other.
  • A BIOS update reset the storage mode to its factory default without anyone noticing.
  • BitLocker detected the firmware change and the boot process now fails or stops at a recovery prompt.

Why it matters

This error typically lands at the worst moment, in the middle of setting up a new laptop for a hire who starts tomorrow or reimaging a machine that needs to go back out. Each attempt to fix it by trial and error risks a full reinstall, and if BitLocker is enabled the wrong change can lock the drive behind a recovery key. For IT teams rolling out a batch of identical laptops, the same mismatch can repeat across every unit until the underlying driver or image issue is solved.

How AskTechGurus fixes it

Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.

Tell us what’s happening

Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.

A certified engineer diagnoses it

A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.

Fixed and verified with you

The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.

Pay only when it’s resolved

Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.

Frequently asked questions

Is the drive broken?

No. This error almost always means Windows cannot talk to a healthy drive because of the storage mode setting, not that the hardware has failed.

Will we have to reinstall Windows?

Usually not. In most cases Windows can be brought back up with its existing apps and files, and we confirm which mode the installation expects before making any change.

Will this happen on the rest of our new laptops?

It can if they share the same image or deployment process. We explain what caused the mismatch so the remaining machines can be set up correctly.

Still stuck? Let a pro take it from here.

AskTechGurus connects you with vetted, US-based systems engineers who fix this every day. No call centers, no scripts, no surprise bills.

Start now →