Virtual machine boots into BSOD

I have a new notebook computer with Windows 7 64-bit.  I prefer to use other operating systems, so I created a vmx file from the physical disc in my old laptop.  It has 3 operating systems:  two of them are Windows XP Professional and one is Windows 7 Professional 32-bit.  VMWare Converter was used to create the vmx file, which contains three volumes with these operating systems.  Using VMPlayer, all of the systems boot into a BSOD with STOP: 0x00000007B.  

I have never used a virtual machine before, and feel awkward trying to work with it.  I can't even seem to select "safe mode" during the reboot process.  The keyboard and mouse seem to have no effect on the boot menu. At any rate, I'd appreciate some guidance on how to remedy the BSOD.
ddantesAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
John HurstConnect With a Mentor Business Consultant (Owner)Commented:
Are you sure the VMDK is OK?  It sounds like it is damaged somehow.

If you can run it long enough, try running System File Checker (SFC /SCANNOW) and see if that helps.
0
 
Paul SConnect With a Mentor Desktop Support Manager / Network AdministratorCommented:
Stop Error 7B means the disk controller driver is missing or not included in the critical driver database for earlier loading during OS boot. normally VMware converter solves this during conversion or as a separate task.

- try telling vmware convert to fix this as a separate task. normally called "reconfigure VM"
- try changing the disk controller type in VMware player. try combinations until it works.

also, read this:

VMware KB: Virtual machine fails to boot with a blue diagnostic screen stating: 7B Stop Code after using VMware Converter
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2002106
0
 
ddantesAuthor Commented:
Thank you for your comment. In VMConverter, I have the window open for customizing reconfiguration.  There is a warning: Unable to locate the required sysprep files.  Not sure where to go from here.
0
Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

 
Paul SDesktop Support Manager / Network AdministratorCommented:
I would ignore the warning and continue if possible. I don't normally provide sysprep files and it works for me.
0
 
Paul SDesktop Support Manager / Network AdministratorCommented:
if you can't continue....

this article says sysprep files are built into Window 7.

VMware KB: Sysprep file locations and versions
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005593

maybe your windows 7 host installation is corrupt?
0
 
John HurstBusiness Consultant (Owner)Commented:
VMWare Converter was used to create the vmx file, which contains three volumes with these operating systems.

Just to be clear, you have 3 folders and each folder has a VMX and a VMDK file (and some others). They are all separate. There is not one VMX file for all 3 machines.

Open VMware Player and point to one of the machines. BEFORE starting the machine, see if you can go to VM, Manage, and Change Hardware Compatibility. See if you can change it to a newer level and see if that helps. This works in VMware Workstation, and I do not know if it works in VMware Player.
0
 
ddantesAuthor Commented:
Thanks to both Experts.  There is only one vmx file and it contains three volumes.  The installations are not corrupt, since they run normally on the old laptop.  Unless they became corrupt during the conversion process.
0
 
John HurstBusiness Consultant (Owner)Commented:
You should move that VMX file into a secure backup location, then separate your 3 machines into 3 folders, and then make a new VMX file for EACH machine. Once done, try upgrading hardware and see if you can open one.  ONE VMX file per machine, please.
0
 
ddantesAuthor Commented:
OK.  This will take more than a day, and I will post again.  Meanwhile, can you provide some specific instruction on upgrading hardware?  Perhaps I could try that first, in case it helps.
0
 
John HurstBusiness Consultant (Owner)Commented:
As I noted for VMWare Workstation, VM, Manage allows you to change hardware compatibility. It is a VMWare function and I have used a change in hardware to resurrect a machine not working properly with respect to hardware.

If you are trying to learn VMWare, you will be much better off with Workststion rather than Player.
0
 
ddantesAuthor Commented:
Thank you.  I have a trial version of VMware Workstation.  But I don't know what hardware should be changed, or what to change it to.
0
 
John HurstBusiness Consultant (Owner)Commented:
VMWare supplies hardware. Look at the level in the Manage section and if you can change up level, please try.

I would not do this until you separate machines into folders, each with its own VMX file.
0
 
ddantesAuthor Commented:
Understood.  Please stand by while the VMX files are created, tested, and re-configured...
0
 
Paul SDesktop Support Manager / Network AdministratorCommented:
did you have a multi-boot menu on the original hardware for selecting which OS to boot? do you still get that on the VM?

Did you try my suggestion of changing the disk controller type?
0
 
Paul SDesktop Support Manager / Network AdministratorCommented:
this article might be relevant too

VMware KB: Injecting SCSI controller device drivers into Windows when it fails to boot after converting it with VMware Converter
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1005208
0
 
ddantesAuthor Commented:
There was a multi-boot menu on the original disc and on the VM.  I have yet to try changing the disc controller.  It is already set as SCSI.  When I created a VMX file with only a single operating system, the VM booted without a BSOD.  However, after a few minutes of working with the machine, a blue screen appeared.
0
 
John HurstBusiness Consultant (Owner)Commented:
Did you try ONE VMX file for ONE machine and change the hardware level?  What happened.
0
 
ddantesAuthor Commented:
Yes, a new VMX file was created with only a single operating system.  The hardware was already set at the highest level.  It booted OK but a BSOD developed after a few minutes.  I even tried lower settings of hardware, but it didn't help.
0
 
ddantesAuthor Commented:
SFC reported corrupt files which were successfully repaired.  I'll see what happens with the VM now and post again.  On start-up, several devices could not be connected because adapters don't exist on the host (parallel and serial ports and an SCSI CD drive).
0
 
John HurstBusiness Consultant (Owner)Commented:
Thanks for trying SFC and keep us posted with results.
0
 
ddantesAuthor Commented:
The VM seems to be working now.  Thanks to both Experts.
0
 
John HurstBusiness Consultant (Owner)Commented:
@ddantes  - Thanks for the update and I was happy to help. I am glad all is well.
0
All Courses

From novice to tech pro — start learning today.