[nflug] vmware player bsod

Stephen Burke qfwfq at adelphia.net
Tue Feb 13 23:24:21 EST 2007

So, after finding this


on digg recently, I decided to finally try diving into the vm realm 
(mainly to avoind the creeping heebie jeebies and feeling of despair 
that booting M$ gives me anymore). I followed the instructions there, 
and I can ALMOST get things going, but as soon as xp gets to the 
splashscreen it crashes with a bsod that says:

"A problem has been detected and windows has been shut down to prevent 
damage to your computer.

If this is the first time you've seen this stop error screen, restart 
your computer. If this screen appears again, follow these steps:

Check for viruses on your computer. Remove any newly installed hard 
drives or hard drive controllers. Check your hard drive to make sure it 
is properly configured and terminated. Run CHKDSK /F to check for hard 
drive corruption, and then restart your computer.

Technical information:

*** STOP: 0x0000007B (0xFC8D2640, 0x0000034, 0x00000000, 0x00000000)"

Then the vmware player window starts flashing red (e17 thing for not 
responding from what I gather), so killing the window is the only way to 

After that "ps -ae | grep vm" still shows this:

  4391 ?        00:00:00 vmnet-bridge
  4405 ?        00:00:00 vmnet-natd
  5086 ?        00:00:00 vmnet-netifup
  5100 ?        00:00:00 vmnet-netifup
  5114 ?        00:00:00 vmnet-dhcpd
  5115 ?        00:00:00 vmnet-dhcpd

And I still see the vmware window in the middle click window list no 
matter how many times I kill it. I can't seem to kill it completely 
without logging out. It keeps popping back up when I return to the 
desktop it was started on.

This machine has a 1.3G duron processor and 512M ram. Maybe not enough 
to run vmware?

The xp system still boots and runs fine, and I can't see how it could be 
infected with a virus since it's almost never used, though as a toy 
inside vmware it might be amusing.

I'm can't actually recall how or if it's even possible to get to a CL in 
xp to actually run CHDSK /F.

Strangeness indeed.
Clearly I'm doing something terribly wrong, but I can't see what. since 
the instructions don't seem that complex
Has anyone seen this sort of thing before?
Any ideas?


nflug mailing list
nflug at nflug.org

More information about the nflug mailing list