Windows BSOD 0x7B Inaccessible Boot Device
This is an issue I have run into a few times. It can be as simple as allowing Windows to do an automated ‘Startup Repair’, chkdsk/r and/or SFC (offline mode.) But if this is happening because you just cloned or repaired a damaged disk, you may be suffering from a bad HD driver.
The BIOS usually has 3 SATA operating modes: IDE, AHCI or Raid. Each one, in turn, has its own hardware driver within Windows. During initial installation, Windows determines which mode you are using and disables the unused ones.
The trick is to take the unbootable HD out of the original computer and attach it (internally or USB) to a functioning Host computer. Using the Regedit program on the Host, load the SYSTEM hive from the unbootable drive and set the “Start” value to “0” for these three keys:
(Remember, because you are modifying an external hive, HKEY_LOCAL_MACHINE will be replaced by whatever name you provided when loading the external hive. I named the external System Hive HLM in this example.)
Unload the hive from the Host Regedit and the close Regedit. You can then ‘Safely Remove’ the drive and return it to its original computer.
Before letting the system boot into Windows, go into the BIOS and change the SATA operating mode to one of the 2 other modes (I prefer RAID to AHCI or AHCI to Raid) Save the BIOS settings and try booting.
Anytime you clone a drive that uses Intel iaStor drivers, you will likely notice slow (usually bordering on insanely slow) hard drive performance on the newly cloned drive. Re-install the Intel iaStor drivers.