VMware Communities
IDJay
Contributor
Contributor

Help, XP sp3 converted VM boots in safe mode but not normal mode

Newbie here. Not sure if this is a converter question or a player

question. I don't want to double post so if there is a moderator please

place in the correct spot.

I converted my old (5yrs) laptop (XP

sp3) that has a broken screen. I'd like to keep everything as is in a

VM on my new machine. Did conversion and all looked ok.

Windows

tries to boot, stops and I get a blue screen ...0007E error then a quick

VMware page and back to a boot menu couning down to try a normal boot

in 30 seconds. It will do this forever. If I select safe mode with

networking it boots the machine fine.

If I look at device manager I

get a warning messages on "base system Device" and "video controller

(VGA compatible)". If I view hidden devices I see that I have an

warning/error at "visual NDMonitor", and "Partmgr". Also windows does a

hardware check and says it found new hardware and wants to install a

video controller but if I select do it, it just says can't find driver

and my hardware may not work properly. I think it tries to find a

driver for another device also.

I have tried to search for solutions

but have yet to find anything.

I tried installing VM tools but no

help.

should I delete the bad drivers and hope windows rebuilds?

I

suspect it is some hardware driver issue thing. (moving from a gateway

to Toshiba)

Should I try another conversion with different

settings? (old sys only had 172MB ram so VM asked for that, also

created serial and Parallel ports that I disable as the new system does

not have these.)

Any simple way to identify offending driver /

hardware configuration issues?

VM Hard drive is IDE, not SCSI.

Any suggestions?

I'd really

love to get this v machine up and running. Thanks for all the help and

wisdom. All help and suggestions appreciated.

Tags (3)
Reply
0 Kudos
7 Replies
WoodyZ
Immortal
Immortal

VMware cannot support OEM copies of Windows migrated to virtual machines as this is a violation of Microsoft Licensing conditions. If you purchased your computer with Windows pre-installed, you are most likely running an OEM version of Windows. To check whether you are running an OEM version, see How to Determine the Version of Windows XP in Use.

Reply
0 Kudos
IDJay
Contributor
Contributor

Woodyz,

Thanks for the response. So is there no way I can get where I want to be? As this machine is toast due to it being old and the broken display and I am the legal owner of the OS and other software, can't I transfer the license to a virtual machine? So you are saying that is the cause of why I can not boot in normal

mode and only in safe mode, because I possibly have an OEM copy of

Windows XP.

Can I buy another license?

Can I buy a retail copy of XP and install over my copy without formatting or anything such that I would not have to reinstall all of the applications and setting etc.

I thought I have heard others doing exactly what I am trying to do but what do I know. I do appreciate you taking the time to answer my question. Thanks, J

Reply
0 Kudos
a_p_
Leadership
Leadership

Reading your first post it sounds like the system does reboot automatically after the BSOD. If so, first step should be to disable the automatic system reboot to be able to see what the BSOD is about. I guess your old system has some mainboard or other drivers installed which cause the issue.

You can also check for system specific add-ons in Add-/Remove Programs while booted in Safe Mode and uninstall unneeded software.

André

Reply
0 Kudos
WoodyZ
Immortal
Immortal

Creating a working Virtual Machine from your old computer is technically doable however since you are in all likelihood running an OEM version of Windows that came pre-installed on your Gateway computer the issue becomes moot since OEM versions of Windows live and die on the hardware on which they are originally installed and are not legally transferable in any way shape or form to another computer, physical or virtual.

That said, clean building a Virtual Machine while it takes considerably longer then P2V nonetheless will yield a better product in the end and I typically recommend that over P2V especially for long term use.

Reply
0 Kudos
IDJay
Contributor
Contributor

Thanks for all the help. Just as a follow up I decided to to a fresh install start clean and reinstall everything. I figured I'd spend more time figuring everything out than just starting new. Perhaps I should spend the effort to learn linux. But thank you for your support and advice. J

Reply
0 Kudos
admin
Immortal
Immortal

Hi IDJay,

If you still have that virtual machine around give this a try:

01) start windows - STOP 7E

02) press control + alt to release mouse

03) select Virtual Machine > Power > Reset

04) click Reset to restart the virtual machine

05) when windows starts again choose Safe Mode and press Enter

Note: if windows does not start in safe mode restart the virtual machine, click into the virtual machine window, then continuously press F8 as the virtual machine is starting.

06) select a user account and login

07) select Yes to start in Safe Mode

08) click Start

09) right click My Computer > select Manage

10) select Device Manager

11) select View > Show hidden devices

12) right click Visual NDMonitor > select Properties

13) under device usage: select Do not use this device (disable)

14) click OK

15) restart and start windows normally

Woody is correct however you are most likely violating the license agreement and you should buy a new license if you are going to use this virtual machine and the laptop.

You are also much better starting off with a new VM then with a 5 year old laptop conversion.

Message was edited by: khogan - Changed settings from Fusion to Player

Reply
0 Kudos
remaker
Contributor
Contributor

OK, I just solved this one myself after much, much pain.

In the C:\WINDOWS\SYSTEM32\DRIVERS directory, there is some driver loaded during regular boot and not safe boot.

In my case, I renamed three driver files:

ipvnmon.sys to ipvnmon.sys.renamed

sonydcam.sys to sonydcam.sys.renamed

sonyfanc.sys to sonyfanc.sys.renamed

Alternately, look for unsigned driver files using sigverif.exe

The Sony drivers of this particular guest (converted Windows XP machine) seemed to be a real problem.

Reply
0 Kudos