storahci.sys causing blue screen

[richiestang_78]

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-eQqihgSW4KDPh1nwd54ykH7TBssGtAV/view?usp=sharing

 

[kerberos_20]

nothing suspicious in minidump, just that drive failed to power up

 

[richiestang_78]

nothing suspicious in minidump, just that drive failed to power up

Seems to be an issue with some AMD boards/AMD builds . Ive looked around and the only real fix seems to be turning off drive sleep.

Also learned AMD doesn't actually make SATA drivers anymore and just uses the standard Microsoft ones, which when I check mine seem to be from 2006 ( version 10.0.22621.608) which I think is the issue but dont know how to fix that.

Found this thread on the microsoft community with a couple of suggested fixes but not sure if it actually is worth the hassle if I dont know the root cause.

Redirecting

 

[kerberos_20]

Seems to be an issue with some AMD boards/AMD builds . Ive looked around and the only real fix seems to be turning off drive sleep.

Also learned AMD doesn't actually make SATA drivers anymore and just uses the standard Microsoft ones, which when I check mine seem to be from 2006 ( version 10.0.22621.608) which I think is the issue but dont know how to fix that.

Found this thread on the microsoft community with a couple of suggested fixes but not sure if it actually is worth the hassle if I dont know the root cause.

Redirecting

amd chipset drivers does not touch disk drives at all unless you use raid
microsoft drivers are fine, SATA hasnt been updated for ages

your drive which has issue powering up (hardware issue)

!DevNode ffffba8b7902bc20 :
DeviceInst is "SCSI\Disk&Ven_&Prod_ST1000DM003-1CH1\7&2ff5684&0&010000"
ServiceName is "disk"

seagate barracuda 1TB - ST1000DM003-1CH1

 

[kerberos_20]

what pops in mind, do you have enabled hotswap sata in bios? this could be interfering with your not hot swappable sata drive

you could also try different sata data cable (small one) or different SATA port on mainboard

 

[kerberos_20]

other than that, there could be also issue with your sata controller, from minidump it shows up as VEN_1B21&DEV_0612, which would be asmedia 106X
there is one controller per two sata ports, meaning two ports could have issue if controller is faulty, you mainboard seem to have 6 sata slots, that mean 3 SATA controllers
sata 1,2 - one
sata 3,4 - second
sata 5,6 - third

shuffle your drive to different controller, if issue persists, its drive failure (its 10 years old afterall)

 

[richiestang_78]

other than that, there could be also issue with your sata controller, from minidump it shows up as VEN_1B21&DEV_0612, which would be asmedia 106X
there is one controller per two sata ports, meaning two ports could have issue if controller is faulty, you mainboard seem to have 6 sata slots, that mean 3 SATA controllers
sata 1,2 - one
sata 3,4 - second
sata 5,6 - third

shuffle your drive to different controller, if issue persists, its drive failure (its 10 years old afterall)

Thanks for all the help, hot swap was disabled in the BIOS. I did change the port and made sure all teh cables were firmly pressed in. Your right it could be the drive, I'm looking at ditching the HDD anyway for a full SSD computer but was trying to hold off as long as I could. Might just go ahead and buy a Crucial 2TB and swap out that Seagate. I honestly forgot how old that drive was.

 

[richiestang_78]

other than that, there could be also issue with your sata controller, from minidump it shows up as VEN_1B21&DEV_0612, which would be asmedia 106X
there is one controller per two sata ports, meaning two ports could have issue if controller is faulty, you mainboard seem to have 6 sata slots, that mean 3 SATA controllers
sata 1,2 - one
sata 3,4 - second
sata 5,6 - third

shuffle your drive to different controller, if issue persists, its drive failure (its 10 years old afterall)

Swapped out the old Seagate for a Crucial SSD but still have the problem. I still have another 4TB Seagate HDD in the computer but I ran SeaTools and the drive checked out, also checked for a new firmware for it but its up to date. Found a reddit post of someone with the exact same issue, I think there is some sort of problem with Seagate drives, AMD boards and Windows 11 in some sort of combination.

 

[richiestang_78]

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

Redirecting