A technician is troubleshooting a Windows 11 workstation that displays a Stop Code screen with INACCESSIBLE_BOOT_DEVICE during startup immediately after a motherboard firmware update reset the UEFI/BIOS setup to factory defaults. The technician verifies that the NVMe solid-state drive is physically detected in the UEFI setup utility. Which of the following actions should the technician take first to resolve this boot error?
- Reconfigure the storage controller mode (AHCI vs. RAID/NVMe) in the UEFI settings to match the original OS configuration.Answer
- BBoot into the Windows Recovery Environment (WinRE) command prompt and execute bootrec /fixmbr to rebuild the Master Boot Record.
- CBoot into WinRE and execute sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows to repair system file corruption.
- DAccess Task Scheduler within Computer Management via WinRE to re-enable startup hardware services.
Answer
Reconfigure the storage controller mode (AHCI vs. RAID/NVMe) in the UEFI settings to match the original OS configuration.
The correct option addresses the root cause of the error. When UEFI firmware settings are reset to defaults, storage controller modes (such as Intel VMD/RAID vs. Standard AHCI) often revert. If the Windows storage stack driver expects RAID/VMD mode but the controller is operating in AHCI mode (or vice versa), Windows cannot initialize the boot device driver and fails with the Stop Code INACCESSIBLE_BOOT_DEVICE. Reverting the controller mode in UEFI resolves the mismatch.
Step-by-Step Solution
Key Concept
Troubleshooting Windows UEFI storage controller mode mismatches causing INACCESSIBLE_BOOT_DEVICE Stop errors.
Estimated Time:2m 0s