BSOD Driver Power State Failure

I have attached the files has requested.

I am having varying instances of Driver Power State failures as indicated by the BSOD This only happens when using the internet and I cant figure out which file is causing the shutdown.

Also interesting: I use my computer for home recording with an M-Audio interface, Blue Snowball Microphone, and Alesis M1Active 320USB studio monitors.
While recording or playing back in the Studio SONAR7, the program seems to just randomly start working at half speed and getting all jumpy. I will stop it rewind a bit and start it again and it is fine for a bit and then will start doing it again. Any Ideas on this? could this be linked to the same problem that is giving me the BSOD?

Kurt301 said:

I have attached the files has requested.

I am having varying instances of Driver Power State failures as indicated by the BSOD This only happens when using the internet and I cant figure out which file is causing the shutdown.

Also interesting: I use my computer for home recording with an M-Audio interface, Blue Snowball Microphone, and Alesis M1Active 320USB studio monitors.
While recording or playing back in the Studio SONAR7, the program seems to just randomly start working at half speed and getting all jumpy. I will stop it rewind a bit and start it again and it is fine for a bit and then will start doing it again. Any Ideas on this? could this be linked to the same problem that is giving me the BSOD?

Hi Kurt and Welcome

These were all virtually identical and caused by your mausb.sys driver. M-Audio Fast Track Pro PNP Device ID USB\VID_0763&PID_2012\5&BD40FB&0&4 Driver c:\windows\system32\drivers\mausb.sys

I would remove it to test.

Code:

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


Loading Dump File [C:\Users\JMH\Desktop\Windows_NT6_BSOD_jcgriff2\050911-36909-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

DbsSplayTreeRangeMap::Add: ignoring zero-sized range at ?ffffffff`82b5fad4?
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16695.x86fre.win7_gdr.101026-1503
Machine Name:
Kernel base = 0x82a39000 PsLoadedModuleList = 0x82b81810
Debug session time: Mon May  9 11:11:31.240 2011 (GMT-4)
System Uptime: 0 days 1:19:03.254
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
........
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 00000003, A device object has been blocking an Irp for too long a time
Arg2: 859c06a8, Physical Device Object of the stack
Arg3: 82b5fae0, Functional Device Object of the stack
Arg4: 86aeceb8, The blocked IRP

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

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

DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  86aeceb8

DEVICE_OBJECT: 859ad578

DRIVER_OBJECT: 8598f3f8

IMAGE_NAME:  mausb.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  47d6f315

MODULE_NAME: mausb

FAULTING_MODULE: 8eb04000 mausb

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from 82a75044 to 82b15dfc

STACK_TEXT:  
82b5fa94 82a75044 0000009f 00000003 859c06a8 nt!KeBugCheckEx+0x1e
82b5fb00 82a748d8 82b5fbac 00000000 82b6c280 nt!PopCheckIrpWatchdog+0x1f5
82b5fb38 82aa316d 82b7aa20 00000000 6099d5c6 nt!PopCheckForIdleness+0x73
82b5fb7c 82aa3111 82b62d20 82b5fca8 00000001 nt!KiProcessTimerDpcTable+0x50
82b5fc68 82aa2fce 82b62d20 82b5fca8 00000000 nt!KiProcessExpiredTimerList+0x101
82b5fcdc 82aa134e 0004a3b4 85c085b0 82b6c280 nt!KiTimerExpiration+0x25c
82b5fd20 82aa1178 00000000 0000000e 00000000 nt!KiRetireDpcList+0xcb
82b5fd24 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  0x9F_IMAGE_mausb.sys

BUCKET_ID:  0x9F_IMAGE_mausb.sys

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

0: kd> lmvm mausb
start    end        module name
8eb04000 8eb25700   mausb    T (no symbols)           
    Loaded symbol image file: mausb.sys
    Image path: \SystemRoot\system32\DRIVERS\mausb.sys
    Image name: mausb.sys
    Timestamp:        Tue Mar 11 17:01:09 2008 (47D6F315)
    CheckSum:         0002B505
    ImageSize:        00021700
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Got it. Turns out I had the wrong driver for that device. The one I had on there was a driver for another product they make called the Audiophile digital interface. It was similar enough to let my fast track pro work but still it would cause a conflict and of course the BSOD followed.

I couldnt have found it without your help thank you very much, where do I send the cookies?

Thanks for reporting back.
It is appreciated.
Safe surfing.