Avid Pro Audio Community

Avid Pro Audio Community (https://duc.avid.com/index.php)
-   FireWire & USB Audio Interfaces (Win) (https://duc.avid.com/forumdisplay.php?f=19)
-   -   Problem with M-Audio Fast Track Pro driver (https://duc.avid.com/showthread.php?t=422730)

antoniofr 12-06-2022 02:47 PM
Problem with M-Audio Fast Track Pro driver
 
Hello!


I am having problems with M-Audio Fast Track Pro ASIO driver and Cubase 12 in Windows 10. I am having error DRIVER_POWER_STATE_FAILURE on shutdown or rebooting. Error does not occur everytime, only sometimes, but always on rebooting or shutting down and always after using Cubase 12. Screens turn off but computer remains on, and after some minutes, it reboots or shut down with the error and a dump file is generated. If you analyze dump file, the error is:

Code:
DRIVER_POWER_STATE_FAILURE (9F)
*** WARNING: Unable to verify timestamp for MAudioFastTrackPro.sys
You can download dump file here: https://drive.google.com/file/d/1xW6...usp=share_link


I have used this sound card for many years with Cubase 5 and I have no problems until now, when I am using Cubase 12. I have not changed nothing in my system, except Cubase.


Full analysis of dump file:

Code:
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\120622-5062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                        Time (ms)    Location
Deferred                                      srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`5ba00000 PsLoadedModuleList = 0xfffff802`5c62a2f0
Debug session time: Tue Dec  6 21:31:26.021 2022 (UTC + 1:00)
System Uptime: 0 days 1:04:26.645
Loading Kernel Symbols
...............................................................
................................................................
...............................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`5bdf9290 48894c2408      mov    qword ptr [rsp+8],rcx ss:0018:fffff802`61a73820=000000000000009f
0: kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffc9080f74bba0, Physical Device Object of the stack
Arg3: fffff80261a73850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc90811f87aa0, The blocked IRP

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

Implicit thread is now ffffc908`1021c080
*** WARNING: Unable to verify timestamp for MAudioFastTrackPro.sys
*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 4984

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 23317

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 6

    Key  : Analysis.Init.CPU.mSec
    Value: 358

    Key  : Analysis.Init.Elapsed.mSec
    Value: 8172

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 103

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9f

    Key  : Bugcheck.Code.Register
    Value: 0x9f

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  120622-5062-01.dmp

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffc9080f74bba0

BUGCHECK_P3: fffff80261a73850

BUGCHECK_P4: ffffc90811f87aa0

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffc9081021c080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffff8a83`42bf53f0 fffff802`5bc13110    : ffff8c00`e5ca4180 ffff8a83`00000000 fffff802`6c3af0e0 00000000`00000000 : nt!KiSwapContext+0x76
ffff8a83`42bf5530 fffff802`5bc1263f    : ffff8a83`00000004 fffff802`0000000b ffff8a83`42bf56f0 5ffb5c88`00000000 : nt!KiSwapThread+0x500
ffff8a83`42bf55e0 fffff802`5bc11ee3    : ffffc908`00000000 ffffc908`00000000 00000000`00000000 ffffc908`1021c1c0 : nt!KiCommitThreadWait+0x14f
ffff8a83`42bf5680 fffff802`6e7e27ae    : ffffc908`04513c60 00000000`00000000 ffffc908`125e9d00 ffff8a83`42bf5900 : nt!KeWaitForSingleObject+0x233
ffff8a83`42bf5770 ffffc908`04513c60    : 00000000`00000000 ffffc908`125e9d00 ffff8a83`42bf5900 00000000`00000000 : MAudioFastTrackPro+0x127ae
ffff8a83`42bf5778 00000000`00000000    : ffffc908`125e9d00 ffff8a83`42bf5900 00000000`00000000 00000000`00000000 : 0xffffc908`04513c60


SYMBOL_NAME:  MAudioFastTrackPro+127ae

MODULE_NAME: MAudioFastTrackPro

IMAGE_NAME:  MAudioFastTrackPro.sys

STACK_COMMAND:  .process /r /p 0xffffc90802c900c0; .thread 0xffffc9081021c080 ; kb

BUCKET_ID_FUNC_OFFSET:  127ae

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_MAudioFastTrackPro!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {856730f2-272a-3831-6802-9fb475f135ad}

Followup:    MachineOwner
---------
Memory dump analysis:


Code:
Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`5ba00000 PsLoadedModuleList = 0xfffff802`5c62a2f0
Debug session time: Tue Dec  6 21:31:26.021 2022 (UTC + 1:00)
System Uptime: 0 days 1:04:26.645
Loading Kernel Symbols
...............................................................
...............Page b9ce0 not present in the dump file. Type ".hh dbgerr004" for details
.................................................
...............................................................
Loading User Symbols

Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`5bdf9290 48894c2408      mov    qword ptr [rsp+8],rcx ss:0018:fffff802`61a73820=000000000000009f
0: kd> !analyze -v
*******************************************************************************
*                                                                            *
*                        Bugcheck Analysis                                    *
*                                                                            *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an IRP for too long a time
Arg2: ffffc9080f74bba0, Physical Device Object of the stack
Arg3: fffff80261a73850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc90811f87aa0, The blocked IRP

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

Implicit thread is now ffffc908`1021c080
Unable to load image \SystemRoot\System32\drivers\MAudioFastTrackPro.sys, Win32 error 0n2
Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3686

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 25037

    Key  : Analysis.IO.Other.Mb
    Value: 13

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 37

    Key  : Analysis.Init.CPU.mSec
    Value: 921

    Key  : Analysis.Init.Elapsed.mSec
    Value: 19949

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 107

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x9f

    Key  : Bugcheck.Code.KiBugCheckData
    Value: 0x9f

    Key  : Bugcheck.Code.Register
    Value: 0x9f

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1


FILE_IN_CAB:  MEMORY.DMP

BUGCHECK_CODE:  9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffc9080f74bba0

BUGCHECK_P3: fffff80261a73850

BUGCHECK_P4: ffffc90811f87aa0

DRVPOWERSTATE_SUBCODE:  3

FAULTING_THREAD:  ffffc9081021c080

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

STACK_TEXT: 
ffff8a83`42bf53f0 fffff802`5bc13110    : ffff8c00`e5ca4180 ffff8a83`00000000 fffff802`6c3af0e0 00000000`00000000 : nt!KiSwapContext+0x76
ffff8a83`42bf5530 fffff802`5bc1263f    : ffff8a83`00000004 fffff802`0000000b ffff8a83`42bf56f0 5ffb5c88`00000000 : nt!KiSwapThread+0x500
ffff8a83`42bf55e0 fffff802`5bc11ee3    : ffffc908`00000000 ffffc908`00000000 00000000`00000000 ffffc908`1021c1c0 : nt!KiCommitThreadWait+0x14f
ffff8a83`42bf5680 fffff802`6e7e27ae    : ffffc908`04513c60 00000000`00000000 ffffc908`125e9d00 ffff8a83`42bf5900 : nt!KeWaitForSingleObject+0x233
ffff8a83`42bf5770 fffff802`6e7e22eb    : ffffc908`0450c640 ffffc908`125e9d68 ffffc908`0450c758 ffffc908`125e9d00 : MAudioFastTrackPro+0x127ae
ffff8a83`42bf57c0 fffff802`6e7e01ca    : ffffc908`0450b100 ffffc908`11f87ed0 ffffc908`125e9d68 ffffc908`0450c840 : MAudioFastTrackPro+0x122eb
ffff8a83`42bf5800 fffff802`6e7ecb53    : ffffc908`0450b000 ffffc908`125e9d68 ffffc908`11f87ed0 ffffc908`125e9d68 : MAudioFastTrackPro+0x101ca
ffff8a83`42bf5830 fffff802`6e7d18de    : ffffc908`04508c20 ffffc908`00000001 ffffc908`00000001 ffffc908`125e9a00 : MAudioFastTrackPro+0x1cb53
ffff8a83`42bf5860 fffff802`6c3cb5c8    : ffffc908`125e9ab0 00000000`00000000 ffffc908`11f87e00 ffffc908`11f87a00 : MAudioFastTrackPro+0x18de
ffff8a83`42bf5890 fffff802`6c3c06a8    : ffffc908`11f87aa0 ffffc908`11f87ed0 ffffc908`125e9ab0 ffffc908`1021c180 : ks!CKsDevice::DispatchDeviceSetPowerIrp+0x208
ffff8a83`42bf58f0 fffff802`5bd96cff    : ffffc908`00000001 ffffc908`11f87aa0 ffff8a83`42bf5a40 fffff802`5bd979de : ks!CKsDevice::DispatchPower+0x1e8
ffff8a83`42bf5950 fffff802`5bc2a72d    : 00000000`00000000 fffff802`00000000 fffff802`59befac0 00000000`00000000 : nt!IopPoHandleIrp+0x3b
ffff8a83`42bf5980 fffff802`5bd98f89    : 00000000`00000002 ffff8c00`e5bea180 fffffc5a`12cfd1d7 fffff802`5bc1263f : nt!IofCallDriver+0x6d
ffff8a83`42bf59c0 fffff802`6e2416cd    : ffffc908`11f87aa0 ffffc908`0f8e0b30 ffffc908`11f87aa0 ffffc908`10dc9e30 : nt!IoCallDriver+0x9
ffff8a83`42bf59f0 fffff802`6e241023    : ffffc908`11f87aa0 ffffc908`0f8e0c80 ffff8c00`00000000 ffffc908`11f87aa0 : ksthunk!CKernelFilterDevice::DispatchIrp+0x249
ffff8a83`42bf5a50 fffff802`5bd96cff    : ffffc908`11f87aa0 ffff8a83`42bf5bf0 ffffc908`0f8e0c80 ffffc908`1021c1c0 : ksthunk!CKernelFilterDevice::DispatchIrpBridge+0x13
ffff8a83`42bf5a80 fffff802`5bc2a72d    : ffff8c00`e60f0000 00000008`00000000 00000000`00000000 fffff802`00000000 : nt!IopPoHandleIrp+0x3b
ffff8a83`42bf5ab0 fffff802`5bd98f89    : 00000000`00000000 ffff8a83`42bf5bf0 ffff8c00`e60fd000 00000000`00000000 : nt!IofCallDriver+0x6d
ffff8a83`42bf5af0 fffff802`6c2efd8d    : ffffc908`1021c080 ffff8a83`42bf5bf0 ffffc908`0f8e0c80 fffff802`5bd7aeb2 : nt!IoCallDriver+0x9
ffff8a83`42bf5b20 fffff802`5bd9e279    : ffffc908`0f8e0b30 ffffc908`11f87aa0 ffffc908`1021c080 ffffc908`1021c000 : aswSnx+0x3fd8d
ffff8a83`42bf5b70 fffff802`5bc71d85    : ffffffff`fa0a1f00 fffff802`5bd9e0a0 ffffc908`0ba85350 00000000`00000168 : nt!PopIrpWorker+0x1d9
ffff8a83`42bf5c10 fffff802`5be01ec8    : ffff8c00`e60ef180 ffffc908`1021c080 fffff802`5bc71d30 00000000`00000246 : nt!PspSystemThreadStartup+0x55
ffff8a83`42bf5c60 00000000`00000000    : ffff8a83`42bf6000 ffff8a83`42bf0000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  MAudioFastTrackPro+127ae

MODULE_NAME: MAudioFastTrackPro

IMAGE_NAME:  MAudioFastTrackPro.sys

STACK_COMMAND:  .process /r /p 0xffffc90802c900c0; .thread 0xffffc9081021c080 ; kb

BUCKET_ID_FUNC_OFFSET:  127ae

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_MAudioFastTrackPro!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {856730f2-272a-3831-6802-9fb475f135ad}

Followup:    MachineOwner
---------
Can you help me please?


Thank you!

albee1952 12-09-2022 04:54 PM
Re: Problem with M-Audio Fast Track Pro driver
 
Opinions vary, so here is mine: Look at this as an excuse to upgrade your interface. The FT Pro is hardly "pro" and M-Audio's biggest drawback was/is their drivers. Even the cheapest Focusrite USB boxes are going to sound better, and their drivers are much better.:o

Darryl Ramm 12-09-2022 05:45 PM
Re: Problem with M-Audio Fast Track Pro driver
 
It is a dead interface, it has not been supported for years. It's shuffled off its mortal coil. It's freakin snuffed it. And how badly it's nailed to it's perch is described here...

https://avid.secure.force.com/pkb/ar...ck-Pro-Drivers

The real question is how far can you throw that awful M-Audio box. Please post a video online of your throw.

There are many manufacturers of nice audio interface, with a very wide range of features/capabilities and price. Focusrite as Dave mentioned is a frequent default recommendation on DUC, especially the 2i2 as a beginner interface.

There are really nice products available from (in no particular order) UAD, Motu, Apogee, Focusrite, RME, Presonus, and others (but some I did not mention I'd avoid.. especially because of poor driver quality, poor customer support, or poor long term product engineering/driver support). And you are seeing here the result of poor long-term support from Avid/M-Audio for consumer products.

Personally I prefer RME, for their tremendous driver quality and long term support, but you pay significantly more for that.

Have a look around online resellers like Thomann or Sweetwater at the wide range of interfaces that are available, if you have questions or can list the features you are after and your budget folks here can help with suggestions for specific products.

albee1952 12-10-2022 08:49 AM
Re: Problem with M-Audio Fast Track Pro driver
 
Its pinin' for the fjords:p:p


All times are GMT -7. The time now is 03:36 AM.

Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited. Forum Hosted By: URLJet.com