Blue screen 0x0000007B boot error with 64-bit Windows 2003 virtual machine converted from physical machine.
I am running VMWare Converter Starter Edition version 3.0.0 build-39557 installed on a Dell PowerEdge 2950 (a couple of months old) running Windows Server 2003 Enterprise x64 R2 (version 5.2.3790, SP1 with all the latest updates). The server has SCSI RAID drives (2 separate arrays for a physical C: and 😧 drive).
The physical machine is a new clean installation of 64-bit Windows Server 2003 with no other software installed except for VMWare Server and Converter.
I am attempting to create a virtual machine from this machine to run in VMWare Server (version 1.0.1 build-29996) on the same physical machine. The conversion appears to succeed, but when I attempt to start the new virtual machine, it begins to boot, displays the Windows 2003 startup screen briefly, and then fails with a blue screen with the following error:
STOP: 0x0000007B (0xFFFFFADFD520F3C0, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)
I understand the "0x0000007B" means that it can't access the boot device for some reason. I have searched these forums and the knowledge base, but haven't found a solution to this problem.
I have been able to successfully convert and boot a 32-bit Windows Server 2003 physical machine as a virtual machine running in this same VMWare Server. I don't have any other 64-bit machines to test this with.
I am logged in directly to the console of the physical machine with the administrator account. I enabled virtualization in the BIOS. I have tried various combinations when building the virtual machine (customizing or not, fixed or variable disk sizes, importing both C: and 😧 drives or importing only the C: drive, etc). I have the SYSPREP files from the x64 installation disks locally on the server, and I have run SETUPMGR in this folder to create a SYSPREP.INF file. All of these various attempts have failed with the same boot error.
Is it possible to build a 64-bit virtual machine using VMWare Converter Starter Edition? Any suggestions on how to resolve this issue?
Could you post your exact process for implementing it?
All I did was booted the VM using BartPE, opened regedit clicked on hkey_local_machine, clicked on file -> load hive selected c:\windows\system32\config\system (which is the Windows 2003 Enterprise 64bit VM that is giving me the 0x0000007B error) I loaded the hive as SYSTEM2, I expanded SYSTEM2 -> ControlSet001 -> Control -> CrticalDeviceDatabase. I made a new key called pci#ven_1000&dev_0030 I then created a string named ClassGUID with the value data {4D36E97B-E325-11CE-BFC1-08002BE10318} i then created another string called Service with the value data symmpi
I then unloaded the hive
i rebooted the machine and told the VM virtual bios to boot from the HD it then began the infinite reboot loop.
I then went back in to BartPE to make sure the changes I made to the registry were still in there and it appears that they were.
Any suggestions?
thanks,
-Drew
.
You may also need to check if symmpi.sys is present in winnt\system32\drivers and hklm\system\controlset001\services has symmpi key present and start has a value of 0 (start on boot). You may need to import this from another working machine.
I built a small helper VM with win 2003 64, attached the c: drive of migrated/crashing VM as second drive. I was able to load hive and compare registries better.
btw the solution is on the same lines as MS kb314082 - 'more information' section
Woo hoo, it works
-Drew
Very nice ...
I have now a similiar problem with Windows Server 2008 (64bit).
I used VMWARE Converter 4.0 Beta. Source was VMWARE Workstation 6.5.
I get BSOD (STOP 7B)
Is there already a fix for Win2k8???
Best regards,
Volker
I'm having a simlar problem with Server 2008 64bit.
Used VMware converter and booted up the machine - that all worked fine but I also need to restore the system state to bring over a live AD. Using the WBADMIN command to resotre the system state causes the 07b error.
I have 32 bit 2003 servers that have restore the system states without any problems.
I'll try the DVD and the repair option now but hoping for a better fix than that
O.K. I've converted a ton of machines, desktops and servers. I ran into the same Blue screen 0x0000007B error on a VM created from a Dell Vostro 420 and have tried everthing in this thread to fix it. After weeks of trying everthing under the sun I installed the latest build of converter and was looking at the settings and found out by default it uses "preserve disk controller type" by default. I changed this to VM SCSI and ran converter one more time and the machine boots up fine.
for 2003 Converter 3.0.3 is recommended - it does not mess up the settings like 4.0.1 usually does
_________________________
VMX-parameters- WS FAQ -[ MOAcd|http://sanbarrow.com/moa241.html] - VMDK-Handbook
You also find me in the support crew of PHD Virtual Backup
I had exact same problem.
I removed SCSI Controller added IDE Controller and attached its VMDK, No more blue screen
Use Vmware Vcenter converter.
Had the same problem after transferring Windows Server 2003 from Hyper-V to ESXi 6.5:
Solved doing the following:
Mount VHD or VMDK as IDE drive in VMWare Workstation 15.X+
It should boot into OS without BSOD
You can now install vmscsi drivers following VMware Knowledge Base
You can take this opportunity to install VMWareTools
Export to OVA/OVF
Deploy OVA/OVF to ESXi host