After performing a P2V of a Windows 2003 or Windows XP machine to Hyper-V, a STOP 7B BSOD is presented on boot.
To resolve this issue, complete the following steps.
First, confirm that the necessary drivers are present by booting into the AppAssure BootCD
Take note of any missing drivers or registry keys from the above steps. If any of these files are missing they can be created or imported. Hyper-V needs these drivers and services to boot and an absence of this information will result in the 0x7B STOP error.
The following is the information to create the missing registry keys:
pci#ven_8086&dev_7111
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]
“ClassGUID”=”{4D36E96A-E325-11CE-BFC1-08002BE10318}”
“Service”=”intelide”
pci#ven_8086&dev_7110&cc_0601
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601]
“ClassGUID”=”{4D36E97D-E325-11CE-BFC1-08002BE10318}”
“Service”=”isapnp”
primary_ide_channel
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel]
“Service”=”atapi”
“ClassGUID”=”{4D36E96A-E325-11CE-BFC1-08002BE10318}”
secondary_ide_channel
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel]
“Service”=”atapi”
“ClassGUID”=”{4D36E96A-E325-11CE-BFC1-08002BE10318}”
Required Registry Entries
intelide.reg
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelIde]
“ErrorControl”=dword:00000001
“Group”=”System Bus Extender”
“Start”=dword:00000000
“Tag”=dword:00000004
“Type”=dword:00000001
pciide.reg
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\PCIIde]
“ErrorControl”=dword:00000001
“Group”=”System Bus Extender”
“Start”=dword:00000000
“Tag”=dword:00000003
“Type”=dword:00000001
“ImagePath”=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\
00,2e,00,73,00,79,00,73,00,00,00
“DisplayName”=”Standard IDE/ESDI Hard Disk Controller”
atapi.reg
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\atapi]
“ErrorControl”=dword:00000001
“Group”=”SCSI miniport”
“Start”=dword:00000000
“Tag”=dword:00000019
“Type”=dword:00000001
“DisplayName”=”Standard IDE/ESDI Hard Disk Controller”
“ImagePath”=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\
00,73,00,79,00,73,00,00,00
Required Driver Files
windows\system32\drivers\intelide.sys
windows\system32\drivers\pciide.sys
windows\system32\drivers\atapi.sys
Located within C:\Windows\Driver Cache\i386, you should be able to extract these drivers from the driver.cab file. The expand command will allow you to extract from this .cab file. Verify that the driver.cab file is located in the above directory.
In a command prompt, issue the following command:
expand "c:\windows\driver cache\i386\driver.cab" /f:driver.sys c:\windows\system32\drivers
For c:\, verify the proper volume letter for your scenario.
The /f:driver.sys is telling the command to find the specific driver (for instance the pciide.sys) and to extract it to the directory following the switch. The "driver.sys" should be modified to match the missing drivers that have been discovered.
Much of the information was pulled from the resources below and can be referenced if necessary:
If the above efforts should fail, FixIDE from Foolish IT may work: https://www.foolishit.com/free-tech-tools/fixide/
Windows Registry Disclaimer:
Quest Software does not provide support for problems that arise from improper modification of the registry. The Windows registry contains information critical to your computer and applications. Make sure you back up the registry before modifying it. For more information on the Windows Registry Editor and how to back up and restore it, refer to Microsoft Article ID 256986 “Description of the Microsoft Windows registry” at Microsoft Support.
