STOP error on Win2000 after migrating to Virtual PC

  • Thread starter Thread starter Joseph O'Brien
  • Start date Start date
J

Joseph O'Brien

I've been fiddling around with moving a Win2000 box to a Virtual PC,
and I could use some advice about a STOP error I'm getting.

Basically, I created a vhd of the original Windows 2000 drive and
attempted to boot from it using Virtual PC 2007. The STOP error I get
occurs just after the Windows logo appears, and starts with "a device
driver attempting to corrupt the system has been caught...".

At this point, I know I should just start over with a fresh
installation, but now I'm curious if it's possible to figure out which
driver is causing the problem.

I am able to boot into Safe Mode, so I ran msconfig and selected the
"Diganostic Mode" option. However, I still get the same STOP error.

I also replaced the contents of the system32/drivers folder with
drivers from a fresh Windows 2000 installation (also in Virtual PC).
Again, same STOP error.

What other locations should I be concerned about if trying to
eliminate a problematic driver? Is it enough to simply remove suspect
files, or is there a better way to tell Windows not to load a driver?
Or, is it possible that I'm barking up the wrong tree, and the problem
might not be drivers at all?

Thanks!

Joseph
 
Joseph O'Brien said:
I've been fiddling around with moving a Win2000 box to a Virtual PC,
and I could use some advice about a STOP error I'm getting.

Basically, I created a vhd of the original Windows 2000 drive and
attempted to boot from it using Virtual PC 2007. The STOP error I get
occurs just after the Windows logo appears, and starts with "a device
driver attempting to corrupt the system has been caught...".

At this point, I know I should just start over with a fresh
installation, but now I'm curious if it's possible to figure out which
driver is causing the problem.

I am able to boot into Safe Mode, so I ran msconfig and selected the
"Diganostic Mode" option. However, I still get the same STOP error.

I also replaced the contents of the system32/drivers folder with
drivers from a fresh Windows 2000 installation (also in Virtual PC).
Again, same STOP error.

What other locations should I be concerned about if trying to
eliminate a problematic driver? Is it enough to simply remove suspect
files, or is there a better way to tell Windows not to load a driver?
Or, is it possible that I'm barking up the wrong tree, and the problem
might not be drivers at all?
Click to expand...


The virtual machine introduces a different hardware configuration...
so if you want to go through the trouble of performing a repair install
within the virtual
machine, you may get your OS going...
but you might as well just perform a fresh install and get it right
 
Back
Top