Restored Machines fail to boot with BSOD 0x0000007B (4034802)

After a successful rollback by Bare Metal Restore (BMR) or Virtual Export to a supported Hypervisor, the restored machine fails to boot. Boot fails with stop error code STOP: 0x0000007B.

0x0000007B errors usually result from one of the following reasons:

• Storage device drivers or settings
• Hardware issues
• Boot volume issues

1. Boot from a Bootable CD or Windows Recovery Environment (WinRE), open a Command Prompt, type regedit, and press Enter.
2. Highlight HKEY_LOCAL_MACHINE (HKLM) and from the Registry Editor menu select File \ Load Hive...
3. In the Load Hive window browse to C:\Windows\System32\Config, select SYSTEM, and click Open.
4. In the next Load Hive window enter Key Name Restored_HKLM and click OK.
5. Expand to HKLM\Restored_HKLM\ControlSet001\Services, find each of the following Key Names, and set their Start values according to the restore types listed below. NOTE: not all Key Names may be present in all operating systems:
   1. Restored to a Hyper-V or VMware hypervisor:
      1. aliide 3
      2. amdide 3
      3. atapi 0
      4. cmdide 3
      5. iastorv 3
      6. intelide 0
      7. msahci 3
      8. pciide 3
      9. viaide 3
      10. LSI_SAS 0
   2. Restored to a physical machine with native SATA adapter:
      1. aliide 3
      2. amdide 3
      3. atapi 0
      4. cmdide 3
      5. iastorv 3
      6. intelide 3
      7. msahci 0
      8. pciide 0
      9. viaide 3
      10. LSI_SAS 3
   3. Restored to a physical machine with RAID controller:
      1. aliide 3
      2. amdide 3
      3. atapi 0
      4. cmdide 3
      5. iastorv 3
      6. intelide 3
      7. msahci 0
      8. pciide 3
      9. viaide 3
      10. LSI_SAS 3
6. When done, highlight Restored_HKLM and from the Registry Editor menu select File \ Unload Hive..., click Yes.
7. Close the Registry Editor and restart your machine. You should now have a successfully booting restored Windows Server.
   

Should all of these combinations fail, you may need to enable as many storage drivers as possible to allow for the newly created machine to boot up. In order to do this, enable all "SCSI Miniport" group services. This creates a large overhead for loaded drivers, but ensures all registered drivers will be available to the kernel during system load. To do this:

1. Highlight the Services key under HKLM\Restored_HKLM\ControlSet001, right-click on Services and select Find...
2. Search for SCSI Miniport.
3. For each result, change the Start value to 0.
4. Press F3 to find the next result.
5. Repeat steps 3 & 4 until all SCSI Miniport values have been modified.
6. Highlight  Restored_HKLM and from the Registry Editor menu select File \ Unload Hive..., click Yes.
7. Close the Registry Editor and restart your machine. You should now have a successfully booting restored Windows Server.

In case the problem still persists, it is likely because your storage device will not work with any of the generic drivers or even the proprietary drivers included in the restored Windows image. In such cases, it is necessary to inject the third-party storage driver to the offline Windows image. This will require for us to copy the driver files (generally .INF and .SYS, not an executable file) to a USB or optical drive and, once booted into the WinRE environment, load it using either PEImg (for Windows versions prior to Windows 7 / Windows Server 2008 R2) or DISM (Windows 7 / Windows Server 2008 R2 and afterwards).

1. Boot from a Windows Recovery Environment, open a Command Prompt, type diskpart, and press Enter.
2. Type list volume and press Enter. Note which volume contains the restored OS and which one is your USB or optical drive containing the third-party driver.
3. Type exit and press Enter.
4. If restoring an OS prior to Windows 7 or Windows Server 2008 R, go to step 5. Otherwise go to step 6.
5. Restoring an OS prior to Windows 7 or Windows Server 2008 R2:
1. If the WINDOWS directory is not named WINDOWS, then rename it as such: rename C:\foldername C:\WINDOWS (where C: is the restored OS drive letter).
2. Create a dummy folder in the root of the restored drive called users: mkdir users
3. Run PEImg on the desired INF file: peimg.exe /inf=INF_FILE C:\windows (replace C: with the restored OS drive letter, replace INF_FILE with the complete path to the third-party driver INF file).
4. Delete users if created at sub-step 2: rmdir users
5. Rename WINDOWS back to what it was if renamed at sub-step 1: rename C:\WINDOWS C:\foldername (where C: is the restored OS drive letter).
6. Restoring an OS equal to or newer than Windows 7 / Windows Server 2008 R2:
1. Run DISM on the desired INF file: dism /Image:C:\ /Add-Driver /Driver:X:\ /Recurse (where C: is the restored OS drive letter and X: is the USB / optical drive letter where your driver files reside).
2. Hit Enter and it should find the drivers within the USB / optical drive and install them.
7. Type exit and press Enter, then click the Restart button. You should now have a successfully booting restored Windows Server.