Question DRIVER_POWER_STATE_FAILURE (9f) - BSOD on Win 10

[Iddo Genuth]

Hi All,
So I am having a super annoying problem with my desktop win 10 system (for quite a long time on and off - I'd say every 2 out of every 3 resets it happens within 3-10 min if not I am usually fine until the next reset - very strange).

The BSOD is DRIVER_POWER_STATE_FAILURE.

Computer:
Win 10 Home 64 bit (19044.2075)
Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz 3.30 GHz
Asus X99 Sabertooth MB
32GB ram
Nvidia 1080TI latest studio drivers (517.40), recent clean install

Here is the recent minidump info I am getting - it seems to me to have something to do with the missing ACPI driver - but what is this exactly and where do I get this? suggestions?

Thanks
Iddo

Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\092522-20687-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are 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 Personal
Machine Name:
Kernel base = 0xfffff80708800000 PsLoadedModuleList = 0xfffff8070942a290
Debug session time: Sun Sep 25 00:38:37.150 2022 (UTC + 3:00)
System Uptime: 0 days 0:09:06.788
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
......................................
Loading User Symbols
Loading unloaded module list
.....................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff80708bf8fa0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8284b5a29820=000000000000009f

Loading Dump File [C:\WINDOWS\Minidump\092522-20593-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Can't set dump file contexts
MachineInfo::SetContext failed - Thread: 000002D496E1DE60 Handle: 2 Id: 2 - 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 Personal
Machine Name:
Kernel base = 0xfffff80363e00000 PsLoadedModuleList = 0xfffff80364a2a270
Debug session time: Sun Sep 25 01:11:54.027 2022 (UTC + 3:00)
System Uptime: 0 days 0:04:28.666
Loading Kernel Symbols
...............................................................
................................................................
................................................................
........................................
Loading User Symbols
Loading unloaded module list
.....................
nt!KeBugCheckEx:
fffff803641f90e0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd489f926f820=000000000000009f
||1:6: 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: ffffc4840a94c7b0, Physical Device Object of the stack
Arg3: ffffd489f926f850, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffc48417f32a20, The blocked IRP

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2593

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 24170

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x9f

Key : Bugcheck.Code.Register
Value: 0x9f

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: 092522-20593-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 9f

BUGCHECK_P1: 3

BUGCHECK_P2: ffffc4840a94c7b0

BUGCHECK_P3: ffffd489f926f850

BUGCHECK_P4: ffffc48417f32a20

DRVPOWERSTATE_SUBCODE: 3

DRIVER_OBJECT: ffffc4840834a6f0

IMAGE_NAME: ACPI.sys

MODULE_NAME: ACPI

FAULTING_MODULE: fffff80368f20000 ACPI

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffd489f926f818 fffff803643603f7 : 000000000000009f 0000000000000003 ffffc4840a94c7b0 ffffd489f926f850 : nt!KeBugCheckEx
ffffd489f926f820 fffff80364360311 : ffffc48416cf9260 0000000000000000 ffffc4841dd281f0 0000000000000000 : nt!PopIrpWatchdogBugcheck+0xdf
ffffd489f926f890 fffff8036401ca72 : ffffc48416cf9298 ffffb08078440180 ffffb08078440180 0000000000000002 : nt!PopIrpWatchdog+0x31
ffffd489f926f8e0 fffff80364033f6d : fffff7c580001158 0000000000000008 0000000000140001 0000000000002820 : nt!KiProcessExpiredTimerList+0x172
ffffd489f926f9d0 fffff803641fcc7e : ffffffff00000000 ffffb08078440180 ffffb0807844b340 ffffc48417e19080 : nt!KiRetireDpcList+0x5dd
ffffd489f926fc60 0000000000000000 : ffffd489f9270000 ffffd489f926a000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e


IMAGE_VERSION: 10.0.19041.2060

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x9F_3_aswSnx_DEV_PNP0501_IMAGE_ACPI.sys

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {f2046b84-2e2e-84c8-b14b-f10127d0e155}

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

||1:6: kd> !drvobj ffffc4840834a6f0 f
fffff80364a250a8: Unable to get value of ObpRootDirectoryObject
fffff80364a250a8: Unable to get value of ObpRootDirectoryObject
Driver object (ffffc4840834a6f0) is for:
\Driver\ACPI

Driver Extension List: (id , addr)

Device Object list:
ffffc48416d3be00: Could not read device object


DriverEntry: fffff80368fdb010 ACPI!GsDriverEntry
DriverStartIo: 00000000
DriverUnload: fffff80368f72d10 ACPI!ACPIUnload
AddDevice: 00000000

Dispatch routines:
[00] IRP_MJ_CREATE fffff80368f21010 ACPI!ACPIDispatchIrp
[01] IRP_MJ_CREATE_NAMED_PIPE fffff80368f21010 ACPI!ACPIDispatchIrp
[02] IRP_MJ_CLOSE fffff80368f21010 ACPI!ACPIDispatchIrp
[03] IRP_MJ_READ fffff80368f21010 ACPI!ACPIDispatchIrp
[04] IRP_MJ_WRITE fffff80368f21010 ACPI!ACPIDispatchIrp
[05] IRP_MJ_QUERY_INFORMATION fffff80368f21010 ACPI!ACPIDispatchIrp
[06] IRP_MJ_SET_INFORMATION fffff80368f21010 ACPI!ACPIDispatchIrp
[07] IRP_MJ_QUERY_EA fffff80368f21010 ACPI!ACPIDispatchIrp
[08] IRP_MJ_SET_EA fffff80368f21010 ACPI!ACPIDispatchIrp
[09] IRP_MJ_FLUSH_BUFFERS fffff80368f21010 ACPI!ACPIDispatchIrp
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff80368f21010 ACPI!ACPIDispatchIrp
[0b] IRP_MJ_SET_VOLUME_INFORMATION fffff80368f21010 ACPI!ACPIDispatchIrp
[0c] IRP_MJ_DIRECTORY_CONTROL fffff80368f21010 ACPI!ACPIDispatchIrp
[0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff80368f21010 ACPI!ACPIDispatchIrp
[0e] IRP_MJ_DEVICE_CONTROL fffff80368f21010 ACPI!ACPIDispatchIrp
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff80368f21010 ACPI!ACPIDispatchIrp
[10] IRP_MJ_SHUTDOWN fffff80368f21010 ACPI!ACPIDispatchIrp
[11] IRP_MJ_LOCK_CONTROL fffff80368f21010 ACPI!ACPIDispatchIrp
[12] IRP_MJ_CLEANUP fffff80368f21010 ACPI!ACPIDispatchIrp
[13] IRP_MJ_CREATE_MAILSLOT fffff80368f21010 ACPI!ACPIDispatchIrp
[14] IRP_MJ_QUERY_SECURITY fffff80368f21010 ACPI!ACPIDispatchIrp
[15] IRP_MJ_SET_SECURITY fffff80368f21010 ACPI!ACPIDispatchIrp
[16] IRP_MJ_POWER fffff80368f21010 ACPI!ACPIDispatchIrp
[17] IRP_MJ_SYSTEM_CONTROL fffff80368f21010 ACPI!ACPIDispatchIrp
[18] IRP_MJ_DEVICE_CHANGE fffff80368f21010 ACPI!ACPIDispatchIrp
[19] IRP_MJ_QUERY_QUOTA fffff80368f21010 ACPI!ACPIDispatchIrp
[1a] IRP_MJ_SET_QUOTA fffff80368f21010 ACPI!ACPIDispatchIrp
[1b] IRP_MJ_PNP fffff80368f21010 ACPI!ACPIDispatchIrp

Fast I/O routines:
Cannot read _FAST_IO_DISPATCH at fffff80368fa2520
||1:6: kd> !drvobj \Driver\ACPI
fffff80364a250a8: Unable to get value of ObpRootDirectoryObject
Driver object \Driver\ACPI not found

 

[Colif]

Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD

1. Open Windows File Explore
2. Navigate to C:\Windows\Minidump
3. Copy the mini-dump files out onto your Desktop
4. Do not use Winzip, use the built in facility in Windows
5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
7. Then post a link here to the zip file, so we can take a look for you . . .

it might be internet drivers

 

[Iddo Genuth]

Hi Colif,
The above is the dmp file.
I am linking to all of them if you need more:
https://www.dropbox.com/sh/7tq8y7fh4m20dw7/AADFYRdgSjhMmqPOtVpjwaE2a?dl=0

What do you mean by internet drivers? (I didn't know there is such a thing - do you mean Lan card drivers? I have both 2 oneboard cards and I am actually using a QNAP 10GBE card)
Iddo

 

[Colif]

Sorry I am slow to reply, weather isn't being nice to me.
Yes, I meant Ethernet, lets see if dumps agreed. Shame debugger freezes up with more than 5 dumps

Conversion of dumps

report - Click run as fiddle to see report

Spoiler

File: 092522-20906-01.dmp (Sep 25 2022 - 05:39:13)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
*** WARNING: Unable to verify timestamp for aswArPot.sys
Probably caused by: ACPI.sys (Process: AvastSvc.exe)
Uptime: 0 Day(s), 0 Hour(s), 09 Min(s), and 16 Sec(s)

File: 092522-20781-01.dmp (Sep 25 2022 - 07:23:59)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: ACPI.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 13 Min(s), and 26 Sec(s)

File: 092522-20687-01.dmp (Sep 25 2022 - 07:38:37)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: ACPI.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 09 Min(s), and 06 Sec(s)

File: 092522-20593-01.dmp (Sep 25 2022 - 08:11:54)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: ACPI.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 28 Sec(s)

File: 092422-21343-01.dmp (Sep 25 2022 - 05:06:19)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: ACPI.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 03 Min(s), and 48 Sec(s)

File: 092422-20750-01.dmp (Sep 25 2022 - 05:22:19)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: ACPI.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 57 Sec(s)

File: 091622-20500-01.dmp (Sep 16 2022 - 20:53:26)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: ACPI.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 04 Min(s), and 18 Sec(s)

File: 091622-16078-01.dmp (Sep 17 2022 - 01:46:24)
BugCheck: [DRIVER_POWER_STATE_FAILURE (9F)]
Probably caused by: ACPI.sys (Process: System)
Uptime: 0 Day(s), 0 Hour(s), 08 Min(s), and 44 Sec(s)

the last one to occur blames Avast

Aug 19 2022

aswArPot.sys

Avast Antivirus http://www.avast.com/

I believe they all caused by Avast
all of them include
FAILURE_BUCKET_ID: 0x9F_3_aswSnx_DEV_PNP0501_IMAGE_ACPI.sys

Aug 19 2022

aswSnx.sys

Avast Antivirus http://www.avast.com/

try uninstalling it and see if you still BSOD.

 

[Iddo Genuth]

Hi Colif,
Thanks for getting back to me.
M... that is a surprise. Didn't expect this - I had AVAST on this computer and many others for years without a problem - of course, something might have broken somehow over time. I don't like having my computer without protection though - do you suggest uninstalling testing and re-installing or some other antivirus software?

P.S. I updated the Ethernet card bios and drivers anyway - not sure if it did something.

 

[ubuysa]

The DRIVER_POWER_STATE_FAILURE BSODs occur because an Interrupt Request Packet (IRP) is being held for too long. The address of the IRP is given in argument 4 and displaying this IRP gives...

2: kd> !irp ffffa30be35caa60
Irp is active with 9 stacks 6 is current (= 0xffffa30be35cac98)
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
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffa30bcc8d27b0 00000000 fffff80191b25920-00000000 Success Error Cancel pending
           \Driver\ACPI    serial!SerialSetPowerD0Completion
            Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e0 ffffa30bd2a34070 00000000 fffff80191b41d20-00000000 Success Error Cancel
           \Driver\Serial    serenum!Serenum_FDOPowerComplete
            Args: 00000000 00000001 00000001 00000000
[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffa30bd2da85a0 00000000 fffff8017d1791f0-ffffa30be22641b0 Success Error Cancel pending
           \Driver\Serenum    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
[N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffa30be22641b0   

            Args: 00000000 00000000 00000000 00000000

This indicates that there was some sort of ACPI power state change issue with what looks like a serial attached device (though that doesn't mean it's physically attached to a serial port).

I can see two drivers that you have installed that are known to cause BSODs. These are AiChargerPlus.sys (the Asus Charger Driver) and IOMap64.sys (a component of the Asus Smart Doctor tool) - this one is known to cause BSOD when waking from sleep. I would recommend that you completely uninstall the Asus AiCharger Plus tool and the Asus Smart Doctor tool and see whether that stops these BSODs.

 

[Iddo Genuth]

Many thanks! - I will do that now and report although I don't restart the computer every day so the results might take a little time (I try not to since it is so unstable after restarts that it can take several tries until I get a working computer again that doesn't BSOD...).

 

[ubuysa]

Many thanks! - I will do that now and report although I don't restart the computer every day so the results might take a little time (I try not to since it is so unstable after restarts that it can take several tries until I get a working computer again that doesn't BSOD...).

If it continues to BSOD after uninstalling the two Asus tools, please zip up all new minidumps and upload the zip file to here.