When you convert an already installed Win7 Image in to a Virtual Image or if you do a complete PC restore from one machine to another- you might face the 0x0000007B Stop error. This will happen in a loop and you have to disable the Auto Restart to see the blue screen error code. When this error appears windows does not create any memory crash dump because a device driver that the computer boot controller needs is not configured to start during the start-up process.The hitch is that drivers are there but not enabled in an effort to improve boot performance. Only the one required driver (Ide, AHCI, RAID) is loaded to save the boot time.
After trying couple of things for hours I came up with following steps that consistently worked for me:Boot to Baremetal Windows ( If it’s a VHD then mount the VHD)Depending on what interface you have, you need to change the start value of corresponding registry entry to load the driver. If the value is 3, that driver would not load. So if you are going from AHCI to IDE, which is the case in most of P2V then open regedit.
After trying couple of things for hours I came up with following steps that consistently worked for me:Boot to Baremetal Windows ( If it’s a VHD then mount the VHD)Depending on what interface you have, you need to change the start value of corresponding registry entry to load the driver. If the value is 3, that driver would not load. So if you are going from AHCI to IDE, which is the case in most of P2V then open regedit.
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\IntelIde]
Change the data for value "Start" from "3" to "0".6a.Also repeat for: HKLM/System/CurrentControlSet001/Services/ and edit the "Start" parameter to the corresponding value from the list:
Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3
Also check these two reg entries
[HKEY_LOCAL_MACHINE\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111] "ClassGUID"="{4D36E96A-E325-11CE-BFC108002BE10318}" "Service"="intelide"
[HKEY_LOCAL_MACHINE\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601] "ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}" "Service"="isapnp"
Aliide = 3
Amdide =3
Atapi = 0
Cmdide = 3
iaStorV = 3
intelide = 0
msahci = 3
pciide = 3
viaide = 3
Also check these two reg entries
[HKEY_LOCAL_MACHINE\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111] "ClassGUID"="{4D36E96A-E325-11CE-BFC108002BE10318}" "Service"="intelide"
[HKEY_LOCAL_MACHINE\ControlSet001\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7110&cc_0601] "ClassGUID"="{4D36E97D-E325-11CE-BFC1-08002BE10318}" "Service"="isapnp"
Thank you for the useful article. I am sure I am not the only one who has such kind of problems with W7. I started thinking of m&a data room service for my business after watching that BSOD.
ReplyDeletethanks, I'm guessing plenty of people would just give up after a few tries. When I had this problem I spent a long time researching and decided to post here hopping somebody will find it useful. 1 is make me happy :)
Deletem&a room to avoid seeing bsod? would be a nightmare if you did get bsod and can't access it physically, even through vm will be a headache.
This comment has been removed by a blog administrator.
ReplyDelete