Problem blue screen vista

Removing VMware solves the problem; unplugging my mouse when I reboot and leaving it unplugged until the Vista login screen appears circumvents it. I use VMware in my job so I unplug the mouse. I'm hoping it is fixed in 6.

Ray Megal. Thanks for the tip. I was just starting to consider installing VMware on my x64 Vista machine, which like Ray is almost an exact copy of your machine.

I use the VMs daily in my work and I've never had it crash or lockup. May 22, It took me quite some time to get it booting again. My machine is also a close clone of yours that I built following Jeff's posts.

I just switched to VMWare about a two months ago. Second, Dual Core Support. I basically just set up a base image and then I have a seperate VM for each company I work with so that I never have to worry about downtime when I replace my equipment also makes backups a breeze. Other problems with VMWare: the restore from paused state is horribly slow disable background snapshots immediately, then jumping from one VM to another will take 5 minutes instead of He even had it corrupt a VM image entirely a while back, which caused major frustration.

Jesse Ezell. Great post -- hope it helps others. I know Jon Galloway harps on this a lot, and I tend to agree with him. Jeff Atwood. Yeah, like Jeff said. I think VMware is more full featured than Virtual PC, but it's not a player; it's a server that's been skinned to look like a player. Install it on another system and take a look at all the auto-run services it installs. Jon Galloway. It seems that keyboards and mice are dangerous thing to have on a pc.

Turns out the Intellipoint 6. How random and bad is that. May 23, This is a sore issue for me. For me the VMWare experience has been a very painful one. VMWare technical support cost just as much as I paid for the software, which is something I just cannot afford. I did dig out something from the VMWare knowledge base about onboard network card and sli based motherboards, where the hosts apparently crashes. This was logged way back in They recommend disabling the onboard network card and adding a seperate one.

Which I did, but did not fix my issue. I once found a thread on their forums, same problem, same mouse, but no reply or anything. My solution: Unplug on reboot, use hibernation. It's a common issue as well. So my final solution: Uninstall VMware and use VirtualBox ok it's missing some features but works reasonably well. You know, someone always has a particular brand of hard drive, motherboard, psu that they've had a bad experience with and thus blames.

I find all the brands fail occasionally. May 24, Once fixed, that sucka slams! Scott - I feel your pain with the VM. Mark Deason. May 25, Thanks for your feedback. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question Report abuse. Details required :. Cancel Submit. SpiritX Volunteer Moderator. Install theWindows SDK but just choose the debugging tools.

File menu - Symbol File Path and enter. Close and reopen WinDbg. File menu - Open Crash Dump This will analyse the crash dump. You need to close and reopen WinDbg for each dump file analysed. Because you are downloading symbols from the internet WinDbg will appear to be doing nothing. But it's downloading. Be patient. You are looking for a driver or system library that the crash occurred in at the end of the listing.

Find the file, right click then Properties - Details tab. If it shows a driver you'll need to update the driver identified. Type replacing drivername. If it shows a system file see if you can get a program from analyze -v. Type in theWinDbg command prompt.

Or upload the minidump files to your Public folder on Skydrive and copy the link from the address bar and I'll analyse them. If you have downloaded any of the Live applications or have a web based Live mail account you already have access to your Skydrive.

Put your event list in the Public folder and copy the link from the address bar. Hello Hoomep. Luigi Bruno.