I just switched to VMWare about a two months ago. It's super-stable and a miracle of modern software. I also hope a $100 power supply might be a simple solution to your problem. Perhaps the reason you didn't see it before was (a) you didn't reboot often enough to get a statistical sample, and (b) perhaps you didn't have all of those devices connected when you did reboot, and (c) perhaps the installation of VMware player moved the initialization of certain hardware devices into closer proximity so their peak power consumption states were reached simultaneously. Perhaps what you experienced is a legitimate error due to too much power consumption, and the removing of USB devices that draw power from the bus dropped you below the threshold. Early on, I found that I couldn't have it connected to the PC's internal USB devices because it would increase the liklihood of the INTERNAL_POWER_ERROR. And I have another datapoint that leads me to believe it is a power issue: I have one of those USB fish tanks from ThinkGeek. The new chassis to which I upgraded had a 450w power supply instead of the 400w power supply. On the other hand, perhaps it is actually an issue with insufficient power. I believe what's happening with the error may be _related_ to VMware, but maybe as peripherally as a "timing" issue. I also have to say to Vista developers - great job on handling a motherboard/chipset replacement. Henceforth, I haven't had a single INTERNAL_POWER_ERROR (2 months, 20-30 reboots). Then, for other reasons, I upgraded the chassis and motherboard, keeping all other things constant (including the system OS instance). I have VMware Workstation 6.0, and it's essential to my work. When I downgraded to a video card with lower power consumption, the problem lessened, but remained. I also found that removing USB devices would lessen the likelihood of the error. I very rarely rebooted my system, but when I did, it would blue-screen with the INTERNAL_POWER_ERROR about 1 in 5 times. That said, I had done similarly to what you had described. I had a very similar problem with a previous machine, and I'm pretty sure it's not _specific_ to VMware. To debug this, in the debugger type:Īll subsequent debugger commands will show you the actual The power policy manager experienced a fatal error.Īrg1: 0000000000000101, Unhandled exception occured while processing a system power event.Īrg3: fffffa6001dc8b10, ExceptionPointer. Probably caused by : VMkbd.sys ( VMkbd+15da ) *** ERROR: Module load completed but symbols could not be loaded for VMkbd.sysīda8 not present in the dump file. Perhaps VMWare doesn't like my Wireless USB Keyboard? Mental note, relearn WinDbg'ing. UPDATE: Installed Windows Debugging Tools (WinDbg.exe) and analyzed the crash dump and it's the VMWare Keyboard Driver, of all things. I hope this post helps someone having this same issue. I have the Crash Dumps if you work for VMWare and you're interested. My guts says that this is a bug in the VMWare USB bridging code (the stuff in VMWare that lets you use USB devices inside a VM) or it's somewhere in the USB drivers in Windows. ALL of them, to be clear, save one wired USB Keyboard that I used to log in and remove VMWare. The only way I could get the system to boot up was to remove ALL the USB devices. I am using a Quad-proc machine with an MSI motherboard with the latest BIOs and a buttload of USB devices. I looked all over and checked out the VMWare Forums and no one at VMWare has acknowleded the problem in a Googl-eable way. Needless to say this scared the crap out of me. However, when it's installed my 64-bit machine blue screens, and it's very difficult to get uninstalled, actually. I had some trepidation at the time of the install because I am not a fan of the way that VMWare adds virtual network devices that are listed in Network Connections, but it came highly recommended from respected power users I know and I needed it to install a prepared Suse VM from the Mono folks. Working backwards, the last and only interesting thing I installed was VMWare Player for Windows. I built it to be stable and I trust the machine. I started cussing Vista out and panicking, but this machine has been exceedingly stable since I built it last year and I reboot only every few months. At this point I was in a blue screen "loop" with the ominous message "INTERNAL_POWER_ERROR" on the blue screen. I rebooted this evening, the first reboot since March, in fact, and blue-screened (BSOD) upon startup. I hope this helps someone because it totally freaked me out this evening.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |