[SOLVED] Error DRIVER_POWER_STATE_FAILURE on shutdown or reboot

[antoniofr]

Hi everyone!

I am having a trouble with my computer. I format disk drive and reinstall Windows 10 pro (2 times), and I am having error DRIVER_POWER_STATE_FAILURE (amdppm.sys) on shutdown or rebooting. Error does not occurs everytime, only sometimes, but always on rebooting or shutting down. Screens turn off but computer remains on, and after some minutes, it reboots or shut down with the error and dump file. I did not change any hardware on my computer, and I didn't receive this error before.

111522-5906-01.dmp 15/11/2022 16:47:21 DRIVER_POWER_STATE_FAILURE 0x0000009f 0000000000000003 ffffa40fb240fb00 fffffc004706f850 ffffa40fbeaebaa0 amdppm.sys amdppm.sys+c165 Processor Device Driver Microsoft® Windows® Operating System Microsoft Corporation 10.0.19041.2251 (WinBuild.160101.0800) x64 ntoskrnl.exe+3f92d0 C:\Windows\Minidump\111522-5906-01.dmp 12 15 19041 1.747.780 15/11/2022 16:47:54

My hardware is:

MSI B450M Mortar Max
AMD Ryzen 5 3600
32 GB RAM Corsair DDR4-3200
MSI GeForce GTX 1650 SUPER
SSD NVMe Samsung 980 PRO 1TB

You can download dump file here: https://drive.google.com/file/d/174ifRAm_eaomUqQmQf6k-p_vhKUzb2IJ/view?usp=share_link

Any help will be appreciated.

Thank you!

 

[rgd1101]

brand and model of the psu?

 

[antoniofr]

Corsair CX650 80 plus bronze 650 watt

 

[Colif]

conversion of dump file

report - click run as fiddle to read


File: 111522-5906-01.dmp (Nov 16 2022 - 02:47:21)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
*** WARNING: Unable to verify timestamp for MAudioFastTrackPro.sys
Probably caused by: memory_corruption (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 27 Min(s), and 52 Sec(s)

Jun 10 2015

MAudioFastTrackPro.sys

M-Audio USB Audio Driver (WDM), Avid Technology, Inc.

update or remove those. Could be a dongle.

 

[antoniofr]

Thank you for confirm this! I suspect about this device (M-Audio Fast Track Pro USB audio interface). I think it could be related to a BIOS update, because before reinstalling Windows, I updated BIOS from E7B89 to last version. With old version I did not had any problem. I think it could be related to USB power when system is off. I thougth it was ok, because I noted all BIOS config before upgrading, but maybe there is some wrong value. I’ll recheck or try downgrade BIOS.
Another option I had in mind is an incompatibility of drivers with last version of Windows (22H2).

I will post when I do some checks.

Thanks!

 

[antoniofr]

I have done some progress. I checked BIOS config and everything is correct. I did a lot of tests today and I have discovered where is the problem, it only occurs after using Cubase 12.0.40. After using that app, sometimes system shutdown is bad, with the error indicated in the first message and respective dump . I tried drivers asio4all, and it seems that problem does not occur with this drivers, but it's not a solution, because genuine drivers are better performance than asio4all. I am trying using Cubase with Fast Track Pro genuine drivers and change them in Cubase config ONLY before closing app, and it seems solved.

Not perfect for me, but I think I could survive that way...

 

[Colif]

Unless the makers release new drivers, you may need to use the asio4all drivers. It must be a change in one of the programs that has caused it.

The last driver being released in 2016 doesn't help

Jan 19. 2016
This is the final driver release for the Fast Track Pro
Qualified with Windows 7, 8, 8.1
Note that Windows 10 (or later) is not compatible and will not be qualified

https://avid.secure.force.com/pkb/articles/en_US/download/Fast-Track-Pro-Drivers

Seems they didn't change their drivers to work with the new driver model on win 10. that shouldn't be a reason though. But they not releasing any new ones either.

I guess this is your driver since previous one is from 2013

Cubase is from this year and Fast track from 2015, since it was what changed here you could ask on their forums - https://forums.steinberg.net/t/cubase-12-0-40-maintenance-update-available/799904

 

[antoniofr]

I am using last driver (6.1.11). I used it for several years in Windows 10 with Cubase 5 and no problems. Seems driver is not fully compatible with Cubase 12.

 

[Colif]

Only thing that has changed in that time is a new version of Cubase 12 as its up to 12.0.40 now. Was updated in August.

I think its them that have changed something. They might have an answer for you.

 

[antoniofr]

All problems happened with Cubase 12.0.40. Yesterday I updated to 12.0.50 (last version right now) and I have not more crashes. I need more time to confirm if this update solves the problem.

 

[Colif]

i did try to find issues for 12.0.40. There are problems with some midi devices.

release notes don't mention fixes - https://www.steinberg.net/cubase/release-notes/12/

 

[antoniofr]

Bad news, crash again, so Cubase 12.0.50 doesn't fix it. I'll try to set asio4all after using Cubase and see what happen.

 

[Colif]

I wonder how you would go trying a previous version, I see there are a few between 5 and 12 - more than meets eye actually
I assume Cubase 8.5 works with 10 since its from December 2015
Cubase 9 is Dec 2016
there has been a new version every year until current one which is 2 years late
https://en.wikipedia.org/wiki/Steinberg_Cubase#Editions

I wonder at what stage they dropped support for that driver.

seems only way to use their forums is using some other account. If you don't want to use asio.sys you probably need to ask them.

 

[antoniofr]

I can confirm that problem is between Cubase 12 and M-Audio Fast Track Pro ASIO drivers. In Cubase, I am using genuine M-Audio drivers and before closing Cubase, I change to asio4all drivers and then to M-Audio ASIO drivers again. That way I have not more crashes. Not a solution but a way to avoid this problem. This drivers aren't going to be updated anymore.

Thanks for your help!

 

[antoniofr]

I am still trying to solve this problem.

I have analyzed with WinDbg Preview dump file:

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

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

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 00000148FA30F5C0  Handle: 1  Id: 1 - Error == 0x8000FFFF

************* 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
........
nt!KeBugCheckEx:
fffff802`5bdf9290 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`61a73820=000000000000009f

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

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 00000148FD2F5CE0  Handle: 1  Id: 1 - Error == 0x8000FFFF

************* 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
........
nt!KeBugCheckEx:
fffff802`5bdf9290 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`61a73820=000000000000009f
||2: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: 4765

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 10319

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

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

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

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

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

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

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

||2:0: kd> dt nt!_TRIAGE_9F_POWER fffff80261a73850
   +0x000 Signature        : 0x8000
   +0x002 Revision         : 2
   +0x008 IrpList          : 0xfffff802`5c623a60 _LIST_ENTRY [ 0xffffc908`0b4f86a0 - 0xffffc908`0f5c8c10 ]
   +0x010 ThreadList       : 0xfffff802`5c620ae0 _LIST_ENTRY [ 0xffff8a83`3fc1bbb8 - 0xffff8a83`42bf5bb8 ]
   +0x018 DelayedWorkQueue : 0xffffc908`02c8ece0 _TRIAGE_EX_WORK_QUEUE
   +0x020 DelayedIoWorkQueue : 0xffffc908`02c70990 _TRIAGE_EX_WORK_QUEUE
||2:0: kd> !irp
Free build - use !irpfind to scan memory for any active IRPs
||2:0: kd> !irp ffffc90811f87aa0
Irp is active with 15 stacks 13 is current (= 0xffffc90811f87ed0)
No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.
     cmd  flg cl Device   File     Completion-Context
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000 

            Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0  0 ffffc908114612d0 00000000 00000000-00000000 
           \Driver\MAUSBFASTTRACKPRO
            Args: 00016600 00000001 00000004 00000006
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffc90810dc9e00 00000000 fffff8025bd79350-ffffc9080f5c8c10 Success Error Cancel pending
           \Driver\ksthunk    nt!PopRequestCompletion
            Args: 00016600 00000001 00000004 00000006
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffc9080f5c8c10 

            Args: 00000000 00000000 00000000 00000000
||2:0: kd> !devstack ffffc9080f74bba0
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffc9080f8e0b30 Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
\FileSystem\aswSnx ffffc9080f8e0c80  InfoMask field not found for _OBJECT_HEADER at ffffc9080f8e0b00

  ffffc90810dc9e00  \Driver\ksthunk    ffffc90810dc9f50  InfoMask field not found for _OBJECT_HEADER at ffffc90810dc9dd0

  ffffc908114612d0  \Driver\MAUSBFASTTRACKPROffffc90811461440  InfoMask field not found for _OBJECT_HEADER at ffffc908114612a0

> ffffc9080f74bba0  \Driver\USBHUB3    ffffc908123daca0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffc90810a5ca20 :
  DeviceInst is "USB\VID_0763&PID_2012\6&1f3785f2&0&2"
  ServiceName is "MAUSBFASTTRACKPRO"
||2:0: kd> !poaction
PopAction: fffff8025c6232e0
  State..........: 3 - Set System State
  Updates........: 0  SHUTDOWN-set
  Action.........: ShutdownOff
  Lightest State.: Shutdown
  Flags..........: c0000004 OverrideApps|DisableWakes|Critical
  Irp minor......: SetPower
  System State...: Shutdown
  Hiber Context..: 0000000000000000

Allocated power irps (PopIrpList - fffff8025c623a60)
  IRP: ffffc908106e3aa0 (set/S5), PDO: ffffc9080f74bba0, CURRENT: ffffc908114612d0, NOTIFY: ffffc90810a5cac0
  IRP: ffffc90811f87aa0 (set/D3,), PDO: ffffc9080f74bba0, CURRENT: ffffc908114612d0

Irp worker threads (PopIrpThreadList - fffff8025c620ae0)
  THREAD: ffffc90802c8e300 (static)
  THREAD: ffffc90802cd5380 (static)
  THREAD: ffffc9080ffd7080 (dynamic)
  THREAD: ffffc90810c09080 (dynamic)
  THREAD: ffffc9080e539340 (dynamic)
  THREAD: ffffc9080fd750c0 (dynamic)
  THREAD: ffffc9080e594080 (dynamic)
  THREAD: ffffc9080e61c380 (dynamic)
  THREAD: ffffc9080e61a080 (dynamic)
  THREAD: ffffc908106d4080 (dynamic)
  THREAD: ffffc9080fa7a080 (dynamic)
  THREAD: ffffc9080fb53080 (dynamic)
  THREAD: ffffc9080e6c1080 (dynamic)
  THREAD: ffffc90802d87080 (dynamic)
  THREAD: ffffc9081021c080 (dynamic), IRP: ffffc90811f87aa0, DEVICE: ffffc9080f8e0b30

Error resolving nt!_POP_CURRENT_BROADCAST...

I see a line:

  ffffc9080f8e0b30 Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2

I think it's from Avast antivirus. Do you think it can cause the problem?



EDITED: Look at this. I suspect Avast antivirus can be involved:

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: 4686

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 11058

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

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

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

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

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

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

0: kd> !devstack ffffc9080f74bba0
  !DevObj           !DrvObj            !DevExt           ObjectName
  ffffc9080f8e0b30 Unable to load image \SystemRoot\system32\drivers\aswSnx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSnx.sys
 \FileSystem\aswSnx ffffc9080f8e0c80  InfoMask field not found for _OBJECT_HEADER at ffffc9080f8e0b00

  ffffc90810dc9e00  \Driver\ksthunk    ffffc90810dc9f50  InfoMask field not found for _OBJECT_HEADER at ffffc90810dc9dd0

  ffffc908114612d0  \Driver\MAUSBFASTTRACKPROffffc90811461440  InfoMask field not found for _OBJECT_HEADER at ffffc908114612a0

> ffffc9080f74bba0  \Driver\USBHUB3    ffffc908123daca0  Cannot read info offset from nt!ObpInfoMaskToOffset

!DevNode ffffc90810a5ca20 :
  DeviceInst is "USB\VID_0763&PID_2012\6&1f3785f2&0&2"
  ServiceName is "MAUSBFASTTRACKPRO"

 

[Colif]

remove avast and see if it fixes it

 

[antoniofr]

remove avast and see if it fixes it

I uninstalled Avast and I got same BSOD, so Avast is not involved...

 

[Colif]

@johnbl can you offer any advice on this?

 

[johnbl]

I would update bios, update the USB3 chipset drivers and update windows.
then go into windows control panel device manager, find the usb3 hub that the device is connected to and right mouse click and tell windows to not let the device sleep. You should also do this for the actual usb audio device.

This is not a fix but would be a work around. There have been a lot of changes to usb sleep functions. A old driver might not have a required function but more likely the BIOS version and usb3 driver versions do not match.


for older machines that have a true usb 2.x chip you can put the device on the usb 2 port rather than the usb 3 port. This might give different results.

dump was no longer available.

NOTE: if you move the device to a usb 2 port, go into windows control panel device manager, find the option to show removed devices and delete the greyed out entries. Windows just hides removed usb devices but the driver can still be running and cause problems until you remove it.

note: older machines BIOS version should match the motherboard USB 3 and usb 2 driver version. if you are running the microsoft generic usb drivers with a non updated BIOS then many of the power management functions might not be in the bios table correctly and cause this type of problem.

 

[antoniofr]

Hello.

BIOS is updated to last version (MSI B450M Mortar Max BIOS 7B89v2H). I also tried to connect USB audio interface to USB 2.0 port, but I have the same problem, BSOD on shutdown. Device USB sleep is disabled always.

I am going to try what you say about installing chipset drivers and removing driver and connecting to USB port.

Sorry, I removed old dump file. New dump file: https://drive.google.com/file/d/1xW6mqa21tOq37DDH17JmLCPjno_dMHIt/view?usp=share_link

Thanks!


EDITED: I tried actions commented, but nothing works.

 

[antoniofr]

@johnbl Maybe a solution could be disable C-states in my BIOS? Actually it is configured as auto.

 

[johnbl]

@johnbl Maybe a solution could be disable C-states in my BIOS? Actually it is configured as auto.

in the dump it just looks like you audio device is connected to a usb 3 hub
the system is waiting for the audio device to respond to a request but it is most likely does not even see the request since the usb 3 hub it is attached to is waiting for a wake up signal.

I would expect that if you go into device manager, right click on the usb3 hub to bring up properties then find the power management tab and tell windows not to let the device sleep. Should work around the problem.

you could also disable the sleep states in bios but then nothing would sleep on your machine.
notes:
looks like microsoft generic usb3 driver, microsoft usb host controller service installed.
VBoxUSBMon.sys Tue Oct 11 06:43:48 2022

if you change the dump type to kernel then I could also look at the usb logs and see the actual connections being used for the USB
if you provide a kernel dump. (memory.dmp file)
BIOS Version 2.H0
BIOS Starting Address Segment f000
BIOS Release Date 07/27/2022

Processor Version AMD Ryzen 5 3600 6-Core Processor
Processor Voltage 8bh - 1.1V
External Clock 100MHz
Max Speed 4200MHz
Current Speed 3600MHz

Manufacturer Micro-Star International Co., Ltd.
Product Name MS-7B89
Socket Designation AM4
Processor Type Central Processor
Processor Family 6bh - AMD Zen Processor Family
Processor Manufacturer Advanced Micro Devices, Inc.
Product B450M MORTAR MAX (MS-7B89)

you might need to pick up the chipset drivers:
B450 MORTAR MAX | Motherboard | MSI Global

some of the usb are supported by the chipset drivers some are directly supported by the cpu.

(looks like these are supported by the chipset drivers)
AMD® B450 Chipset y 1x USB 3.2 Gen2 (SuperSpeed USB 10Gbps) Type-C port on the back panel y 1x USB 3.2 Gen2 (SuperSpeed USB 10Gbps) Type-A port on the back panel y 2x USB 3.2 Gen1 (SuperSpeed USB) ports available through the internal USB 3.2 Gen1 connector y 6x USB 2.0 (High-speed USB) ports (2 Type-A ports on the back panel, 4 ports available through the internal USB 2.0 connectors)

(looks like these are supported by the cpu)
AMD® CPU y 4x USB 3.2 Gen1 (SuperSpeed USB) Type-A ports on the back pane

in general USB supported directly by the cpu are the most likely to work correctly.

 

[antoniofr]

in the dump it just looks like you audio device is connected to a usb 3 hub
the system is waiting for the audio device to respond to a request but it is most likely does not even see the request since the usb 3 hub it is attached to is waiting for a wake up signal.

I would expect that if you go into device manager, right click on the usb3 hub to bring up properties then find the power management tab and tell windows not to let the device sleep. Should work around the problem.

you could also disable the sleep states in bios but then nothing would sleep on your machine.
notes:
looks like microsoft generic usb3 driver, microsoft usb host controller service installed.
VBoxUSBMon.sys Tue Oct 11 06:43:48 2022

if you change the dump type to kernel then I could also look at the usb logs and see the actual connections being used for the USB
if you provide a kernel dump. (memory.dmp file)
BIOS Version 2.H0
BIOS Starting Address Segment f000
BIOS Release Date 07/27/2022

Processor Version AMD Ryzen 5 3600 6-Core Processor
Processor Voltage 8bh - 1.1V
External Clock 100MHz
Max Speed 4200MHz
Current Speed 3600MHz

Manufacturer Micro-Star International Co., Ltd.
Product Name MS-7B89
Socket Designation AM4
Processor Type Central Processor
Processor Family 6bh - AMD Zen Processor Family
Processor Manufacturer Advanced Micro Devices, Inc.
Product B450M MORTAR MAX (MS-7B89)

you might need to pick up the chipset drivers:
B450 MORTAR MAX | Motherboard | MSI Global

some of the usb are supported by the chipset drivers some are directly supported by the cpu.

(looks like these are supported by the chipset drivers)
AMD® B450 Chipset y 1x USB 3.2 Gen2 (SuperSpeed USB 10Gbps) Type-C port on the back panel y 1x USB 3.2 Gen2 (SuperSpeed USB 10Gbps) Type-A port on the back panel y 2x USB 3.2 Gen1 (SuperSpeed USB) ports available through the internal USB 3.2 Gen1 connector y 6x USB 2.0 (High-speed USB) ports (2 Type-A ports on the back panel, 4 ports available through the internal USB 2.0 connectors)

(looks like these are supported by the cpu)
AMD® CPU y 4x USB 3.2 Gen1 (SuperSpeed USB) Type-A ports on the back pane

in general USB supported directly by the cpu are the most likely to work correctly.

I tried disabling C-states in BIOS, but it doesn't work. I think the big problem here is driver. I tried everything, and there is no way... So finally I buy another USB audio interface (Focusrite Scarlett 2i2) and now evething is OK.

Thanks for your help.

 

[Colif]

Some times buying a new piece of hardware is only answer.