Applies to


Fernly32 asked on


I've recently been getting crashes of the type DRIVER_POWER_STATE_FAILURE. Actually the first 2 crashes didn't even result in a blue screen, simply a freeze with speakers glitching. Only the third time it gave the error. I read some threads and checked out the minidump files using blueScreenViewer, and it says the files causing these crashes (respectively) are

1. ntoskrnl.exe 2. ntoskrnl.exe and Wdf01000.sys 3.  ntoskrnl.exe and Mbm3DevMt.sys

I can't actually identify these drivers properly.  Mbm3DevMt.sys seems to be a dell one which I've updated, but I want to make sure I adjust anything else that I need to. The other two are Microsoft kernel files? I'm not sure if (and how) I need to update those.

I'd appreciate if someone could give me a hand, please!

Thanks in advance.

4 people had this question

Abuse history

The answered status icon Answer
Patrick Barker replied on


All of the attached DMP files are of the DRIVER_POWER_STATE_FAILURE (9f) bugcheck.

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

If we run an !irp on the 4th parameter of the bugcheck (blocked IRP address), we get the following:

>[ 16, 2]   0 e1 fffffa8008805050 00000000 fffff80002e7c6f0-fffffa8005d993d0 Success Error Cancel 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    nt!IopUnloadSafeCompletion

WwanUsbMp64.sys is the Dell Wireless 5530 HSPA Mini-Card Network Adapter driver.

We also have:

*** 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

wwussf64.sys is the SSNDIS filter service from Dell as well.


1. Update your Dell Wireless drivers ASAP -

2. In your loaded drivers list, dtsoftbus01.sys is listed which is the Daemon Tools driver. Daemon Tools is a very popular cause of BSOD's in 7/8 based systems. Please uninstall Daemon Tools. Alternative imaging programs are: MagicISO, Power ISO, etc.

3. If the above do not help, please enable Driver Verifier to look for further device driver corruption and or conflicts:

Driver Verifier:

What is Driver Verifier?

Driver Verifier is included in Windows 8, 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008, Windows 2000, Windows XP, and Windows Server 2003 to promote stability and reliability; you can use this tool to troubleshoot driver issues. Windows kernel-mode components can cause system corruption or system failures as a result of an improperly written driver, such as an earlier version of a Windows Driver Model (WDM) driver.

Essentially, if there's a 3rd party driver believed to be at issue, enabling Driver Verifier will help flush out the rogue driver if it detects a violation.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8 -

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (Windows 7 & 8)
- DDI compliance checking (Windows 8)
- Miscellaneous Checks
4. Select  - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is [B]NOT[/B] provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- If Driver Verifier finds a violation, the system will BSOD.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will flag it, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.
If you did not set up a restore point, do not worry, you can still disable Driver Verifier to get back into normal Windows:

- Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.
・    Restart and boot into normal Windows.

How long should I keep Driver Verifier enabled for?

It varies, many experts and analysts have different recommendations. Personally, I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier.

My system BSOD'd, where can I find the crash dumps?

They will be located in %systemroot%\Minidump

Any other questions can most likely be answered by this article:


Debugger/Reverse Engineer.
2 people found this helpful

Abuse history

The answered status icon Answer


These were Related to WwanUsbMp64.sys WWAN Wireless Module Device Driver from Ericsson AB.  Yours is from 2010.  I woul re-install the newest driver available.

I wuold also remove or update the software Related to Mbm3DevMt.sys F3607gw Mobile Broadband Device Management Driver from MCCI Corporation

Cat herder
Windows Insider MVP
MVP-Windows and Devices for IT
Be the first person to mark this helpful

Abuse history