Question DRIVER_POWER_STATE_FAILURE (9f) BSOD ?

[atomicWAR]

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 :

 

[ubuysa]

I can tell you what the problem is here but you need to upload the dump for me to do so. There is way more to memory dump analysis than just analyze -v....

 

[Stanisław]

The DRIVER_POWER_STATE_FAILURE (9f) BSOD error indicates that a driver has failed to complete a power IRP (Input/Output Request Packet) within a specific time. Based on the error log you provided, it seems that the storahci.sys driver is causing the issue.

Here are a few suggestions to help troubleshoot and resolve the problem:

1. Update Drivers: Ensure that you have the latest drivers installed for all your hardware components, especially the storage-related drivers. Visit the manufacturer's website for each device and download the latest drivers compatible with your operating system.
2. Check for Firmware Updates: Update the firmware of your SSDs and other storage devices to the latest version. Firmware updates often include bug fixes and performance improvements.
3. Disable Power Management for Storage Devices: Open Device Manager, expand the "Disk drives" category, right-click on each storage device, and go to the "Power Management" tab. Uncheck the option that allows the computer to turn off the device to save power.
4. Disable Fast Startup: Sometimes, Fast Startup can cause compatibility issues with certain drivers. Disable Fast Startup by going to Control Panel > Power Options > Choose what the power buttons do, and uncheck the "Turn on fast startup" option.
5. Check for System File Corruption: Run the System File Checker (SFC) utility to scan for and repair any corrupted system files. Open Command Prompt as an administrator and run the command: sfc /scannow
6. Update BIOS: Check if there is a BIOS update available for your motherboard. Visit the manufacturer's website and follow their instructions to update the BIOS. A BIOS update can sometimes resolve compatibility issues and improve system stability.
7. Remove and Reinstall Problematic Drivers: If the issue persists, try uninstalling the storahci.sys driver and reinstalling it. Open Device Manager, expand the "Storage controllers" category, right-click on the driver, and select "Uninstall device." Then restart your computer, and Windows will automatically reinstall the driver.

Next Time Please Upload A Dump Because It's A Nuisance To Read.

 

[atomicWAR]

The DRIVER_POWER_STATE_FAILURE (9f) BSOD error indicates that a driver has failed to complete a power IRP (Input/Output Request Packet) within a specific time. Based on the error log you provided, it seems that the storahci.sys driver is causing the issue.

Here are a few suggestions to help troubleshoot and resolve the problem:

1. Update Drivers: Ensure that you have the latest drivers installed for all your hardware components, especially the storage-related drivers. Visit the manufacturer's website for each device and download the latest drivers compatible with your operating system.
2. Check for Firmware Updates: Update the firmware of your SSDs and other storage devices to the latest version. Firmware updates often include bug fixes and performance improvements.
3. Disable Power Management for Storage Devices: Open Device Manager, expand the "Disk drives" category, right-click on each storage device, and go to the "Power Management" tab. Uncheck the option that allows the computer to turn off the device to save power.
4. Disable Fast Startup: Sometimes, Fast Startup can cause compatibility issues with certain drivers. Disable Fast Startup by going to Control Panel > Power Options > Choose what the power buttons do, and uncheck the "Turn on fast startup" option.
5. Check for System File Corruption: Run the System File Checker (SFC) utility to scan for and repair any corrupted system files. Open Command Prompt as an administrator and run the command: sfc /scannow
6. Update BIOS: Check if there is a BIOS update available for your motherboard. Visit the manufacturer's website and follow their instructions to update the BIOS. A BIOS update can sometimes resolve compatibility issues and improve system stability.
7. Remove and Reinstall Problematic Drivers: If the issue persists, try uninstalling the storahci.sys driver and reinstalling it. Open Device Manager, expand the "Storage controllers" category, right-click on the driver, and select "Uninstall device." Then restart your computer, and Windows will automatically reinstall the driver.

Next Time Please Upload A Dump Because It's A Nuisance To Read.

Yeah I had already tried those before disabling cstates as they are the obvious offenders. I have searched this does seem to be a thing on Taichi boards but not only them. I'll give the driver install another go because I know know how that one can not work three times then magically fix it the fourth. I changed my settings for a full system memory dump next crash so hopefully I'll hve more for you to dig into. Thanks for your reply.

 

[atomicWAR]

I can tell you what the problem is here but you need to upload the dump for me to do so. There is way more to memory dump analysis than just analyze -v....

What form you want it in? I just find analyze finds most issues for me. I have my system set for a full memory dump on my next crash not just the 256bit I have now. Here's some more versions of the dump. If you have a particular viewer/view you'd like me to use let me know as I'd be happy to comply and thanks for your time. Sorry for the slow reply I oddly din't get notifications you had tried to help me out. I'll be more dilgent in checking the tread directly in the future instead of relying on notifications.

- <Event xmlns="

http://schemas.microsoft.com/win/2004/08/events/event

">

- <System>

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

<EventID>41</EventID>

<Version>9</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2023-06-06T08:40:54.3020573Z" />

<EventRecordID>78905</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>W4R</Computer>

<Security UserID="S-1-5-18" />

</System>

- <EventData>

<Data Name="BugcheckCode">159</Data>

<Data Name="BugcheckParameter1">0x3</Data>

<Data Name="BugcheckParameter2">0xffffbb889e3b8050</Data>

<Data Name="BugcheckParameter3">0xfffff8061ffc2178</Data>

<Data Name="BugcheckParameter4">0xffffbb88aa2978a0</Data>

<Data Name="SleepInProgress">0</Data>

<Data Name="PowerButtonTimestamp">0</Data>

<Data Name="BootAppStatus">0</Data>

<Data Name="Checkpoint">0</Data>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="SystemSleepTransitionsToOn">0</Data>

<Data Name="CsEntryScenarioInstanceId">0</Data>

<Data Name="BugcheckInfoFromEFI">false</Data>

<Data Name="CheckpointStatus">0</Data>

<Data Name="CsEntryScenarioInstanceIdV2">0</Data>

<Data Name="LongPowerButtonPressDetected">false</Data>

<Data Name="LidReliability">false</Data>

<Data Name="InputSuppressionState">0</Data>

<Data Name="PowerButtonSuppressionState">0</Data>

<Data Name="LidState">3</Data>

</EventData>

</Event>

 

[ubuysa]

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.

 

[atomicWAR]

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 THINK I found a fix as I haven't crashed in a few days now. I am not sure which did it or a combo of both but I enabled HIPM in power management and hunted down an Asmedia SATA driver not listed in Asrocks page nor obviously AMD's. I'd source the person for credit but I can't find it...I did A LOT of searches, digging through forums, etc etc.

 

[Gunhawk4711]

I THINK I found a fix as I haven't crashed in a few days now. I am not sure which did it or a combo of both but I enabled HIPM in power management and hunted down an Asmedia SATA driver not listed in Asrocks page nor obviously AMD's. I'd source the person for credit but I can't find it...I did A LOT of searches, digging through forums, etc etc.

Hi, as I am facing 100% the same problem as you and also running a x670e Taichi Mobo with AMD Ryzen 7950x, I am curious to hear about your fix. On another forum at computerbase I have a long thread where they convince me that this is because I am using quite old Harddisks, but I believe more in a Driver and/or Hardware issue. Would be glad if it is a driver issue so I don't need to RMA my combo. This really drives me nuts and the Disks I am using were all 100% functional in my old Intel platform.
Could you please point me to what you have changed (HIPM and where?)
Thanks in advance

 

[atomicWAR]

HIPM

Add AHCI Link Power Management to Power Options in Windows

How to Add or Remove 'AHCI Link Power Management - HIPM/DIPM' from Power Options in Windows

www.tenforums.com

Driver

Asmedia ASM-106x Sata 6G controller Drivers Version 3.2.3.0 WHQL

Windows

www.station-drivers.com

I did both to get it working hope it helps. Make sure to set turn on hipm In power management under hard disks.

 

[atomicWAR]

Hi, as I am facing 100% the same problem...

Hope those help

 

[atomicWAR]

Hi, as I am facing 100% the same problem as you and also running a x670e Taichi Mobo with AMD Ryzen 7950x, I am curious to hear about your fix. On another forum at computerbase I have a long thread where they convince me that this is because I am using quite old Harddisks, but I believe more in a Driver and/or Hardware issue. Would be glad if it is a driver issue so I don't need to RMA my combo. This really drives me nuts and the Disks I am using were all 100% functional in my old Intel platform.
Could you please point me to what you have changed (HIPM and where?)
Thanks in advance

LMK if that works for you I'll do a write up of the fix and post it.

 

[Gunhawk4711]

For the moment (after a clean installation of Windows 11) the problem has gone - even without this - however, I need to check back my config to make sure the Harddisk is still attached to the ASMedia Controller

 

[Gunhawk4711]

Hi - here is my update:
I ran the system successfully for quite some days, but I discovered, that my SATA Harddisks were attached to the X670E Chipset controller - not to the ASMedia one. I have now changes this and a couple of moments later, I am getting my old Powerstate BSOD Errors back, so my problem is definitively a problem with the ASMedia Controller on the Board and / or its drivers.

For now I followed the advise to enable the HIPM setting according to the article https://www.tenforums.com/tutorials/72971-add-ahci-link-power-management-power-options-windows.html. After entering the command

REG ADD HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60 /v Attributes /t REG_DWORD /d 2 /f

I was surprised to find the setting already enabled - not sure if that was also valid prior.

 

[atomicWAR]

Hi - here is my update:
I ran the system successfully for quite some days, but I discovered, that my SATA Harddisks were attached to the X670E Chipset controller - not to the ASMedia one. I have now changes this and a couple of moments later, I am getting my old Powerstate BSOD Errors back, so my problem is definitively a problem with the ASMedia Controller on the Board and / or its drivers.

For now I followed the advise to enable the HIPM setting according to the article https://www.tenforums.com/tutorials/72971-add-ahci-link-power-management-power-options-windows.html. After entering the command

REG ADD HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\0012ee47-9041-4b5d-9b77-535fba8b1442\0b2d69d7-a2a1-449c-9680-f91c70521c60 /v Attributes /t REG_DWORD /d 2 /f

I was surprised to find the setting already enabled - not sure if that was also valid prior.

It was the same for me on hipm...but the two bits seemed to fix the issue. Keep me looped in on your system stablity. I'll wait for a proper write up if you stay stable over lets say the weekend? Thx for the update! I really hope this clears things up for you. I use both controllers personally (7 disks) and I've been stable for over a week now so fingers crossed for you.

 

[Gunhawk4711]

#Update: Yesterday I followed the rest of your advise and installed the ASMedia 106x SATA Driver Package. Since then, the issue seem to be gone as well. If the system remains to be stable, I think the root cause were with the driver - obviously the Windows 11 out of the box driver is faulty then. I will let ASROCK know - they definitively should include the driver in there mainboard package!

 

[atomicWAR]

#Update: Yesterday I followed the rest of your advise and installed the ASMedia 106x SATA Driver Package. Since then, the issue seem to be gone as well. If the system remains to be stable, I think the root cause were with the driver - obviously the Windows 11 out of the box driver is faulty then. I will let ASROCK know - they definitively should include the driver in there mainboard package!

Awesome! Glad I could help. I'll do a real write up and post it later today or tomorrow. Thx for the update. Lmk if you ever need anything (dm or find me in the forums). I'll link the write up here when done.

 

[atomicWAR]

If you found this thread here is your fix...

Walkthrough - [FIX] BSOD DRIVER_POWER_STATE_FAILURE (9f) ASRock X670E Taichi motherboard via storahchi.

If you're here you've likely endured daily BSOD with your ASRock X670E Taichi motherboard. I use a lot of SATA ports and users like me find this DRIVER_POWER_STATE_FAILURE (9f) bug via storahci more easily than we'd like. It took me months to piece this fix together through trial error and some...

forums.tomshardware.com

 

[Techsnologic]

I'm glad I'm not the only one that's been getting this problem!
I've been searching around now for months after getting this issue with a build I completed in Feb.
I'm currently testing out the fixes posted above, but for reference, I don't have the Taichi motherboard, mine is a MSI MPG B650 Edge Wifi.
I've tested out reseating and swapping my RAM, swapping my GPU power cable, Re-installing Win 11 all to no avail so far so I'm hoping the above fixes work for me too.
I do have multiple drives installed, 2 on the bottom ports and 2 on the side ports as well as 2 NVME drives as well.
I'll try to remember to post again in a few days if this fixed my issue or not but I'm keeping my fingers crossed!

 

[Techsnologic]

I'm glad I'm not the only one that's been getting this problem!
I've been searching around now for months after getting this issue with a build I completed in Feb.
I'm currently testing out the fixes posted above, but for reference, I don't have the Taichi motherboard, mine is a MSI MPG B650 Edge Wifi.
I've tested out reseating and swapping my RAM, swapping my GPU power cable, Re-installing Win 11 all to no avail so far so I'm hoping the above fixes work for me too.
I do have multiple drives installed, 2 on the bottom ports and 2 on the side ports as well as 2 NVME drives as well.
I'll try to remember to post again in a few days if this fixed my issue or not but I'm keeping my fingers crossed!

Can confirm after 10 days of solid testing, no more BSODs! Seems to not only be an issue with the ASRock boards, but MSI too for the exact same reason.