New
#1
Unusually unfixable BSOD preventing booting: Inaccessible Boot Device
The problem: system worked well for many months until an insertion of a regular Lexar USB somehow caused a reboot, but unknown to me with the BIOS reset. SATA RAID had reverted to SATA AHCI and the boot locked up. On reboot I checked BIOS, found the change, and reset back to RAID. From then on, I have been plagued with a BSOD – Inaccessible Boot Device (BSODibd). The RAID 1 drive has 4 standard partitions, BIOS boot/MBR, and a dual boot BCD (Win 10/Win 7)
I can’t afford a complete re-install (would take weeks to customize and activate everything), and I have no idea when/whether this might happen again. So far I’ve spent ages discovering that no one seems to have a real handle on this error.
What is not the problem or doesn’t work:
-not a disk signature collision (eg. boot with clone active) – all h38 BCD signatures match, and generalizing the BCD to {boot} doesn’t work either
-there are no hardware errors or partition errors and all data is accessible by WIN PE’s.
-Recovery USB command and other options don’t work: startup repair (automatic or manual), SFC, standard Bootrec, BCDboot commands including /rebuildBCD still cause BSODibd
-MBR repair does nothing since the MBR and boot recs check out fine, and I know the boot does access the BCD
-Third party software like Easy Recovery Environment doesn’t recognize the multi-partitions on the RAID and thinks it’s a screwed up GPT so it was useless, as were Dual Boot Repair, Easy BCD and others which all claim success at what they do but still result in the BSODibd.
What I just discovered does work to give me the multi-boot selection screen (even though it still leaves me high and dry with application installations and activations) is replacing just the Windows 10 registry hive (not the Windows 7 one) with an older version.
What exactly could the boot process be referencing in the registry that could cause a BSODibd under these circumstances, does anyone know?