VMware Communities
ThomasHelm
Contributor
Contributor

WS6 BSOD with INTERNAL_POWER_ERROR on WinXPSP2

After installing WS6 Build 45731, my computer doesn't start. I will get allways a BSOD with the error message:

INTERNAL_POWER_ERROR

\*** STOP 0x000000A0 (0x00000101, 0x00000007, 0xF78DE75C, 0x00000000)

The only way to start my computer is to select the 'last known good configuration' option an startup. But not all new drivers will be installed after that. It's an rollback.

WS5.5 works fine.

My Hard/Software: 1.4GHz Centrino, 2 GB RAM, XPSP2 with all patches.

Whats wrong?

Thomas

Reply
0 Kudos
40 Replies
BehnReady
Contributor
Contributor

Yes, vmkbd.sys is the reason for the bsod on my system. I tried to remove it from the system32 directory, and then the system booted fine, although my keyboard didn't work, and I had to login using onscreen keyboard. If only they would solve this little problem and give us an updated vmkd.sys.

Reply
0 Kudos
Dagon
Contributor
Contributor

I don't know if this is helpful or not, but I ran into an interesting problem with vmkbd.sys recently. I put together a new development system the other day for a client and loaded VMWare Workstation 6 on it as the first application after installing the OS (Windows XP Professional). After loading on all the other applications I started testing the system out and noted a long delay while booting the system - after the Windows desktop was loaded but before the taskbar or icons were presented.

After some testing and taking a look at the boot sequence with Bootvis, I found that vmkbd.sys was blocking for 24 seconds after it loaded and bringing the entire system to a halt. I assume some function is timing out and it eventually errors and continues. It will be very frustrating for the person using the computer if they reboot frequently at all.

Reply
0 Kudos
m_anders
Contributor
Contributor

Has anyone tried to see if this issue still exists with the new VMware Workstation 6.0.1, Build 55017 build recently released?

My solution has been to use a non bundled BT dongle that isn't recognized as having built in keyb/mouse support outside of windows.

Reply
0 Kudos
Dagon
Contributor
Contributor

My issue was resolved with the update, if that is of any help.

Reply
0 Kudos
m_anders
Contributor
Contributor

Dagon,

You really should have started your own topic, as your delay issue has nothing to do with the BSOD message the rest of us are seeing when using a wireless input device.

With that aside, I upgraded to the newest build, inserted my old BT dongle and rebooted.... and rebooted..... and rebooted.

This time there is no BSOD, it just continuously reboots. So looks like this issue was not addressed - which is also clear by reading the changelog.

Shame on VMWARE for not even mentioning this issue.

Reply
0 Kudos
RickNY
Contributor
Contributor

Just in case this helps anyone else having this issue...

I have a Logitech 3200 Cordless Desktop installed.. The Logitech drivers replace the default i8042 driver with its own, which I believe is l8042.. The solution for me to eliminate the BSOD was as follows:

1) Open Device Manager

2) On the menu bar, click 'View' then 'Show hidden devices'

3) Find the entry for 'PS/2 Keyboard'

4) Right-click and choose 'Disable'

On my system, the Logitech Setpoint software is installed, but it hides the PS/2 keyboard device because its listed as 'This device cannot start because its not present, doesnt have all the drivers installed...', etc. It seems the VMware filter driver for the keyboard causes the computer to crash at bootup when Windows attempts to load that device.

Hope that helps..

Rick

Reply
0 Kudos
m_anders
Contributor
Contributor

Rick,

Tried that. Still no go. With the newest vmware workstation, it just reboots. Doesn't even bsod any more. Gets stuck in a reboot cycle.

Reply
0 Kudos
Aaron44126
Contributor
Contributor

I've been having this problem...

Workaround for me is to just disable the "Bluetooth HID Device" in the device manager. This allows the machine to boot with the BT dongle plugged in without a BSOD. I don't use a bluetooth keyboard or mouse, though, so this won't work for you if you do - it'll kill your bluetooth keyboard/mouse input.

It's worth noting that I have this issue on 64-bit Vista (doesn't seem to be specific to a certain version of Windows, just any that have the built-in bluetooth drivers...?).

There used to be a way to submit a problem report by submitting a support request without requesting an answer (even if you didn't have a paid support plan) as petr told me long ago here: http://communities.vmware.com/message/325853#325853. I can't find this option anymore, so there seems to be no way to report this without buying a support plan...? Grr.

Reply
0 Kudos
Robert1802
Contributor
Contributor

I had(!) the same problem on Vista x64 using a Logitech wireless keyboard with VMware player 2.0.2. Microsoft recently released a bug fix for several USB related errors. See

http://support.microsoft.com/kb/941600

for more details. After I applied the fix, reinstalled VMware and bounced the system, it started without BSOD and all VMware services running fine.

Reply
0 Kudos
BoomSchtick
Contributor
Contributor

I'm having this problem running a HP with XP sp2 and the very latest 6.0.2 download available to me. I thought it was my Microsoft USB keyboard, but it does it with ALL usb keyboards. It's a good thing that my PC has a ps2 port, or there would have been no way for me to get back up and running. I uninstalled 6.0.2 and installed 6.0.1 and am having the same problem.

My system boots fine if vmware is not installed and my usb keyboard is plugged in. Smiley Sad

Reply
0 Kudos
BoomSchtick
Contributor
Contributor

I did some more troubleshooting. I'm having the same problem with 6.0.0, 6.0.1 and 6.0.2. I did not have this problem before I recently reformatted my machine and started fresh. I took my old hard drive and copied the vmkbd.sys from it and replaced the ones on my production machine with them. It seems that did not make any difference.

They were all had vmkbd.sys version 1.0.0.0 with the same size and date, except 6.0.2 has a vmkbd.sys file version of 1.0.0.1.

One thing I did do differently is leave the PS/2 keyboard in with the USB keyboard. My machine boots just fine with 6.0.2 installed as LONG as the PS/2 keyboard is plugged in. It does not seem to matter if a USB keyboard is plugged in or not in that case.

Reply
0 Kudos
azulmarino
Contributor
Contributor

I suffered from this BSOD after installing WMware Player 2.0.2.

I have a USB keyboard and a Logitech MX wireless mouse.

The solution: use an adapter to connect the USB keyboard to the PS/2 port.

Reply
0 Kudos
m_anders
Contributor
Contributor

Has a solution been found for this yet?

Even with the current build of 6.0.2 build 59824, the issue persists.

Seems of the blue tooth dongle has built in keyboard and mice profiles (such as the microsoft bt keyboard/mouse set), the system bsod's on first reboot after vmware installation.

Reply
0 Kudos
m_anders
Contributor
Contributor

Has a solution been found for this yet?

Even with the current build of 6.0.2 build 59824, the issue persists.

Seems of the blue tooth dongle has built in keyboard and mice profiles (such as the microsoft bt keyboard/mouse set), the system bsod's on first reboot after vmware installation.

Reply
0 Kudos
kernel_md
Contributor
Contributor

Hello everyone,

It seems that I overcame this problem.

I have a Logitech MX5500 Wireless Kbd & Mouse, and having the same BSOD, even if I unplug the btooth dongle.

Here is the solution:

1. Oper Regedit

2. Goto HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E96B-E325-11CE-BFC1-08002BE10318}

Here you have "UpperFilters" param of type REG_MULTI_SZ with a value like: "kbdclass vmkbd"

A driver name per line, notice that vmkbd by default is the last in the list.

Edit that parametter by putting vmkbd to be the first in the list.

Note that in some cases "vmkbd" can be named differently: vmkbd2, vmkbd3 - it does not matter, it is because you probably have installed a newer version of wmvare above old one or smth like that, and the previous driver was not able to be deletet from registry, anyway this does not change the idea.

3. Reboot and you should not have any BSOD now.

For me it worked, hope for you it will also.

Reply
0 Kudos
garyfritz
Enthusiast
Enthusiast

kernel.md, THANK YOU!!! I've had an XP SP2 system that's been "dead" ever since I got a new laptop almost a year ago. Couldn't figure out what was wrong with it. I didn't have a wireless keyboard, and in fact it would die if I unplugged every single device or peripheral except C:.

I finally isolated it to the VMkbd.sys driver, and that led me here. Your simple fix resolved the problem. Thank you thank you!!

Reply
0 Kudos
kernel_md
Contributor
Contributor

glad to help you men Smiley Wink

Reply
0 Kudos
chintancm
Contributor
Contributor

can somebody tell me how do i arrange this "UpperFilters" param of type REG_MULTI_SZ with a value like: "kbdclass vmkbd" to the first? bcoz i am not able to shift it to the first row,

will u please give a step by step details....

thanks in advance...

Reply
0 Kudos
kernel_md
Contributor
Contributor

Look here

Reply
0 Kudos
chintancm
Contributor
Contributor

the photo shows how to change the value, but by doing that the entire row wont shift to the first row...as u said that the solution is to shift the entire row to first position...hope u r clear with my problem...

Reply
0 Kudos