Blue Screen 0x0000007B error_P2V and V2V Issues

V2V & P2V Migration Issues and Blue Screen 0x0000007B error

I use Disk2VHD utilities to converted Windows 2003 R2 Domain Controller machine’s physical SATA disk to vhd file and then use the vhd file to create vm on Hyper-v.

Everything so far it looks fine.

However the VM wouldn’t boot in Hyper-V, It continuously reboot and it didn’t even have the decency to turn blue.

After Pressing F8 during the boot and then selecting the option to “Disable automatic restart on system failure”; then the blue screen error code appeared and it was indicating that the issue caused by changing hard drive controllers of Windows OS (lack of a necessary driver required by Hyper-V HW)

I do have similar experience before with V2V, and I consider is a common issue with V2V and P2V especially when you migrate Windows XP / Windows 2003 machine.

bluescreen

I decided to write this post hopping to help someone have a similar issue

Solution

In order to solve this issue, I need access to registry of the VM, but my computer (vm) unable to boot!

In this case I have to mount the VHD to my system (or attach the VHD (drive) in another computer (VM) as a secondary)

Then follow the steps below.

1-Check the file system and Confirm Files Exist

windows\system32\drivers\intelide.sys

windows\system32\drivers\atapi.sys

 

2- Edit the Registry on a the mounted Drive

Locate the SYSTEM registry on the mounted drive and mount it (How to Edit the Registry on a Secondary Drive); then confirm Registry Entries Exist

HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Services\IntelIde

HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Services\PCIIde

HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Services\atapi

HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111

HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601

HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel

HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel

 

Create registry files mentioned below, and run it if there is missing Entries in order to regenerate Entries

 

Create file “IntelIde.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Services\IntelIde]

“ErrorControl”=dword:00000001

“Group”=”System Bus Extender”

“Start”=dword:00000000

“Tag”=dword:00000004

“Type”=dword:00000001

 

Create file “PCIIde.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\ITmugDC\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”

 

Create fileatapi.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\ITmugDC\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

 

Create file “dev_7111.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111]

“ClassGUID”=”{4D36E96A-E325-11CE-BFC1-08002BE10318}”

“Service”=”intelide”

 

Create file “dev_7110.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601]

“ClassGUID”=”{4D36E97D-E325-11CE-BFC1-08002BE10318}”

“Service”=”isapnp”

 

Create file “primary_ide.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Control\CriticalDeviceDatabase\primary_ide_channel]

“Service”=”atapi”

“ClassGUID”=”{4D36E96A-E325-11CE-BFC1-08002BE10318}”

 

Create file “secondary_ide.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\ITmugDC\ControlSet001\Control\CriticalDeviceDatabase\secondary_ide_channel]

“Service”=”atapi”

“ClassGUID”=”{4D36E96A-E325-11CE-BFC1-08002BE10318}”

 

When you have finished steps above, Boot the VM and it should boot successfully

If you have any question, feel free to contact me

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s