VMware Communities
niewoo
Contributor
Contributor

Windows 7 Guest: STOP 0x0000007B

Looks like this has been discussed before - I coudn't find explicitely which driver I should pre-load though. I'm trying to convert my old laptop to run on my new laptop as a guest under vmware workstation. I have a VHD with the old guest os, but when trying to launch the guest I get the 7B BSOD. The guest is Win7 x64 ... which storage driver should I pre-load on the old laptop before trying this procedure again?

Alternately, should I just try one of the tools that do P2V conversion? I have both machines running - so I'm willing to try whatever is easiest.

24 Replies
RDPetruska
Leadership
Leadership

It may be easist to run the VMware Converter on the image - and just choose the Reconfigure stage (the image creation has already been done).  This *should* update the VM to use the correct drivers for the VMware-specific virtual devices (especially the hard disk controller, which is what is giving this error).

Reply
0 Kudos
niewoo
Contributor
Contributor

ok - thanks.

Reply
0 Kudos
niewoo
Contributor
Contributor

I'm getting an error trying the converter. Burried in the log file on the source machine:

"building partition list: can't have more then one active partition on a disk"

Is this because of the 100MB system partition? I tried to not include this in the conversion, but then I get a warning that there is no system disk.

Thanks,

Nick.

Reply
0 Kudos
niewoo
Contributor
Contributor

I gave up on the built in converter (seems like it doesn't support Windows7) and used the standalone conversion tool. I was able to image everything, but I get the same BSOD, so both paths have ended up in the same place. I guess I need to figure out what driver is failing - in Safe Mode the OS boots until CLASSPNP.SYS is loaded.

Reply
0 Kudos
niewoo
Contributor
Contributor

After a bunch of work, this is what I tried:

- Task: Perform P2V from Win7 x64 Enterprise to Win7 x64 Enterprise

- Installed standalone converter on Destination. Could not get this to connect to Source machine

- Installed standalone converter on Source. Managed to get image to convert to Destination

- Upon boot, received BSOD 7B

- Researched KB and found article http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&e...

- Tried intsalling vmscsi on Source - just got error that this is invalid driver (I think because its not 64bit)

- Then tried enabling LSI_SAS on source (note: select SCSI on HDD option, Auto seems to pick IDE)

- Now standalone converter on Source kept getting "Internal Error" upon conversion

- Re-installed standalone converter on Source and try again

- Success finally ...

A bunch of stuff I don't know why it kept failing, but got it to work eventually.

Reply
0 Kudos
vazquezm
Contributor
Contributor

Hello Everyone;

I created a rescue disk(boot dvd backup) from my laptop dell and tried to create with those DVDs a virtual machine, when VM is booting I got same error 0x0000007B, I have read other post and I believe this issue can be solve changing some parameters or change the regestry in windows, I boot with a rescue disk and I was able to open a command window.

in the vmx file the IDE parameter is

ide0:0.present = "TRUE"

ide0:0.fileName = "Other.vmdk"

Any Ideas?

Thank you

Reply
0 Kudos
continuum
Immortal
Immortal

Hi

read my notes http://sanbarrow.com/p2v2008r2.html
and post the vmx-file


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
vazquezm
Contributor
Contributor

I found also this link _http://iamrobertsworry.livejournal.com/791047.html but when I try to unload the hive I got access denied in regedit

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "8"

scsi0.present = "TRUE"

memsize = "4096"

ide0:0.present = "TRUE"

ide0:0.fileName = "Other.vmdk"

ide1:0.present = "TRUE"

ide1:0.autodetect = "FALSE"

ide1:0.deviceType = "cdrom-raw"

floppy0.startConnected = "FALSE"

floppy0.fileName = ""

floppy0.autodetect = "TRUE"

ethernet0.present = "TRUE"

ethernet0.connectionType = "nat"

ethernet0.wakeOnPcktRcv = "FALSE"

ethernet0.addressType = "generated"

sound.present = "TRUE"

sound.fileName = "-1"

sound.autodetect = "TRUE"

pciBridge0.present = "TRUE"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge4.functions = "8"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge5.functions = "8"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge6.functions = "8"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

pciBridge7.functions = "8"

vmci0.present = "TRUE"

hpet0.present = "TRUE"

displayName = "Other"

guestOS = "other"

nvram = "Other.nvram"

virtualHW.productCompatibility = "hosted"

powerType.powerOff = "hard"

powerType.powerOn = "hard"

powerType.suspend = "hard"

powerType.reset = "hard"

extendedConfigFile = "Other.vmxf"

ide1:0.fileName = "D:"

ethernet0.generatedAddress = "00:0c:29:cd:35:40"

vmci0.id = "1137521984"

tools.syncTime = "FALSE"

uuid.location = "56 4d 98 a4 fc 89 8f 09-6b ac cc 9c 43 cd 35 40"

uuid.bios = "56 4d 98 a4 fc 89 8f 09-6b ac cc 9c 43 cd 35 40"

cleanShutdown = "TRUE"

replay.supported = "FALSE"

vhv.enable = "TRUE"

replay.filename = ""

ide0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.pciSlotNumber = "16"

ethernet0.pciSlotNumber = "32"

sound.pciSlotNumber = "33"

vmci0.pciSlotNumber = "34"

ethernet0.generatedAddressOffset = "0"

vmotion.checkpointFBSize = "33554432"

disable_acceleration = "TRUE"

bios.forceSetupOnce = "FALSE"

ide0:0.mode = "independent-persistent"

Reply
0 Kudos
vazquezm
Contributor
Contributor

Continuum:

I fixed the issue follow your article "Patching - easy variant" and link http://iamrobertsworry.livejournal.com/791047.html.

Your article gave me the hint that all changes must be done in the new key that you are creating and unload the new key instead system hive.

In sumary I did these steps:

On the target platform boot the newly created VM into the Windows 7 Recovery CD.
After boot is finished click on the CMD-button and run regedit.
Select HKLM and then Menu > File > Load Hive.
Browse to the Windows-directory on the virtualdisk > system32\config and select the file SYSTEM.
When asked for a name enter p2v.
Then find the key 

HKLM\p2v\ControlSet001\services\LSI_SAS

and set the start type to REG_DWORD 0
Also I reviewed that other keys were set according to http://iamrobertsworry.livejournal.com/791047.html

Then select HKLM\p2v and click Menu > File > Unload Hive. )here is where I was failing because I was trying to unload system key instead p2v
You can close regedit now and restart.

Thank you.

Reply
0 Kudos
batequeixo
Contributor
Contributor

Hi niewoo,

I am doing exactly the same, for the second time. The first I attempted steps found on research and ended up getting in worse shape. This second attempt I want to get it right.

Could you elaborate more precisely on this topic:

"Then tried enabling LSI_SAS on source (note: select SCSI on HDD option, Auto seems to pick IDE)"

Thanks!

Reply
0 Kudos
batequeixo
Contributor
Contributor

Here is the fix that worked for me. It's almost like surgery so follow these steps precisely for good results!

This procedure assumes the following:

  1. You used some kind of cloning software (e.g. Clonezilla or VMware Converter) to produce an image of the Windows 7 OS
  2. You restored the image as a VM and, upon booting, the 'blue screen of death' (BSOD) displays with errors that read: "STOP 0x0000007B" and, in between parenthesis, the second group of hex code reads 0xFFFFFFFFC0000034. This is an indication that the boot process is crapping out due to incompatible or mismatch device drivers or handlers.
  3. The PC is a Dell Latitude E6420 running 64 bits linux OS, with VMware Workstation 8.0.3 on top.  Regardless, these instructions should work for most hardware.

Remember: if you get to the BSOD, the imaging portion went well!  All we need to do is satisfy Win7 regedit requirements.

The fix:

  • Mount the Win7 DVD in VMware Player (or Workstation) and boot to it.
  • At the first screen (Language Selection), hit Shift-F10 for a command prompt.
  • Run Regedit.
  • Load the system hive from the VM's disk:

1. Highlight HKEY_LOCAL_MACHINE
2. File > Load Hive
3. Select < c: > \Windows\System32\config\system
4. Regedit will ask for a Key name: Name it something like "p2v"
5. Expand HKEY_LOCAL_MACHINE\asdf\ControlSet001\Services\intelide
6. 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
7.
Then find the key: HKLM\p2v\ControlSet001\services\LSI_SAS and set the start type to REG_DWORD 0
9. Navigate up from the key to the hive (''p2v''), then hit 'File > Unload Hive'.  In other words, select HKLM\p2v and click Menu > File > Unload Hive. 10.Exit regedit and reboot the VM.
11. "Voila! Hear the angles sing!" --> from 'iamrobertsworry'

Thanks enormously to 'Continuum', 'Andrew Cohen' and 'Roberts Worry' for unknowlingly helping to put these instructions together.

References:

http://iamrobertsworry.livejournal.com/791047.html

http://communities.vmware.com/message/2027796
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&e...


Reply
0 Kudos
deafgrischa
Contributor
Contributor

Thank you batequeixo,

It was exactly my problem and your answer was perfect for me, it was the solution also for Workstation 7.1.5, Windows 7 Host & Guest.

Reply
0 Kudos
abirhasan
Enthusiast
Enthusiast

Thats great !!

abirhasan 
Reply
0 Kudos
djmorse
Contributor
Contributor

THANK YOU batequeixo!!! These steps worked to perfection!!! I was getting STOP 7B after VMware Converter failed at 98%.  I was afraid I'd need to do another P2V, which takes hours, but following your excellent guide I did a successful P2V using:

On Guest (physical on Dell Inspiron 1750)

- VMware Converter 5.0.0-470252

- Windows 7 Pro 32-bit SP1

- Default settings on P2V (which was IDE unfortunately, guess I should have chosen SCSI??)

On Host:

- VMware Workstation 8.0.4 build 744019

- Win7 Ultimate 64-bit SP1

Reply
0 Kudos
AMoeller
Contributor
Contributor

I want to thank you for the work you have done so far. I have any issue where i am getting the same thing after i cloned a Physical machine into a virtual machine using the VM convertor tool. I am coping a image from an all in one system with windows 7 embedded X64 on it with all of settings, it captures the image just fine with no errors. Just on first boot in goes to the windows logo like it is booting then dies.

I have when over my registry many times and change to what you have inputed on this form, even changed them in controlset002. I did not add any setting if they did not exist in the registry, controlset002 was missing alot. I even went into a working VM registry and copy of the setting that were different. I have an INF file named vmscsi-1.2.0.4.flp i am going to go into CMD and install it hoping it will help this capture image boot.

SO here are my current setting compared to what they were.

REG value      Start(was)     Start(now)          Tag(was)     Tag(now)          Error code(was)     Errorcode(now)    

Aliide                =3                    3                         1               1                         3                             3

Amdide             =3                    3                         1               1                         3                             3

Atapi                = 0                    0                       21(33)        21(33)                   3                              3

Cmdide            = 3                    3                         1               1                         3                             3

iastore                 Does not exist( this is for intel rapid storage??)-(did not have that installed)

iaStorV                 Does not exist (" SAME" )

intelide            = 0                    0                          4               4                         0                              3

msahci            = 3                    3                         22(34)       40(64)                   3                              3

pciide              = 3                    3                         6(6)           10(16)                  3                              3

viaide              = 3                    3                         NA               NA                    3                              3

LSI_SAS         =0                     0                        40(64)          40(64)                1                              1

LSI_SCIS          0                    0                        22(34)         22(34)                  1                              1

Extra Reg entries that i found on a working VM: LSI_FC & LSI_SAS2(i think this is my second drive)

If there is any over information you may need, please let me know.

Reply
0 Kudos
continuum
Immortal
Immortal

post your vmx file BEFORE you try to install anything - the vmscsi floppy is not required for Win7 !


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
AMoeller
Contributor
Contributor

Here is my VMX File:

.encoding = "windows-1252"

config.version = "8"

virtualHW.version = "8"

memsize = "2048"

MemAllowAutoScaleDown = "FALSE"

displayName = "CW7E-64"

guestOS = "windows7-64"

sound.present = "TRUE"

sound.filename = "-1"

sound.autodetect = "TRUE"

usb.present = "TRUE"

ethernet0.present = "TRUE"

ethernet0.addressType = "generated"

ethernet0.connectionType = "bridged"

ethernet0.virtualDev = "e1000"

ethernet0.startConnected = "TRUE"

ide0:0.present = "TRUE"

ide0:0.autodetect = "TRUE"

ide0:0.filename = "D:\Brookdale\ISOs\W7 Emebedded tool kit X64.iso"

ide0:0.deviceType = "cdrom-image"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsisas1068"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "CW.vmdk"

mks.enable3d = "TRUE"

vmci0.present = "TRUE"

ehci.present = "TRUE"

pciBridge0.present = "TRUE"

tools.upgrade.policy = "useGlobal"

pciBridge4.present = "TRUE"

pciBridge4.virtualDev = "pcieRootPort"

pciBridge5.present = "TRUE"

pciBridge5.virtualDev = "pcieRootPort"

pciBridge6.present = "TRUE"

pciBridge6.virtualDev = "pcieRootPort"

pciBridge7.present = "TRUE"

pciBridge7.virtualDev = "pcieRootPort"

extendedConfigFile = "Windows 7 x64.vmxf"

virtualHW.productCompatibility = "hosted"

scsi0.pciSlotNumber = "160"

ide0:0.startConnected = "TRUE"

ethernet0.generatedAddress = "00:0c:29:06:6b:88"

ethernet0.pciSlotNumber = "33"

usb.pciSlotNumber = "32"

ehci.pciSlotNumber = "35"

sound.pciSlotNumber = "34"

vmci0.id = "1855557575"

vmci0.pciSlotNumber = "36"

uuid.location = "56 4d d8 2b 1f 83 6a da-32 3e aa 85 a3 06 6b 88"

uuid.bios = "56 4d d8 2b 1f 83 6a da-32 3e aa 85 a3 06 6b 88"

cleanShutdown = "TRUE"

replay.supported = "FALSE"

replay.filename = ""

scsi0:0.redo = ""

pciBridge0.pciSlotNumber = "17"

pciBridge4.pciSlotNumber = "21"

pciBridge5.pciSlotNumber = "22"

pciBridge6.pciSlotNumber = "23"

pciBridge7.pciSlotNumber = "24"

scsi0.sasWWID = "50 05 05 6b 1f 83 6a d0"

usb:1.present = "TRUE"

ethernet0.generatedAddressOffset = "0"

vmotion.checkpointFBSize = "134217728"

softPowerOff = "FALSE"

usb:1.speed = "2"

usb:1.deviceType = "hub"

usb:1.port = "1"

usb:1.parent = "-1"

bios.forceSetupOnce = "FALSE"

tools.remindInstall = "TRUE"

usb:0.present = "TRUE"

usb:0.deviceType = "hid"

usb:0.port = "0"

usb:0.parent = "-1"

Let me know if you see anything, thank you.

Reply
0 Kudos
continuum
Immortal
Immortal

Looks good
Boot into a Win7 LiveCD next and load the system hive of the installed system. Note: that is not the one in X:\windows\... but the one in C:\ or D:\
Then check which controlset is used by reading
HKLM\System\Select\Current
That should be 1
Then check the value for Start for LSI_SAS - should be 0


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
AMoeller
Contributor
Contributor

I load up and check it, here are my two screenshots below. Do you want me to take screenshots of the rest of the setting in the registry? Let me know if there is anything you need.

Now i have two ideas left.

1. add a second HDD onto the VM that would be set as a IDE drive not SCSI. Then Map both drives and clone the contains over to the new IDE HDD. Ones that is done, i would edit the VMX file so it know what HDD to boot to.

2. Install that driver package that i got from VM. To do that i need to map the drive then capture it as a WIM and inject the driver into the WIM. After that then reapply the wim on top of the HDD, which would erase the old image without the driver.

Let me know what you think.

Thank you

Reply
0 Kudos