F5F Stay Refreshed Software Operating Systems storahci.sys is linked to the blue screen issue.

storahci.sys is linked to the blue screen issue.

storahci.sys is linked to the blue screen issue.

S
superfreak1203
Junior Member
6
07-24-2021, 03:58 PM
#1
Didnt mean to double post but thought I should add some more details and a new post seemed easier, I keep getting sporadic bluescreen crashes, seems to be mostly when I leave my computer and it goes to sleep, I know because it will be on the login screen when I come back. I then checked the event viewer to see the error followed by the dump files and it says the following:
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: ffffcb07e57df050, Physical Device Object of the stack
Arg3: ffffc90dda0d7198, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffcb07ea5189c0, The blocked IRP
Scrolled down the log and it seems to points to the storahci.sys as the cause.
I know this is a drive controller but have already tried reinstalling the chipset drivers with no effect. What else should I try? My system drive is a fresh install of Windows 11, but I do have two HDD and a two SSDs that were data/storage drive I brough over from my last computer. I didn't have any issues with the drives on my previous system, which was a Windows 10 Intel 7700K and Asus 270F mobo.
here is the dmp file
https://drive.google.com/file/d/1-eQqihg...sp=sharing
S
superfreak1203
07-24-2021, 03:58 PM #1

Didnt mean to double post but thought I should add some more details and a new post seemed easier, I keep getting sporadic bluescreen crashes, seems to be mostly when I leave my computer and it goes to sleep, I know because it will be on the login screen when I come back. I then checked the event viewer to see the error followed by the dump files and it says the following:
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: ffffcb07e57df050, Physical Device Object of the stack
Arg3: ffffc90dda0d7198, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffcb07ea5189c0, The blocked IRP
Scrolled down the log and it seems to points to the storahci.sys as the cause.
I know this is a drive controller but have already tried reinstalling the chipset drivers with no effect. What else should I try? My system drive is a fresh install of Windows 11, but I do have two HDD and a two SSDs that were data/storage drive I brough over from my last computer. I didn't have any issues with the drives on my previous system, which was a Windows 10 Intel 7700K and Asus 270F mobo.
here is the dmp file
https://drive.google.com/file/d/1-eQqihg...sp=sharing

O
Ombilicus
Junior Member
12
07-25-2021, 09:22 PM
#2
no unusual signs in the minidump, only that the drive didn't start
O
Ombilicus
07-25-2021, 09:22 PM #2

no unusual signs in the minidump, only that the drive didn't start

R
Raphdu38
Junior Member
18
07-25-2021, 10:23 PM
#3
It appears there may be a problem with certain AMD boards or builds. The only apparent solution seems to be disabling drive sleep. Also discovered that AMD no longer develops SATA drivers and relies on the standard Microsoft ones, which may be outdated (version 10.0.22621.608 from 2006). This could be the source of the issue, but it's unclear if fixing it would help. A thread on the Microsoft community suggests a few possible fixes, though it's uncertain if it's worth the effort without knowing the exact cause.
R
Raphdu38
07-25-2021, 10:23 PM #3

It appears there may be a problem with certain AMD boards or builds. The only apparent solution seems to be disabling drive sleep. Also discovered that AMD no longer develops SATA drivers and relies on the standard Microsoft ones, which may be outdated (version 10.0.22621.608 from 2006). This could be the source of the issue, but it's unclear if fixing it would help. A thread on the Microsoft community suggests a few possible fixes, though it's uncertain if it's worth the effort without knowing the exact cause.

D
DreaMaker20
Member
124
07-25-2021, 11:18 PM
#4
amd chipset drivers don't interact with disk drives unless raid is enabled.
microsoft drivers work, but sata hasn't been updated in a long time.
your drive has trouble starting (hardware problem).
seagate barracuda 1TB - ST1000DM003-1CH1
D
DreaMaker20
07-25-2021, 11:18 PM #4

amd chipset drivers don't interact with disk drives unless raid is enabled.
microsoft drivers work, but sata hasn't been updated in a long time.
your drive has trouble starting (hardware problem).
seagate barracuda 1TB - ST1000DM003-1CH1

O
OmqDace
Posting Freak
798
08-05-2021, 11:42 PM
#5
what comes to mind is whether hotswap sata is active in bios, possibly affecting your non-hot-swappable sata drive. You might also want to test with a smaller sata data cable or another sata port on the motherboard.
O
OmqDace
08-05-2021, 11:42 PM #5

what comes to mind is whether hotswap sata is active in bios, possibly affecting your non-hot-swappable sata drive. You might also want to test with a smaller sata data cable or another sata port on the motherboard.

R
196
08-13-2021, 05:33 PM
#6
other than that, there might be problems with your SATA controller. From the minidump, it appears as VEN_1B21&DEV_0612, which corresponds to Asmedia 106X. There is one controller for every two SATA ports, so a fault in the controller could affect two ports. Your mainboard has six SATA slots, indicating three controllers. SATA 1 and 2 are one, SATA 3 and 4 are the second, and SATA 5 and 6 are the third. Try moving your drive to a different controller; if the issue continues, it may point to a drive failure (it’s ten years old).
R
RasselLetsPlay
08-13-2021, 05:33 PM #6

other than that, there might be problems with your SATA controller. From the minidump, it appears as VEN_1B21&DEV_0612, which corresponds to Asmedia 106X. There is one controller for every two SATA ports, so a fault in the controller could affect two ports. Your mainboard has six SATA slots, indicating three controllers. SATA 1 and 2 are one, SATA 3 and 4 are the second, and SATA 5 and 6 are the third. Try moving your drive to a different controller; if the issue continues, it may point to a drive failure (it’s ten years old).

_
_juhuaxia12
Member
61
08-19-2021, 09:36 AM
#7
Thank you for the assistance. The BIOS had hot swap turned off, and I adjusted the port while ensuring all cables were securely connected. You're correct—it might be the drive, and I'm considering replacing it with a new SSD instead of sticking with the HDD. I was trying to delay the decision as long as possible, but now I might just purchase a Crucial 2TB and swap the Seagate drive. I didn't realize how outdated that storage device was.
_
_juhuaxia12
08-19-2021, 09:36 AM #7

Thank you for the assistance. The BIOS had hot swap turned off, and I adjusted the port while ensuring all cables were securely connected. You're correct—it might be the drive, and I'm considering replacing it with a new SSD instead of sticking with the HDD. I was trying to delay the decision as long as possible, but now I might just purchase a Crucial 2TB and swap the Seagate drive. I didn't realize how outdated that storage device was.

B
benjiboo751
Junior Member
38
08-19-2021, 06:30 PM
#8
Swapped the old Seagate for a Crucial SSD yet the issue persists. I still have a 4TB Seagate HDD in the computer, but SeaTools showed it as available. I checked for new firmware, but it was already up to date. I found a Reddit post about someone else having the same problem, suggesting a possible issue with Seagate drives, AMD boards, and Windows 11 together.
B
benjiboo751
08-19-2021, 06:30 PM #8

Swapped the old Seagate for a Crucial SSD yet the issue persists. I still have a 4TB Seagate HDD in the computer, but SeaTools showed it as available. I checked for new firmware, but it was already up to date. I found a Reddit post about someone else having the same problem, suggesting a possible issue with Seagate drives, AMD boards, and Windows 11 together.

U
Upss1
Junior Member
11
08-21-2021, 06:28 AM
#9
I wanted to post an update, seems to be an issue with the SATA controllers, seems to be the ASMedia ones, I have found several threads about it, and looks like the only real work around right now is to use the chipset SATA ports and disable the ASMedia ones all together.
Re: Random BSOD DRIVER_POWER_STATE_FAILURE amdppm.sys Ryzen 7 7700X
This SSD used to be in one of my AM4 builds and I never had this issue. I’m using a Samsung Evo 970 plus. As an experiment i installed Windows on my crucial P5 plus and I had the same crash so I don’t think it is drive related as I have ruled that out.
community.amd.com
New computer build/install and getting crash from DRIVER_POWER_STATE_FAILURE - Microsoft Q&A
Hi, I'm running windows 11 pro on the main production version and get a crash every few hours. DRIVER_POWER_STATE_FAILURE Bug check code: 0x0000009f Parameter 1: 00000000`00000003 Parameter 2: ffffdc89`5b9c9050 Parameter 3: fffff589`f0abf178 Parameter 4:…
answers.microsoft.com
U
Upss1
08-21-2021, 06:28 AM #9

I wanted to post an update, seems to be an issue with the SATA controllers, seems to be the ASMedia ones, I have found several threads about it, and looks like the only real work around right now is to use the chipset SATA ports and disable the ASMedia ones all together.
Re: Random BSOD DRIVER_POWER_STATE_FAILURE amdppm.sys Ryzen 7 7700X
This SSD used to be in one of my AM4 builds and I never had this issue. I’m using a Samsung Evo 970 plus. As an experiment i installed Windows on my crucial P5 plus and I had the same crash so I don’t think it is drive related as I have ruled that out.
community.amd.com
New computer build/install and getting crash from DRIVER_POWER_STATE_FAILURE - Microsoft Q&A
Hi, I'm running windows 11 pro on the main production version and get a crash every few hours. DRIVER_POWER_STATE_FAILURE Bug check code: 0x0000009f Parameter 1: 00000000`00000003 Parameter 2: ffffdc89`5b9c9050 Parameter 3: fffff589`f0abf178 Parameter 4:…
answers.microsoft.com