[steveapathy]

I upgraded to 64-bit Windows 7 Home Premium about 2 days ago (from Vista Home Premium, SP2) and have experienced at least 3 BSoD's all from "driver power state failure." When Windows boots back up, I get the following description

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA8005E34A00
BCP3: FFFFF80000B9C4D8
BCP4: FFFFFA80049DB8B0
OS Version: 6_1_7600
Service Pack: 0_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\121409-27768-01.dmp
C:\Users\Steve\AppData\Local\Temp\WER-96642-0.sysdata.xml

I have attached the .dmp file mentioned. The other doesn't seem to actually exist.

Avast, Ad-Aware and Spybot S&D all came up with nothing.

I'm not positive all of the information you need or where to get it. I have minimal technical computer troubleshooting experience. Please let me know how I can help you help me.

 

[steveapathy]

I found the troubleshooting guide by luck in another thread, so I think I now have all the right files you need. They should be attached to this post.

 

[steveapathy]

I got a new message after another DPSF BSoD

Can anybody spare the time to help?

 

[usasma]

Most likely it's due to mausbft.sys dated Wed Feb 11 18:45:31 2009, which probably belongs to your M-Audio USB Audio Driver (WDM) by Avid Technology, Inc.
All 3 dump files point to it as the cause.

1 - download the latest version of the driver from the device manufacturer's website
2 - uninstall the current drivers from your system
3 - install the freshly downloaded drivers
4 - test by waiting for another BSOD.

Here's the memory dump analysis summaries:

Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Sat Dec 12 09:30:18.210 2009 (GMT-5)
System Uptime: 0 days 13:42:15.209
BugCheck 9F, {3, fffffa8005552a00, fffff80000b9c4d8, fffffa8004a1c010}
*** WARNING: Unable to verify timestamp for mausbft.sys
*** ERROR: Module load completed but symbols could not be loaded for mausbft.sys
Probably caused by : mausbft.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec 14 18:03:30.482 2009 (GMT-5)
System Uptime: 0 days 13:40:56.354
BugCheck 9F, {3, fffffa8005e34a00, fffff80000b9c4d8, fffffa80049db8b0}
*** WARNING: Unable to verify timestamp for mausbft.sys
*** ERROR: Module load completed but symbols could not be loaded for mausbft.sys
Probably caused by : mausbft.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Debug session time: Mon Dec 14 04:21:24.275 2009 (GMT-5)
System Uptime: 1 days 18:19:55.114
BugCheck 9F, {3, fffffa8005b22a00, fffff80000b9c4d8, fffffa80070abc10}
*** WARNING: Unable to verify timestamp for mausbft.sys
*** ERROR: Module load completed but symbols could not be loaded for mausbft.sys
Probably caused by : mausbft.sys
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  System

 

[steveapathy]

Thanks a lot. I'll update in a couple of days if it doesn't return.

 

[steveapathy]

Just an update:

After uninstalling the m-box software and drivers, and then re-installing with updated drivers, I haven't gotten a single BSOD. Consider this one [Solved]

 

[usasma]

Glad to hear it, thanks for letting us know!