I'm facing a tough problem with the INACCESSIBLE_BOOT_DEVICE BSOD on a cloning project. Usually, this kind of error can be traced back to driver issues, especially with storahci or stornvme drivers, but I've tried all the standard fixes. I've checked the BIOS settings to ensure AHCI is enabled, and I even disabled VMD to get it to work right. I've also gone through the registry to make sure everything is in order and tried recreating the EFI system partition without success. What's strange is that this clone was from an HP laptop with an AMD chipset, and I'm trying to clone it to Intel machines—something seems to be causing issues specifically in this transition. I've verified that the necessary drivers are intact and even tried booting in safe mode, but nothing seems to work. I'm really curious to solve this problem rather than just going for a clean install. What else could be causing the INACCESSIBLE_BOOT_DEVICE BSOD? Any ideas on what I might be missing regarding AMD controllers or other potential barriers?
4 Answers
Going off your note about fresh installs working fine, it seems like there’s a strong possibility that the issue lies in the data you've cloned. The fact that clones from the AMD system to Intel aren’t working could indicate a driver issue, maybe something related to core Windows drivers that expect AMD hardware but are now trying to run on Intel gear. That's just my experience talking. Cloning from comparable systems usually avoids these issues, but man, you've got dedication for wanting to solve this!
Is this happening during the boot process or later, once Windows has loaded? If it's during boot, that usually points to some sort of corruption. Cloning isn't ideal if the hardware isn't similar, and that can definitely lead to headaches like these. It's not uncommon for a faulty storage drive to cause issues either, although you said everything checks out, right?
It's definitely occurring on boot. The health of the drives is fine, and the clone itself seems good. I know the usual fixes for SATA to NVMe transitions, but this time something deeper is causing chaos. It's an unusual case—very curious about what might be hidden that's causing this error.
What about the boot method? Is it set to UEFI or legacy BIOS? If it's UEFI, make sure your EFI entry is valid and updated for the new partition GUIDs. Sometimes switching between different boot types can solve these issues. Just throwing some thoughts your way!
Thanks for the tip! Yes, I've checked and confirmed that the ESP is all good—no issues there. Typically, just ensuring storahci and stornvme loads properly on boot is enough, but I'm looking for anything else unusual that might be blocking the boot process.
Have you checked for dump files? Those can be super helpful in analyzing BSOD issues. If you can boot into Windows normally or through Safe Mode, check C:WindowsMinidump for any crash logs. If you find some, zip them up and share for better troubleshooting! Also, consider adjusting your dump settings to ensure you're capturing more detailed logs in case any more BSODs pop up after that.
I appreciate that! It really does seem like an AMD-related driver issue since disabling everything AMD hasn’t helped much. I suspect there might be remnants in the registry that are tripping things up during boot. I’ll keep digging into it when I get back to work.