Question about driver power state failure and BSOD issue.
Question about driver power state failure and BSOD issue.
So I have been getting BSOD since the begining of my build in early January. I have slowly eliminated issues (first ram stability, then graphics and now this). Regardless if my ram is running ddr5 4800 or Expo 6000 I keep getting a BSOD with a DRIVER_POWER_STATE_FAILURE (9f). I am running a 7950X on a X670E Taichi 7 HDDs in various drive pools and 64GB of DDR5 6000 G.Skill Trident Z5 Neo RGB. Also running 4 Nvme drives Nextorage 2TB as my OS drive, 4TB WD 850X, 2 TB Silicon power and Sabrent Rocket 2TB. I've installed the latest chipset drivers and every other for that matter. I have tried disabling C states, not allowing the HDDs to sleep in windows power plan and probably a few other things I am forgeting. Below is my error log/bug check analysis. Am I wrong it stating the faulting drive is the Nexstorage C: drive? Any help or ideas how to fix would be appreciated?
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (32 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff805`7ac00000 PsLoadedModuleList = 0xfffff805`7b813470
Debug session time: Fri Jun 2 13:00:26.640 2023 (UTC - 7:00)
System Uptime: 0 days 3:07:52.219
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..........................................
Loading User Symbols
Loading unloaded module list
.............................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`7b02b8f0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff805`7700ab40=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: ffffce8b3ea77050, Physical Device Object of the stack
Arg3: fffff8057700ab88, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffce8b4aea89e0, The blocked IRP
Debugging Details:
------------------
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1093
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 1042
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: 280
Key : Analysis.Init.Elapsed.mSec
Value: 3987
Key : Analysis.Memory.CommitPeak.Mb
Value: 97
Key : Bugcheck.Code.DumpHeader
Value: 0x9f
Key : Bugcheck.Code.Register
Value: 0x9f
Key : Dump.Attributes.AsUlong
Value: 1008
Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1
Key : Dump.Attributes.ErrorCode
Value: 0
Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1
Key : Dump.Attributes.LastLine
Value: Dump completed successfully.
Key : Dump.Attributes.ProgressPercentage
Value: 0
FILE_IN_CAB: 060223-18578-01.dmp
DUMP_FILE_ATTRIBUTES: 0x1008
Kernel Generated Triage Dump
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffffce8b3ea77050
BUGCHECK_P3: fffff8057700ab88
BUGCHECK_P4: ffffce8b4aea89e0
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffffce8b3e9ebd80
IMAGE_NAME: storahci.sys
MODULE_NAME: storahci
FAULTING_MODULE: fffff8057d080000 storahci
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: NortonSecurity
DPC_STACK_BASE: FFFFF8057700AFB0
STACK_TEXT:
fffff805`7700ab38 fffff805`7b173066 : 00000000`0000009f 00000000`00000003 ffffce8b`3ea77050 fffff805`7700ab88 : nt!KeBugCheckEx
fffff805`7700ab40 fffff805`7b172f3c : 00000000`00000002 fffff805`7567e180 fffff805`7567e180 fffff805`75685800 : nt!PopIrpWatchdogBugcheck+0x122
fffff805`7700abc0 fffff805`7ae2815b : ffffce8b`4aeb3240 ffffce8b`00000001 fffff805`7700ae68 00000000`00000002 : nt!PopIrpWatchdog+0xc
fffff805`7700abf0 fffff805`7ae298d6 : 00000000`00000022 ffffce8b`627950c0 fffff805`7700ae20 00000000`00068fb1 : nt!KiProcessExpiredTimerList+0x1eb
fffff805`7700ad20 fffff805`7b034d65 : 00000000`00000000 00000000`00000000 ffffce8b`6666d080 0000018e`cb7cd990 : nt!KiRetireDpcList+0xed6
fffff805`7700afb0 fffff805`7b034d0f : ffffb90a`ef0173c9 fffff805`7ae2c0c9 ffffce8b`65c4c700 00000000`00000000 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffb90a`ef017330 fffff805`7ae2c0c9 : ffffce8b`65c4c700 00000000`00000000 00000000`00000000 00007ff8`fabd4160 : nt!KiPlatformSwapStacksAndCallReturn
ffffb90a`ef017340 fffff805`7b0344db : 00000000`00000040 0000018e`d1b58c40 00000000`00000088 0000018e`d3f298d0 : nt!KiDispatchInterrupt+0xd9
ffffb90a`ef017430 fffff805`7b02e331 : 0000018e`cb7cd990 0000018e`00000000 00000000`00400060 00000000`00000000 : nt!KiDpcInterruptBypass+0x1b
ffffb90a`ef017460 00007ff8`fab6bbfe : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0xb1
00000021`0e9bd3a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`fab6bbfe
IMAGE_VERSION: 10.0.22621.1690
STACK_COMMAND: .cxr; .ecxr ; kb
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_storahci.sys
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {21defffd-4d1f-b62d-8f72-d4892aa9cff8}
Followup: MachineOwner
---------
0: kd> !drvobj ffffce8b3e9ebd80 f
fffff8057b840030: Unable to get value of ObpRootDirectoryObject
fffff8057b840030: Unable to get value of ObpRootDirectoryObject
Driver object (ffffce8b3e9ebd80) is for:
\Driver\storahci
Driver Extension List: (id , addr)
Device Object list:
ffffce8b3eadf050: Could not read device object
DriverEntry: fffff8057d0ae010 storahci!GsDriverEntry
DriverStartIo: 00000000
DriverUnload: fffff8057d0fec30 storport!RaDriverUnload
AddDevice: 00000000
Dispatch routines:
[00] IRP_MJ_CREATE fffff8057d15ff80 storport!RaDriverCreateIrp
[01] IRP_MJ_CREATE_NAMED_PIPE fffff8057af71b00 nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE fffff8057d15fee0 storport!RaDriverCloseIrp
[03] IRP_MJ_READ fffff8057af71b00 nt!IopInvalidDeviceRequest
[04] IRP_MJ_WRITE fffff8057af71b00 nt!IopInvalidDeviceRequest
[05] IRP_MJ_QUERY_INFORMATION fffff8057af71b00 nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION fffff8057af71b00 nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA fffff8057af71b00 nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA fffff8057af71b00 nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS fffff8057af71b00 nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION fffff8057af71b00 nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION fffff8057af71b00 nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL fffff8057af71b00 nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL fffff8057af71b00 nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL fffff8057d0ce500 storport!SrbShimHookDeviceControl
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL fffff8057d0c4170 storport!RaDriverScsiIrp
[10] IRP_MJ_SHUTDOWN fffff8057af71b00 nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL fffff8057af71b00 nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP fffff8057af71b00 nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT fffff8057af71b00 nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY fffff8057af71b00 nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY fffff8057af71b00 nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER fffff8057d0d0230 storport!RaDriverPowerIrp
[17] IRP_MJ_SYSTEM_CONTROL fffff8057d162790 storport!RaDriverSystemControlIrp
[18] IRP_MJ_DEVICE_CHANGE fffff8057af71b00 nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA fffff8057af71b00 nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA fffff8057af71b00 nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP fffff8057d0c6990 storport!RaDriverPnpIrp
Device Object stacks:
ffffce8b3eadf050: Could not read device object
Error processing device objects. Processed 0 device objects before error.
0: kd> lmvm storahci
Browse full module list
start end module name
fffff805`7d080000 fffff805`7d0b2000 storahci # (pdb symbols) C:\ProgramData\Dbg\sym\storahci.pdb\C1C58BAFD3E29FF64813435F84CDA4671\storahci.pdb
Loaded symbol image file: storahci.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\storahci.sys\3A43E6AD32000\storahci.sys
Image path: storahci.sys
Image name: storahci.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 3A43E6AD (This is a reproducible build file hash, not a timestamp)
CheckSum: 0003853A
ImageSize: 00032000
File version: 10.0.22621.1690
Product version: 10.0.22621.1690
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: storahci.sys
OriginalFilename: storahci.sys
ProductVersion: 10.0.22621.1690
FileVersion: 10.0.22621.1690 (WinBuild.160101.0800)
FileDescription: MS AHCI Storport Miniport Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> lmvm storahci
Browse full module list
start end module name
fffff805`7d080000 fffff805`7d0b2000 storahci # (pdb symbols) C:\ProgramData\Dbg\sym\storahci.pdb\C1C58BAFD3E29FF64813435F84CDA4671\storahci.pdb
Loaded symbol image file: storahci.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\storahci.sys\3A43E6AD32000\storahci.sys
Image path: storahci.sys
Image name: storahci.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 3A43E6AD (This is a reproducible build file hash, not a timestamp)
CheckSum: 0003853A
ImageSize: 00032000
File version: 10.0.22621.1690
Product version: 10.0.22621.1690
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: storahci.sys
OriginalFilename: storahci.sys
ProductVersion: 10.0.22621.1690
FileVersion: 10.0.22621.1690 (WinBuild.160101.0800)
FileDescription: MS AHCI Storport Miniport Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> !blackboxbsd
Version: 0xc0
Product type: 1
Auto advanced boot: FALSE
Advanced boot menu timeout: 30
Last boot succeeded: TRUE
Last boot shutdown: FALSE
Sleep in progress: FALSE
Power button timestamp: 0x0
System running: TRUE
Connected standby in progress: FALSE
User shutdown in progress: FALSE
System shutdown in progress: FALSE
Sleep in progress: 0
Connected standby scenario instance id: 0
Connected standby entry reason: 0
Connected standby exit reason: 0
System sleep transitions to on: 0
Last reference time: 0x1d99572aa5c4864
2023-06-02T16:52:50.112Z
Last reference time checksum: 0x1aaf5941
Last update boot id: 313
Boot attempt count: 1
Last boot checkpoint: TRUE
Checksum: 0x7d
Last boot id: 313
Last successful shutdown boot id: 312
Last reported abnormal shutdown boot id: 312
Error info boot id: 0
Error info repeat count: 0
Error info other error count: 0
Error info code: 0
Error info status: 0x0
Power button last press time: 0x0
Power button cumulative press count: 0
Power button last press boot id: 0
Power button last power watchdog stage: 0
Power button watchdog armed: FALSE
Power button shutdown in progress: FALSE
Power button last release time: 0x0
Power button cumulative release count: 0
Power button last release boot id: 0
Power button error count: 0
Power button current connected standby phase: 0
Power button transition latest checkpoint id: 0
Power button transition latest checkpoint type: 0
Power button transition latest checkpoint sequence number: 0
Power transition Shutdown Device Type: 0
Power transition Setup In Progress: FALSE
Power transition OOBE In Progress: FALSE
Power transition Sleep Checkpoint Source: 0
Power transition Sleep Checkpoint: 0
Power transition Connected Standby Entry Reason Category: 0
Power transition Connected Standby Exit Reason Category: 0
Power transition Connected Standby Entry Scenario Instance Id: 0x0
Feature Configuration State : Committed
0: kd> !blackboxntfs
NTFS Blackbox Data
Record 0:
Record type: 1 (Slow I/O Timeout)
Record length: 32
Irp: ffffce8b757da010
Scb: ffffce8b51997970
Thread: ffffce8b711e7080
1 Slow I/O Timeout Records Found
0 Oplock Break Timeout Records Found
0: kd> !blackboxntfs
NTFS Blackbox Data
Record 0:
Record type: 1 (Slow I/O Timeout)
Record length: 32
Irp: ffffce8b757da010
Scb: ffffce8b51997970
Thread: ffffce8b711e7080
1 Slow I/O Timeout Records Found
0 Oplock Break Timeout Records Found
0: kd> !blackboxpnp
PnpActivityId : {00000000-0000-0000-0000-000000000000}
PnpActivityTime : 133302062375839747
PnpEventInformation: 3
PnpEventInProgress : 0
PnpProblemCode : 24
PnpVetoType : 0
DeviceId : USB\VID_045E&PID_0B12\3032373130313337313437323336
VetoString :
I understand the issue, but I require the dump file to proceed. Analyzing memory dumps involves more than just running -v...
The DRIVER_POWER_STATE_FAILURE (9f) BSOD signifies that a driver failed to finish a power IRP within a defined period. According to the log, the storahci.sys driver appears to be involved. Here are some recommendations to assist in diagnosing and fixing the issue:
Update Drivers: Confirm you have the most recent drivers for all hardware, particularly those related to storage. Check the manufacturer's site for each device and download compatible updates.
Check Firmware Updates: Make sure your SSDs and other storage devices are running the latest firmware versions, as these often contain fixes and performance enhancements.
Disable Power Management for Storage Devices: In Device Manager, select "Disk drives," right-click each storage device, and choose the "Power Management" tab. Turn off the power-saving option to prevent the computer from shutting down the device.
Disable Fast Startup: Fast Startup may interfere with driver compatibility. Adjust settings in Control Panel > Power Options > Choose what the power buttons do by unchecking "Turn on fast startup."
Inspect System File Corruption: Use the System File Checker (SFC) tool to detect and repair corrupted files. Run it from an administrator's Command Prompt: sfc /scannow
Update BIOS: Look for available BIOS updates for your motherboard and follow the manufacturer's guidance to apply them, as this can address compatibility problems.
Remove and Reinstall Problematic Drivers: If the problem continues, uninstall the storahci.sys driver and reinstall it. In Device Manager, expand "Storage controllers," right-click the driver, and select "Uninstall device." Restart your system, and Windows will reinstall the driver automatically.
Next Time Please Upload A Dump Because It's A Nuisance To Read.
I had already attempted those before turning off cstates since they are clearly the main culprits. I noticed this issue appears on Taichi boards too, not just there. I plan to reinstall the driver again because I understand that fixing it three times won’t always work. I adjusted my settings for a full system memory dump during the previous crash, which should give you more material to investigate. Appreciate your response.
Here is the rewritten version:
You're looking for a specific format. I tend to find analysis most helpful for me. My system is configured to perform a complete memory dump upon any crash, not just the 256-bit one currently available. I have additional versions of the dump ready. If you have a particular viewer or tool you'd prefer me to use, please let me know and I'll be glad to follow your instructions. Thank you for your patience.
I apologize for the delayed response; it seems I didn't receive notifications as expected. I will try checking the data directly in the future rather than depending on alerts.
Analysing a memory dump is WAY more intensive and complex than just using analyze -v. You can't debug this 0x9F bugcheck with analyze -v for example. Just upload the relevant dumps (the .dmp files) in C:\Windows\Minidump.
DO NOT write a complete memory dump!!
It will be huge and nobody (certainly not me) is going to download it. In Windows 10/11 you should set the dump type to 'Automatic memory dump'. Most problems can be analysed via the minidumps however, which you'll find in the folder above.
I believe I discovered a solution since I haven't crashed in several days now. It's unclear whether it was one fix or a combination of both, but I turned on HIPM in power management and looked for an Asmedia SATA driver that wasn't listed on the Asrocks page or obviously from AMD. I reached out to someone for credit, but I can't find them... I did a lot of searches, checking forums and similar sites.
Hi, I'm dealing with the exact same issue as you are, running a x670e Taichi Mobo with AMD Ryzen 7950x. I'm interested in your solution. On another forum at computerbase, someone shared a long thread suggesting it might be due to old hard disks, but I think it could be related to a driver or hardware problem. I'd appreciate confirmation if it's a driver issue so I don't have to return my combo. This is really frustrating, especially since the disks I'm using worked perfectly on my old Intel system. Could you help me identify what changes were made (HIPM and where)? Thanks in advance.
Add AHCI Link Power Management to Power Options in Windows
Instructions for including or excluding 'AHCI Link Power Management - HIPM/DIPM' in Windows Power Options
www.tenforums.com
Driver
Asmedia ASM-106x Sata 6G controller Drivers Version 3.2.3.0 WHQL
Windows
www.station-drivers.com
Performed both actions to ensure functionality; please verify the 'Hipm' setting under Hard Disk power management.