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
continuum
Immortal
Immortal

dont you have lsi-sas driver in your system ?


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

0 Kudos
AMoeller
Contributor
Contributor

Are you talking about the image i captured with the VM Couverture?? Because that is a ALL in one with Windows 7 embedded installed on it, i am guess it does not have it do to the fact it is Windows 7 embedded.

Do i need to inject this driver into the image before i capture it, or can i inject it when i make it a convert it into a WIM for it to work with VM?

I just look at a VM i have working just fine that i captured from a desktop weeks ago and found this: Capture5.JPG

Then i booted up my BAD VM with a windows CD and navigated to that path and found this.:Capture4.JPG

SO i think you are right i am missing the driver need for the VM to open I am going to inject them .sys file and see if that works. Or i am going to need to capture as a wim them inject and apply on top.

Let me know if you think this will work.

0 Kudos
AMoeller
Contributor
Contributor

I added the LSI_SAS.sys & LSI_SCSI.sys & LSI_FC.sys with the reg-keys that point. i am getting lost, let me know if need any more information, or if i can send you a copy of the VM.

0 Kudos
continuum
Immortal
Immortal

I guess I would check which drivers are included and activate that one - even if it is only IntelIDE.

If you like call me via skype and we can have a look together.

skype - name = sanbarrow


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

0 Kudos
AMoeller
Contributor
Contributor

Good News got it working now. I do not think it is only the next steps i just but some of the ones that i did before, just figure out the right order.

This is after i change the HDD driver registry key to default values and added the extra .sys files (LSI_SAS\SCSI\FC)

What i did this time was:

1. Shutdown the VM when i got the blue screen

2. Add a IDE HDD in the setting menu and saved, then booted to BIOS to make sure it saw it.

3. Mapped the VMDK so i could see it

4.Captured the the mapped VMDK with Image-X

5.Mounted the WIM with DISM to the DIR of your picking.

6. Added the VMSCSI.INF with DISM that you get from : VMware KB: Injecting SCSI controller device drivers into Windows when it fails to boot after convert...

7. Unmounted and Committed the WIM

8. Made an ISO of the new WIM (non Bootable)

9. Back to the VM and added a 2nd CD Drive and attach the new ISO you just created.

10. Boot the VM into the Windows 7 Embedded toolkit ISO

11 Apply WIM to the IDE drive 

     a.when you get the menu to pick partition format the scsi drive

     b. create a partition on IDE and do not select create system partition.

12. when it installs and reboots, tell it to use Last known good config.

13. Now you should be in

0 Kudos