Multiple BSODs with DRIVER_POWER_STATE_FAILURE at the top

Luke27 · 23 Aug 2014

Hi everyboy. I have tried to follow the instructions provided as closely as possible but am not technically equipped to be sure I've done all the right things in all the right ways.
I am unable to open the .dmp files in the zip folder that the DM log collector collected - WinSDK wont install the debugger that I would need to do that (apparently because I have a version of Visual C++ that's too new or something but, again, I am not equipped to sort that out myself).
I originally suspected the crashes were happening because of the battery I bought from a third party manufacturer - windows and lenovo power manager had started telling me that it would need to be replaced soon shortly before they started happening.
So I started to use the laptop plugged in, without the battery in at all, and that worked for a while. But recently I've had a few separate BSOD crashes whilst in that state. I tried to use the driver verifier in its standard settings (yes, I failed to follow the instructions properly, a thousand apologies) and that caused a crash but no obviously useful information was forthcoming

.

- So now I've come to you for help.

Arc · 24 Aug 2014

Disable Driver Verifier at once.

Uninstall Networx.

Free up the startup. Windows does not need any other program to auto start with it, but the auto start programs often conflicts and causes various problems including BSODs.

Click on the Start button
Type “msconfig (without quotes), click the resulting link. It will open the System Configuration window.
Select the “Startup” tab.
Deselect all items other than the antivirus (you may keep F.lux).
Apply > OK
Accept then restart.

F5521gw Mobile Broadband Driver.

Code:

BugCheck 9F, {3, fffffa8006738870, fffff80000b9c3d8, fffffa80041af170}

*** WARNING: Unable to verify timestamp for wwussf64.sys
*** ERROR: Module load completed but symbols could not be loaded for wwussf64.sys
Probably caused by : wwussf64.sys

Followup: MachineOwner
---------

Code:

          Unable to load image \SystemRoot\system32\DRIVERS\WwanUsbMp64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WwanUsbMp64.sys
*** ERROR: Module load completed but symbols could not be loaded for WwanUsbMp64.sys
 \Driver\WwanUsbServ
            Args: 00041100 00000001 00000001 00000002

Update the driver. Dont keep it active when the computer is going to sleep.

Let us know how it runs. Further troubleshooting actions will be required, I guess.

Luke27 · 24 Aug 2014

will try. many thanks

Luke27 · 27 Aug 2014

I did this and it seems to have worked - no BSOD errors since. Many many thanks.

Arc · 27 Aug 2014

Good news. Let us know for any further issue.

Luke27 · 08 Sep 2014

Nooooo. It started doing it again!

Arc · 08 Sep 2014

The mobile broadband driver is still causing the issue.

Code:

Name    [00000021] F5521gw Mobile Broadband Driver
Adapter Type    Wireless
Product Type    F5521gw Mobile Broadband Driver
Driver    c:\windows\system32\drivers\wwanusbmp64.sys (7.2.8.1, 278.23 KB (284 912 bytes), 2013/11/22 03:22 PM)

Code:

            Args: 00000000 00000000 00000000 00000000
 [ 16, 0]   0  0 fffffa8007e24b90 00000000 fffff88001708b30-fffffa80085271a0    
           \Driver\ecnssndisfltr    ndis!ndisSetDevicePowerOnComplete
            Args: 00000000 00000000 00000000 00000002
>[ 16, 2]   0 e1 fffffa8008527050 00000000 00000000-00000000    pending
          Unable to load image \SystemRoot\system32\DRIVERS\WwanUsbMp64.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for WwanUsbMp64.sys
*** ERROR: Module load completed but symbols could not be loaded for WwanUsbMp64.sys
 \Driver\WwanUsbServ
            Args: 00041100 00000001 00000001 00000002

If this device is active when the computer is going to sleep, it will cause a BSOD.

Luke27 · 10 Sep 2014

Hmm, I reinstalled that driver last time and it stopped crashing for a while (which I've done again now). but now its having trouble with it again. how does that work? Also when I checked the driver version on the device manager it shows an older version than the one I installed which is now listed in the programme manager. So confusing.
Anyway, it hasn't been doing it since i reinstalled and the device has been off most of the time since then - I'll try to remember the sleep thing.
Thanks

Arc · 10 Sep 2014

Its ok, let us know for any further issue.