Article ID: 119295, created on Dec 24, 2013, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0
  • Virtuozzo hypervisor


Windows installed in the virtual machine crashes with Blue screen of Death STOP 0x7B


Usual causes of the "Inaccessible Boot Device" stop message are:

  • A device driver that the virtual machine's boot controller needs is not configured to start during the startup process.
  • A device driver that the virtual machine's boot controller needs is corrupted.
  • Information in the Windows registry (information related to how the device drivers load during startup) is corrupted.


The following steps can be attempted in order to fix the problem:

  1. Change interface type of the virtual machine's virtual hard disk from SATA to IDE, or vice versa, from IDE to SATA. (Please note that by default Windows Server 2003 does not support SATA interface.)

    You can change the interface type either from the PVA Panel or from CLI:

    # prlctl list MyVM -i | grep hdd
    Boot order: hdd0 cdrom0 fdd0 net0
      hdd0 (+) ide:0 image='/var/parallels/MyVM.pvm/harddisk.hdd' type='expanded' 65536Mb
    # prlctl set MyVM --device-set hdd0 --iface sata

    Try to boot the virtual machine

  2. Check that startup type for the necessary device drivers is properly configured:

    • Boot the virtual machine from an Windows installation image
    • Choose the Repair your computer option:

    • Choose Command Prompt from the System Recovery options:

    • Switch to main Windows boot drive. (Note: in some cases the actual "Windows boot drive" may be D: or some other letter depending on your particular setting. To check whether the drive you switched to contains WINDOWS folder list the contents of the disk by executing the dir command:

    Once you switch to correct driver, switch to the Windows\System32\config folder:

    cd Windows\System32\config
    • Load the SYSTEM registry hive:

    • Launch Registry editor to make necessary changes:

    • Find the following registry branches: HKEY_LOCAL_MACHINE/fix/ControlSet001/services/atapi, HKEY_LOCAL_MACHINE/fix/ControlSet001/services/intelide, HKEY_LOCAL_MACHINE/fix/ControlSet001/services/msachi And confirm that in every path the key Start has the value 0:

    • Repeat the previous step for HKEY_LOCAL_MACHINE/fix/ControlSet002/services/atapi, HKEY_LOCAL_MACHINE/fix/ControlSet002/services/intelide, HKEY_LOCAL_MACHINE/fix/ControlSet002/services/msachi branches

    • Do not forget to unload the hive:

    • Try to boot the virtual machine.

    NOTE: If you do not have a Windows installation image, you can connect the virtual hard disk to some other Windows virtual machine and carry out Step 2 from the second Windows installation.

  3. Boot the virtual machine from a Windows installation image (or connect the virtual hard disk to another Windows virtual machine) and check the disk for errors:

  4. Check the size and the modification date of the device drivers for boot controller:

    (Confirm that they were not modified recently and if possible compare the numbers with some other working Windows installation)

Search Words

bsod 7b


Inaccessible Boot Device

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF