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

0 Kudos
40 Replies
Aldebaran
Hot Shot
Hot Shot

0 Kudos
ThomasHelm
Contributor
Contributor

There's no help. I have the problems with startup and not shutdown or suspend or hibernate. I have also no sidewinder gamepad.

Thomas

0 Kudos
el1971
Expert
Expert

One question: Does this problem happen with your Host OS or Guest OS?

\-- Edi

0 Kudos
ThomasHelm
Contributor
Contributor

This problem happens in the host machine.

Thomas

0 Kudos
el1971
Expert
Expert

Do you have a wireless keyboard?

\-- Edi

0 Kudos
ThomasHelm
Contributor
Contributor

I have externally connected a microsoft keyboard elite for bluetooth on my host (notebook).

Thomas

0 Kudos
el1971
Expert
Expert

Do you also receive a BSOD when the keyboard is not connected to the Host?

\-- Edi

0 Kudos
ThomasHelm
Contributor
Contributor

The wireless keyboard and the installed drivers from WS6 was the reason for the BSOD. If I disconnect the wireless keyboard and startup the computer, windows will starts fine. At the welcome screen I connect the wireless keyboard and type in my password for logon. From here all was fine.

If I now start the computer with the wireless keyboard conntected, I will get the BSOD. Disconnect the wireless keyboard and restart, no BSOD will occure and I connect the keyboard later for work.

Thanks.

Thomas

0 Kudos
m_anders
Contributor
Contributor

I too have a wireless keyboard (the ms bluetooth elite).

Config is q6600/4gb/vista ultimate 64bit

The issue seems to be with the vmkbd.sys driver. With that renamed, the system boots just fine (although I have no keyboard functionality). With vmware uninstalled, everything works just fine. Seems like this driver isn't hooking properly or something.

Also, the crash memory dump analysis points to this as well.

\----


*******************************************************************************

\* *

\* Bugcheck Analysis *

\* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck A0, \{101, 7, fffff9800149bb30, 0}

Unable to load image \??\C:\Windows\system32\drivers\VMkbd.sys, Win32 error 0n2

\*** WARNING: Unable to verify timestamp for VMkbd.sys

\*** ERROR: Module load completed but symbols could not be loaded for VMkbd.sys

Probably caused by : VMkbd.sys ( VMkbd+16aa )

Followup: MachineOwner

\----


1: kd> !analyze -v

*******************************************************************************

\* *

\* Bugcheck Analysis *

\* *

*******************************************************************************

INTERNAL_POWER_ERROR (a0)

The power policy manager experienced a fatal error.

Arguments:

Arg1: 0000000000000101, Unhandled exception occured while processing a system power event.

Arg2: 0000000000000007

Arg3: fffff9800149bb30, ExceptionPointer. To debug this, in the debugger type:

'dt nt!_EXCEPTION_POINTERS '.

All subsequent debugger commands will show you the actual

source of the error. Start with a stack trace by typing 'kb'.

Arg4: 0000000000000000

Debugging Details:

\----


BUGCHECK_STR: 0xA0

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: System

CURRENT_IRQL: 0

EXCEPTION_RECORD: fffff9800149c9a8 -- (.exr 0xfffff9800149c9a8)

ExceptionAddress: fffff80002059fe1 (nt!IofCallDriver+0x0000000000000051)

ExceptionCode: c0000005 (Access violation)

ExceptionFlags: 00000000

NumberParameters: 2

Parameter[0]: 0000000000000000

Parameter[1]: 00000000000000e0

Attempt to read from address 00000000000000e0

TRAP_FRAME: fffff9800149ca50 -- (.trap 0xfffff9800149ca50)

NOTE: The trap frame does not contain all registers.

Some register values may be zeroed or incorrect.

rax=000000000000000e rbx=fffffa800b494050 rcx=fffffa800b4059a0

rdx=fffffa800b50b6e0 rsi=0000000000000001 rdi=fffffa800b494050

rip=fffff80002059fe1 rsp=fffff9800149cbe8 rbp=fffffa800b4974c0

r8=0000000000000000 r9=000000000000000e r10=fffffa800b3f91c0

r11=fffff9800149c790 r12=0000000000000000 r13=0000000000000000

r14=0000000000000000 r15=0000000000000000

iopl=0 nv up ei ng nz na po nc

nt!IofCallDriver+0x51:

fffff800`02059fe1 49ff64c070 jmp qword ptr \[r8rax*870h] ds:00000000`000000e0=????????????????

Resetting default scope

LAST_CONTROL_TRANSFER: from fffff800020da9da to fffff8000204e250

STACK_TEXT:

fffff980`0149ba88 fffff800`020da9da : 00000000`000000a0 00000000`00000101 00000000`00000007 fffff980`0149bb30 : nt!KeBugCheckEx

fffff980`0149ba90 fffff800`020a91c0 : fffff980`06181718 fffff980`06181788 fffff980`061817f0 fffff980`068ad7f0 : nt!PopExceptionFilter+0x8a

fffff980`0149bad0 fffff800`0207b96c : fffff980`068b2a50 fffff980`068b2ac0 fffff980`068b2b38 fffff980`068b2ba8 : nt!PopPolicyWorkerThread+0x150

fffff980`0149bb00 fffff800`02074a0d : fffff980`0149cca0 fffff980`0149cca0 fffff980`0149c9a8 fffff800`0202ee0e : nt!_C_specific_handler+0x8c

fffff980`0149bb70 fffff800`0208d723 : fffff800`00000001 fffff980`0149cca0 fffff980`0149c9a8 00000000`00000000 : nt!RtlpExecuteHandlerForException+0xd

fffff980`0149bba0 fffff800`02032842 : fffff980`0149c9a8 fffff980`0149c380 fffff980`00000000 fffff980`00000000 : nt!RtlDispatchException+0x228

fffff980`0149c270 fffff800`0204e0ae : fffff980`0149c9a8 fffffa80`0b44f650 fffff980`0149ca50 fffffa80`039acbb0 : nt!KiDispatchException+0xc2

fffff980`0149c870 fffff800`0204cea5 : 00000000`00000000 fffffa80`039acbb0 fffffa80`0b2b4700 fffffa80`0b2f2830 : nt!KiExceptionDispatch+0xae

fffff980`0149ca50 fffff800`02059fe1 : fffff980`03e656aa fffffa80`0b4941a0 fffffa80`0b4f8740 fffffa80`0b493b10 : nt!KiPageFault+0x1e5

fffff980`0149cbe8 fffff980`03e656aa : fffffa80`0b4941a0 fffffa80`0b4f8740 fffffa80`0b493b10 fffff980`05227ea3 : nt!IofCallDriver+0x51

fffff980`0149cbf0 fffffa80`0b4941a0 : fffffa80`0b4f8740 fffffa80`0b493b10 fffff980`05227ea3 fffffa80`00000001 : VMkbd+0x16aa

fffff980`0149cbf8 fffffa80`0b4f8740 : fffffa80`0b493b10 fffff980`05227ea3 fffffa80`00000001 fffffa80`0b4f8740 : 0xfffffa80`0b4941a0

fffff980`0149cc00 fffffa80`0b493b10 : fffff980`05227ea3 fffffa80`00000001 fffffa80`0b4f8740 00000000`00000001 : 0xfffffa80`0b4f8740

fffff980`0149cc08 fffff980`05227ea3 : fffffa80`00000001 fffffa80`0b4f8740 00000000`00000001 00000000`80000000 : 0xfffffa80`0b493b10

fffff980`0149cc10 fffff800`023d22bc : fffffa80`0b2e7390 fffffa80`0b493b10 fffffa80`039acbb0 fffffa80`0b50b6e0 : HIDCLASS!HidpMajorHandler+0x133

fffff980`0149cc40 fffff800`02340fc4 : 00000000`00000002 fffff800`02167878 fffffa80`039acbb0 00000000`00000000 : nt!PopSystemButtonHandler+0x2bc

fffff980`0149cc70 fffff800`0202ee0e : 00000000`00000000 00000000`00000000 00000000`00000001 fffffa80`06778750 : nt!PopPolicyWorkerMain+0x24

fffff980`0149cca0 fffff800`0205a3e3 : fffffa80`06778758 fffff800`02167800 fffffa80`00000000 00000000`00000001 : nt!PopPolicyWorkerThread+0x9e

fffff980`0149cce0 fffff800`022e199b : fffff800`0217a400 00000000`00480058 fffffa80`039acbb0 01c6fe83`9337f401 : nt!ExpWorkerThread+0x12a

fffff980`0149cd50 fffff800`02034b86 : fffff980`00e91180 fffffa80`039acbb0 fffff980`00e9ac40 fffffa80`039ac040 : nt!PspSystemThreadStartup+0x5b

fffff980`0149cd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

VMkbd+16aa

fffff980`03e656aa ?? ???

SYMBOL_STACK_INDEX: a

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: VMkbd

IMAGE_NAME: VMkbd.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46381906

SYMBOL_NAME: VMkbd+16aa

FAILURE_BUCKET_ID: X64_0xA0_VMkbd+16aa

BUCKET_ID: X64_0xA0_VMkbd+16aa

Followup: MachineOwner

\----


0 Kudos
AndersN
Enthusiast
Enthusiast

0 Kudos
m_anders
Contributor
Contributor

Found a work around on my setup.

Quite silly actually, but it does work.

I have the bluetooth Elite wireless keyboard and a wired trackball.

If I boot the system without the BT dongle installed, no BSOD.

0 Kudos
AndersN
Enthusiast
Enthusiast

Yep..

I just plugged in an old PS/2 keyboard (with cable) and stowed it away behind my printer..

Seems like as long as it's just connected, the system boots fine even if it's not even used. I still only use the wireless BT keyboard and mouse.

0 Kudos
m_anders
Contributor
Contributor

AndersN,

\{SMACK!}, why didn't I think of that!

I will test this out later tonight as well. Fortunately my systemboard still has a ps/2 plug to accept the old style keyboards. I wonder if this resolution will still work with a usb keyboard hooked up as well.

My guess is that with the wireless keyboards, there is no response from the keyboard until the drivers are completely loaded and the keyboard has sync'd. I suspect the vmware driver is expecting some sort of response or value returned. When none is received, it panics and crashes. Should just time out rather than BSOD, or the time out period is insufficient for wireless keyboard.

I think the programmers definitely have enough information to fix this now.

There are several threads covering this issue, one of which goes back to early may. One would think a fix is available by now.

Thanks again for your insight.

0 Kudos
m_anders
Contributor
Contributor

Try this,

Turn off your machine, unplug the ps/2 keyboard.

Plug in a usb keyboard, boot up. It should boot ok.

Unplug the usb keyboard, reboot.

It should continue booting up without any bsod's. Such was the behavior here. I rebooted ~5 times, each time successfully.

I will test this further tomorrow when I revert back to a pre BSOD/vmware ghost image and attempt to crash it again.

0 Kudos
m_anders
Contributor
Contributor

Update.

Plugging in the PS/2 keyboard did not help matters. It still BSODs.

Using my technique above also resulted in a BSOD. Not sure why it didn't bsod yesterday. So far the only fix for me is to remove the BT dongle before windows boots.

0 Kudos
m_anders
Contributor
Contributor

Any updates?

0 Kudos
BehnReady
Contributor
Contributor

I have the exact same problem with both VMware Workstation and VMware Player build 45731 on a Vista Ultimate X86 computer. Hopefully this will be fixed soon, otherwise I'm done with VMware.

0 Kudos
m_anders
Contributor
Contributor

Ok folks, good news!

I got another BT dongle, just a standard one that was not bundled with any keyboard/mouse kit. After some hassles getting the drivers loaded, the wireless keyboard was recognized.

Uninstalled vm wrkstation 5.5 and reloaded version 6. 10 reboots later, no bsods!

My theory is that either the vmkbd.sys driver is somehow flawed, or the way legacy mouse/keyboard function is implemented into those bundled dongles causes a conflict.

It should be noted, that I no longer have any legacy keyboard functionality. If I need to get into the bios, I'll have to hook up a wired usb keyboard. Keyboard only functions in windows. In fact, during POST, the system reports no keyboard found, pauses for a moment, then continues.

FWIW, i'm going to revert back to my MS dongle and try changing the driver to something else. The generic dongle which fixes the bsod issue was recognized as a broadcom based unit. With that in mind, we'll see if the same holds for the MS dongle. I doubt it, but worth a shot.

Can some others test this out as well and report back?

Thanks!

0 Kudos
nightlancer
Contributor
Contributor

i think vmkbd.sys is flawed..

bt shouldn't be the issue in radio frequency transmitted keyboards...

removal of vmware 6 fixes the problem for me..

while tempering around with all other drivers did nothing

hopefully new fixes will come out soon enough

0 Kudos