Blue Screen Following Standby

missllewell · 26 Dec 2009

We've been experiencing shut-down problems for a while now. I think it has been since we installed some software/hardware that does not yet have drivers for windows 7 and we are using it in compatability mode. The hardware - an interface for my husband to use while he records music on the pc - does have pudated drivers but the software does not. We are not using the windows 7 driver for the hardware because the software will not detect it otherwise.
We bought the computer specifically for this programme as our laptop did not have the capability to run it efficiently.
We think that leaving the harddrive plugged in when the computer goes to standby may contribute but we haven't really been paying attention. When it happened the most recent time I unplugged the harddrive before taking the computer out of standby. I have been using the computer for a good 10mins before bluescreen happened. There was a message it had happened before that but I don't know when or why.

The blue screen shows (I think) DRIVE_POWER_STATE_FAILURE. I have attached the minidump details as requested.

I have read a number of threads on here, all with different advice and, as I do not have any technical knowledge regdaring computers, I am reluctant to try anything that involves restoring factory settings or losing information without instructions I actually understand.

Information I can find to provide is...
Processor: Intel Core 2 Quad CPU Q8200 @ 2.33GHz 2.33GHz
RAM: 6 GB
Systerm type: 64-bit
C: 1TB

Thanks :)

**Pauly** · 26 Dec 2009

Can we have some more details about the device you are talking about, and how its connected to the computer

All but one of the dump files report Bugcheck 0x9F Driver_Power_State_Failure
So this is a driver issue but we need to find the offending one

Will report back shortly

**Pauly** · 26 Dec 2009

All dumps are pointing at mausbft.sys

This seems to be a driver for M-Audio/Midiman USB device so im guessing this is what you where talking about

I would start by removing this driver to see if your system becomes stable again
If it does then we can look at getting the device installed and working correctly
Give us the exact device you are using and may be able to find a better driver

missllewell · 30 Dec 2009

Hi Pauly - thanks for the prompt reply.

It's definately the M-Audio USB wotsit. The bluescreen only happens when the interface/hardware is connected and the computer is left to go into standby. If it's unplugged after use it doesn't happen.
We'd still like to get to the bottom of it. I have now uninstalled the driver. I will leave it to go into sleep mode and I doubt it will blue screen.

We are using the vista version of the USB interface's driver because the windows 7 version does not display as 'M-Audio Fast Track USB' (only as 'M-Audio Fast Track) and the software does not recognise the device. I don't know if this will be rectified until M-Audio come up with a software driver for windows 7... if they do.

Any help you can give us would be helpful. We had been on the m-audio website and used the forums there but they just said 'yeah, it happens' and left it at that.

Cheers

zigzag3143 · 30 Dec 2009

missllewell said:

We've been experiencing shut-down problems for a while now. I think it has been since we installed some software/hardware that does not yet have drivers for windows 7 and we are using it in compatability mode. The hardware - an interface for my husband to use while he records music on the pc - does have pudated drivers but the software does not. We are not using the windows 7 driver for the hardware because the software will not detect it otherwise.
We bought the computer specifically for this programme as our laptop did not have the capability to run it efficiently.
We think that leaving the harddrive plugged in when the computer goes to standby may contribute but we haven't really been paying attention. When it happened the most recent time I unplugged the harddrive before taking the computer out of standby. I have been using the computer for a good 10mins before bluescreen happened. There was a message it had happened before that but I don't know when or why.

The blue screen shows (I think) DRIVE_POWER_STATE_FAILURE. I have attached the minidump details as requested.

I have read a number of threads on here, all with different advice and, as I do not have any technical knowledge regdaring computers, I am reluctant to try anything that involves restoring factory settings or losing information without instructions I actually understand.

Information I can find to provide is...
Processor: Intel Core 2 Quad CPU Q8200 @ 2.33GHz 2.33GHz
RAM: 6 GB
Systerm type: 64-bit
C: 1TB

Thanks :)

Hi and welcome. it is as you fear the M-Audio USB Audio Driver (WDM) by Avid .. I appears in all but one. Whats is happening is the driver is taking too long to respond and the OS thinks there is something serious wrong chrashes the system to prevent damage. here is the link to its home page. they may have a newer driver. Can't uninstall! [Archive] - The Official M-Audio User Forums.

You can alse run a systems file check to verify and repair any system files. It is safe to do and easy. Just type CMD in search. Right click the top and "run as administrator" then type sfc /scannow

Ken J+

Code:

122509-25428-01.dmp    12/25/2009 5:13:04 PM    APC_INDEX_MISMATCH    0x00000001    00000000`776cff2a    00000000`00000000    00000000`0000fffd    fffff880`0980bca0    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121109-23743-01.dmp    12/11/2009 8:27:40 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`05dc0a00    fffff800`041b9518    fffffa80`05cedc60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121209-25100-01.dmp    12/12/2009 11:08:42 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0551ca00    fffff800`00b9c518    fffffa80`09e8f010    netr28x.sys    netr28x.sys+54083                    
121209-25818-01.dmp    12/12/2009 12:24:44 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`053db060    fffff800`00b9c518    fffffa80`09051010    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121209-43383-01.dmp    12/12/2009 1:44:14 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`05d0b060    fffff800`00b9c518    fffffa80`09a98010    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121309-22807-01.dmp    12/13/2009 11:17:02 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`08954520    fffff800`00b9c518    fffffa80`05856010    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121309-25100-01.dmp    12/13/2009 3:21:30 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`08c608b0    fffff800`041b9518    fffffa80`059ebc60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121309-25490-01.dmp    12/13/2009 10:09:48 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`058085d0    fffff800`00b9c518    fffffa80`05e08c60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121609-23088-01.dmp    12/16/2009 2:37:32 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`077dd060    fffff800`00b9c518    fffffa80`058e4a90    USBPORT.SYS    USBPORT.SYS+12921                    
121609-24492-01.dmp    12/16/2009 3:41:58 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`091d0060    fffff800`00b9c518    fffffa80`05673010    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122409-34289-01.dmp    12/24/2009 11:31:06 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`056373e0    fffff800`041be518    fffffa80`055fc9c0    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122609-26379-01.dmp    12/26/2009 9:16:04 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`08d8ba00    fffff800`00b9c518    fffffa80`05505c60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122609-29780-01.dmp    12/26/2009 8:02:34 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0991d260    fffff800`00b9c518    fffffa80`099abb10    ntoskrnl.exe    ntoskrnl.exe+71f00

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\K\Desktop\Minidump\121609-23088-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?fffff800`00b9c500?
Symbol search path is: SRV*d:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02c51000 PsLoadedModuleList = 0xfffff800`02e8ee50
Debug session time: Tue Dec 15 21:35:45.845 2009 (GMT-5)
System Uptime: 0 days 3:03:56.014
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa80077dd060, fffff80000b9c518, fffffa80058e4a90}

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

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

0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80077dd060, Physical Device Object of the stack
Arg3: fffff80000b9c518, Functional Device Object of the stack
Arg4: fffffa80058e4a90, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa80058e4a90

DEVICE_OBJECT: fffffa8007787e10

DRIVER_OBJECT: fffffa8009cd36d0

IMAGE_NAME:  mausbft.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  48a5cf0a

MODULE_NAME: mausbft

FAULTING_MODULE: fffff880088f6000 mausbft

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d31e23 to fffff80002cc2f00

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`02d31e23 : 00000000`0000009f 00000000`00000003 fffffa80`077dd060 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`02ccefa6 : fffff800`00b9c600 fffff800`00b9c600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`00b9c570 fffff800`02cce326 : fffff800`02e71700 00000000`000acb68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`00b9c5e0 fffff800`02ccee7e : 00000019`b1fa2aae fffff800`00b9cc58 00000000`000acb68 fffff800`02e3ef88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`02cce697 : 00000005`dad75bc1 00000005`000acb68 00000005`dad75b9f 00000000`00000068 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`02ccb6fa : fffff800`02e3be80 fffff800`02e49c40 00000000`00000000 fffff880`01482414 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_mausbft.sys

BUCKET_ID:  X64_0x9F_IMAGE_mausbft.sys

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

missllewell · 30 Dec 2009

zigzag3143 said:

here is the link to its home page. they may have a newer driver.

Hi. thanks for the information. As I said, we were using the win7 driver for the hardware but there isn't one yet for the software so the software wasn't recognising the device and would not work. That is why we are using an older version of the driver. If we use the newest version we cannot use the programme at all.

missllewell · 30 Dec 2009

GrrrArgh!

I uninstalled the driver and put it into sleep mode but it happened again! Same message. The interface was still plugged in but not recognised by windows at all as the driver was uninstalled.

I have attached a zipped minidump again...

zigzag3143 · 30 Dec 2009

missllewell said:

GrrrArgh!

I uninstalled the driver and put it into sleep mode but it happened again! Same message. The interface was still plugged in but not recognised by windows at all as the driver was uninstalled.

I have attached a zipped minidump again...

Hi

I have no problems re reading even the same dumps, but they are just going to keep saying the same thing. Driver_POWER_STATE_FAILURE.

maybe I am missing something here. can you re explain (yeah i am being dense) this is just an audio device (hardware) and a driver(software) right?

Code:

122509-25428-01.dmp    12/25/2009 5:13:04 PM    APC_INDEX_MISMATCH    0x00000001    00000000`776cff2a    00000000`00000000    00000000`0000fffd    fffff880`0980bca0    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122909-25786-01.dmp    12/29/2009 10:38:28 PM    APC_INDEX_MISMATCH    0x00000001    00000000`77abff2a    00000000`00000000    00000000`0000fffd    fffff880`0a765ca0    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121109-23743-01.dmp    12/11/2009 8:27:40 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`05dc0a00    fffff800`041b9518    fffffa80`05cedc60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121209-25100-01.dmp    12/12/2009 11:08:42 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0551ca00    fffff800`00b9c518    fffffa80`09e8f010    netr28x.sys    netr28x.sys+54083                    
121209-25818-01.dmp    12/12/2009 12:24:44 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`053db060    fffff800`00b9c518    fffffa80`09051010    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121209-43383-01.dmp    12/12/2009 1:44:14 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`05d0b060    fffff800`00b9c518    fffffa80`09a98010    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121309-22807-01.dmp    12/13/2009 11:17:02 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`08954520    fffff800`00b9c518    fffffa80`05856010    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121309-25100-01.dmp    12/13/2009 3:21:30 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`08c608b0    fffff800`041b9518    fffffa80`059ebc60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121309-25490-01.dmp    12/13/2009 10:09:48 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`058085d0    fffff800`00b9c518    fffffa80`05e08c60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
121609-23088-01.dmp    12/16/2009 2:37:32 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`077dd060    fffff800`00b9c518    fffffa80`058e4a90    USBPORT.SYS    USBPORT.SYS+12921                    
121609-24492-01.dmp    12/16/2009 3:41:58 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`091d0060    fffff800`00b9c518    fffffa80`05673010    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122409-34289-01.dmp    12/24/2009 11:31:06 AM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`056373e0    fffff800`041be518    fffffa80`055fc9c0    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122609-26379-01.dmp    12/26/2009 9:16:04 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`08d8ba00    fffff800`00b9c518    fffffa80`05505c60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122609-29780-01.dmp    12/26/2009 8:02:34 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0991d260    fffff800`00b9c518    fffffa80`099abb10    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122709-23602-01.dmp    12/27/2009 5:04:34 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`0565d060    fffff800`041b9518    fffffa80`056ba950    ntoskrnl.exe    ntoskrnl.exe+71f00                    
122809-25318-01.dmp    12/28/2009 3:24:36 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`095b3780    fffff800`00b9c518    fffffa80`0555fc60    ntoskrnl.exe    ntoskrnl.exe+71f00                    
123009-27674-01.dmp    12/30/2009 3:05:58 PM    DRIVER_POWER_STATE_FAILURE    0x0000009f    00000000`00000003    fffffa80`05559a00    fffff800`041c4518    fffffa80`0ab87c60    ntoskrnl.exe    ntoskrnl.exe+71f00

missllewell · 30 Dec 2009

There is a programme, called Session, through which you can build and record songs. This uses a driver but does not have a driver for win7.

There is an external interface, the M-Audio Fast Track USB (not the same as the M-Audio Fast Track) that attaches to the computer by a USB (you plug your guitar into in and it links to Session) this also has a driver. There is a win7 driver available for this interface but when you use it Session does not recognise the device and you can't record anything. This is why we are using the vista drivers for both Session and the Fast Track USB in compatibility mode which has since caused the blue screen.

The new mini dump has been attached so it includes the ones that have occured since my first post - I didn't know if the information will have changed or not.