Please Safe Me From BSOD Hell Fast Track Pro Windows 7 64 bit - The Official M-Audio User Forums

kyklovod · #1 10-19-2009, 03:08 PM

I will go crazy .. My PC restarts several times per day....
Please help! It was no connection with system sleep or hibernate.It crashed when I work at PC.

Using Windows 7 Professional 64 bit with latest beta drivers
It was same with official v3 64 bit driver for Vista

Here is fragment of dump file. I attach whole log file below

************************************************** *****************************
* *
* 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: fffffa8004872060, Physical Device Object of the stack
Arg3: fffff80004d5d518, Functional Device Object of the stack
Arg4: fffffa8004119c60, 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: fffffa8004119c60

DEVICE_OBJECT: fffffa8005be1e10

DRIVER_OBJECT: fffffa8005be0e70

IMAGE_NAME: mausb.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 48af5813

MODULE_NAME: mausb

FAULTING_MODULE: fffff880084a2000 mausb

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from fffff80003742e23 to fffff800036d3f00

STACK_TEXT:
fffff800`04d5d4c8 fffff800`03742e23 : 00000000`0000009f 00000000`00000003 fffffa80`04872060 fffff800`04d5d518 : nt!KeBugCheckEx
fffff800`04d5d4d0 fffff800`036dffa6 : fffff800`04d5d600 fffff800`04d5d600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`04d5d570 fffff800`036df326 : fffffa80`05b6c168 fffffa80`05b6c168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`04d5d5e0 fffff800`036dfe7e : 00000017`f4a687c4 fffff800`04d5dc58 00000000`000a1053 fffff800`0384fce8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04d5dc30 fffff800`036df697 : 00000005`b039b4c2 00000005`000a1053 00000005`b039b47a 00000000`00000053 : nt!KiTimerExpiration+0x1be
fffff800`04d5dcd0 fffff800`036dc6fa : fffff800`0384ce80 fffff800`0385ac40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04d5dd80 00000000`00000000 : fffff800`04d5e000 fffff800`04d58000 fffff800`04d5dd40 00000000`00000000 : nt!KiIdleLoop+0x5a

STACK_COMMAND: kb

FOLLOWUP_NAME: MachineOwner

FAILURE_BUCKET_ID: X64_0x9F_IMAGE_mausb.sys

BUCKET_ID: X64_0x9F_IMAGE_mausb.sys

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

rax=fffff800038775f8 rbx=fffffa8004119c60 rcx=000000000000009f
rdx=0000000000000003 rsi=fffffa8007e22840 rdi=0000000000000000
rip=fffff800036d3f00 rsp=fffff80004d5d4c8 rbp=0000000000000001
r8=fffffa8004872060 r9=fffff80004d5d518 r10=0000000000000000
r11=0000000000008000 r12=fffffa8004119c60 r13=0000000000000000
r14=0000000000000001 r15=fffff800038822d0
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00000246
nt!KeBugCheckEx:
fffff800`036d3f00 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`04d5d4d0=000000000000009f
Child-SP RetAddr : Args to Child : Call Site
fffff800`04d5d4c8 fffff800`03742e23 : 00000000`0000009f 00000000`00000003 fffffa80`04872060 fffff800`04d5d518 : nt!KeBugCheckEx
fffff800`04d5d4d0 fffff800`036dffa6 : fffff800`04d5d600 fffff800`04d5d600 00000000`00000001 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x29330
fffff800`04d5d570 fffff800`036df326 : fffffa80`05b6c168 fffffa80`05b6c168 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x66
fffff800`04d5d5e0 fffff800`036dfe7e : 00000017`f4a687c4 fffff800`04d5dc58 00000000`000a1053 fffff800`0384fce8 : nt!KiProcessExpiredTimerList+0xc6
fffff800`04d5dc30 fffff800`036df697 : 00000005`b039b4c2 00000005`000a1053 00000005`b039b47a 00000000`00000053 : nt!KiTimerExpiration+0x1be
fffff800`04d5dcd0 fffff800`036dc6fa : fffff800`0384ce80 fffff800`0385ac40 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`04d5dd80 00000000`00000000 : fffff800`04d5e000 fffff800`04d58000 fffff800`04d5dd40 00000000`00000000 : nt!KiIdleLoop+0x5a

jon.acker · #2 10-20-2009, 12:36 PM

I get the same thing - seems to be a problem with Vista and the M-Audio drivers (in my case it's the Fast Track Pro). Still awaiting a response from them.

Paul · #3 10-20-2009, 02:53 PM

kyklovod,

Set the Power Options in Windows 7 to Best Performance.

You need to provide more system information. Please refer to this thread for the preferred means of providing this information.

jon.acker · #4 10-31-2009, 12:28 PM

Make/Model: ASUS F3Jr
Operating System: Vista Home Premium
Processor: Intel Core Duo / T2450 2GHz
RAM: 2GB
M-Audio Devices & Driver Versions: Fast Track Pro / 5.1.0.00.5119

Between 10-30 minutes after resuming from sleep the laptop suddenly shuts down with a blue screen:
DRIVER_POWER_STATE_FAILURE

If this is the first time etc...
Technical Information:
STOP: 0x0000009F (0x00000003, 0x88147030, 0x87F93EE8, 0X85760D0)

Have tried modifiying the USB power to be always on (as someone suggested to me). Also tried reinstalling the drivers.

The problem does not occur when the M-Audio driver is disabled.

kyklovod · #5 11-02-2009, 09:57 AM

seems like problem gone with driver version 5.10.0.5131

jon.acker · #6 11-04-2009, 12:01 PM

Good to hear. But I can't see that driver release on m-audios driver list for vista. Where did you get it?

TheEastGateMS · #7 11-04-2009, 01:08 PM

Yes, please, a resolution to this would be greatly appreciated!

buddypepper · #8 11-04-2009, 05:36 PM

Same thing here - where do you get 5.10.0.5131 from?

Paul · #9 11-05-2009, 02:57 PM

The latest Windows drivers would be the Windows 7 beta drivers. These drivers should also work on XP and Vista.

http://forums.m-audio.com/forumdisplay.php?f=164

jon.acker · #10 11-07-2009, 02:21 AM

Thanks for that link Paul. I tried the new beta driver - but the same problem occurred. The only difference was that on resume from sleep the fast-track-pro wasn't visible on the device list and didn't work. About 15 minutes later I had the blue screen again.
Is there no standard way to debug this? I tried looking for a minidump after the crash but windows doesn't seem to have created one. Also, there are no obvious leads on the events log - the only thing logged is in the Administrative events:
"The previous system shutdown at 10:00:27 on 07/11/2009 was unexpected.", etc.