BSOD: bugcheck was: 0x0000009f ...

[calamitag]

Hello, yesterday I got a BSOD:
"The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f (0x0000000000000004, 0x0000000000000258, 0xfffffa800fdfd730, 0xfffff80000b9c3d0). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 081714-55754-01.
"
Here the link for downloading the memory.dmp file.
I wonder why?

Regards,

calamitag

 

[Patrick]

Hi,

DRIVER_POWER_STATE_FAILURE (9f)

This bug check indicates that the driver is in an inconsistent or invalid power state.

BugCheck 9F, {4, 258, fffffa800fdfd730, fffff80000b9c3d0}

1st parameter = 0x4, which implies that a power IRP has failed to synchronize with the PnP Manager.

0: kd> !locks
**** DUMP OF ALL RESOURCE OBJECTS ****
KD: Scanning for held locks..

Resource @ nt!IopDeviceTreeLock (0xfffff8000367bea0)    Shared 1 owning threads
    Contention Count = 1
     [COLOR=#4b0082]Threads: fffffa800fdf6660-01[/COLOR]<*> 
KD: Scanning for held locks.

Resource @ nt!PiEngineLock (0xfffff8000367bda0)    Exclusively owned
    Contention Count = 15
    NumberOfExclusiveWaiters = 3
     Threads: fffffa800fdf6660-01<*> 
     Threads Waiting On Exclusive Access:
              fffffa800fd6e040       fffffa800fdfd730       fffffa800fd84b50

0: kd> !thread [COLOR=#4b0082]fffffa800fdf6660[/COLOR]
[COLOR=#ff0000]*** ERROR: Module load completed but symbols could not be loaded for btwampfl.sys[/COLOR]

Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`0377e4d0 fffff800`0346d5f2 : fffffa80`0fdf6660 fffffa80`0fdf6660 00000000`00000000 00000000`00000008 : nt!KiSwapContext+0x7a
fffff880`0377e610 fffff800`0347d992 : 00000000`00000000 00000000`00000018 00000000`00000050 00000000`00000018 : nt!KiCommitThreadWait+0x1d2
fffff880`0377e6a0 fffff880`0b283a2a : fffffa80`14527770 00000000`00000000 fffffa80`41777400 fffff880`00000050 : [COLOR=#006400]nt!KeDelayExecutionThread+0x186[/COLOR]
fffff880`0377e710 fffff880`0b28365f : ffffffff`fffe7960 00000000`00000002 fffffa80`146ef030 00000000`00000000 : [COLOR=#800080]btwampfl+0x30a2a[/COLOR]
fffff880`0377e770 fffff880`0b5623ed : fffffa80`1470ac10 00000000`00000000 fffffa80`1470ac10 fffffa80`14e6e8a0 : [COLOR=#800080]btwampfl+0x3065f[/COLOR]
fffff880`0377e7e0 fffff880`0b561a92 : fffffa80`1470ac10 00000000`00000000 00000000`00000000 fffffa80`14e6e8a0 : [COLOR=#0000cd]bthport!BthHandleRemoveDevice+0xc1[/COLOR]
fffff880`0377e840 fffff880`0b561903 : fffffa80`14e6e8a0 fffff800`00000001 fffff880`0b5778c0 00000000`00000000 : [COLOR=#0000cd]bthport!BthHandlePnp+0x136[/COLOR]
fffff880`0377e8b0 fffff800`036e3571 : fffffa80`1470aac0 fffff880`0377e9b8 fffffa80`14e6e8a0 fffffa80`14e6e8a0 : [COLOR=#0000cd]bthport!BthDispatchPnp+0x73[/COLOR]
fffff880`0377e900 fffff800`038643a1 : fffffa80`14097060 00000000`00000000 fffffa80`14515890 00000000`00000801 : nt!IopSynchronousCall+0xe1
fffff880`0377e970 fffff800`0357a063 : fffff8a0`33b892d0 fffff8a0`33b892d0 00000000`00000018 00000000`00000000 : nt!IopRemoveDevice+0x101
fffff880`0377ea30 fffff800`03863ef4 : fffffa80`14515890 00000000`00000000 00000000`00000002 00000000`00000000 : nt!PnpRemoveLockedDeviceNode+0x1a3
fffff880`0377ea80 fffff800`03864000 : 00000000`00000000 fffffa80`0fdf6600 fffff8a0`400a4a20 00000000`00000000 : nt!PnpDeleteLockedDeviceNode+0x44
fffff880`0377eab0 fffff800`038640f9 : fffffa80`15797602 fffffa80`15797620 00000000`00000001 fffffa80`15797600 : nt!PnpDeleteLockedDeviceNodes+0xa0
fffff880`0377eb20 fffff800`03481261 : fffff800`03864080 fffff800`0361d2d8 fffffa80`0fdf6600 00000000`00000000 : nt!PnpDelayedRemoveWorker+0x79
fffff880`0377eb70 fffff800`0371373a : 00000000`00000000 fffffa80`0fdf6660 00000000`00000080 fffffa80`0fcf3b30 : nt!ExpWorkerThread+0x111
fffff880`0377ec00 fffff800`034688e6 : fffff880`0356d180 fffffa80`0fdf6660 fffff880`035780c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0377ec40 00000000`00000000 : fffff880`0377f000 fffff880`03779000 fffff880`0377e8a0 00000000`00000000 : nt!KxStartSystemThread+0x16

Looks like your Broadcom Bluetooth drivers aren't playing nice.

0: kd> lmvm btwampfl
start             end                 module name
fffff880`0b253000 fffff880`0b4dc000   btwampfl   (no symbols)           
    Loaded symbol image file: btwampfl.sys
    Image path: \SystemRoot\system32\drivers\btwampfl.sys
    Image name: btwampfl.sys
    Timestamp:        Mon Jul 12 21:41:18 [COLOR=#ff0000]2010[/COLOR]

No surprise, they're nearly 5 years old.

Update them ASAP - HP Drivers and Downloads for Printers, Scanners and More | HP ® Support

Regards,

Patrick

 

[calamitag]

Hello, thank you for your invaluable service you offer since so long. I've just checked the version of my bluetooth and it is the latest available from HP. I mean it was the one installed when the BSOD occurred. AFter a windows update check from Microsoft no other broadcom version is available.

Regards,

Calamitag

 

[Patrick]

I would contact HP and see if they have a driver they can offer you. If not, I would disable Bluetooth entirely, especially if you're not even using it.

Regards,

Patrick