The storahci.sys file is making my computer turn blue.
The storahci.sys file is making my computer turn blue.
I didn't mean to post twice, but I thought I should add more details. Now a new post seems easier, and I keep getting sporadic crashes that feel like bluescreens. It happens mostly when I turn my computer off so it can sleep. I know this because the screen goes dark and shows just "login" before coming back on.
So I checked Event Viewer to see what was wrong. The error message said DRIVER_POWER_STATE_FAILURE (9f), which means a driver failed while trying to control power. The arguments were: Arg1: 0000000000000003, meaning the device object blocked the IRP for too long; and there was an argument about a Physical Device Object in the stack. I also saw another part saying "TRIAGE_9F_POWER on Win7 and higher" or "Functional Device Object of the stack" for older versions, plus details about scrolled-down logs pointing to storahci.sys as the cause.
I know this is related to the drive controller, but I've already tried reinstalling chipset drivers with no success. What else should I try? My system drive is a fresh install of Windows 11, but my computer has two hard drives and one SSD that were data/storage drives from my last machine (a Win 10 system with an Intel 7700K CPU and Asus 270F motherboard). The original drives worked fine before.
Here is the dump file: https://drive.google.com/file/d/1-eQqihg...sp=sharing
Seems like some AMD boards or AMD builds are having problems. I looked around and the only real fix seems to be turning off drive sleep mode too. Also learned that AMD doesn't actually make SATA drivers anymore, they just use Microsoft ones. When I check mine, the version is from 2006 (version 10.0.22621.608), which I think might be the problem but I don't know how to fix it. Found this thread on the Microsoft community with a few suggested fixes, but not sure if it's worth the hassle since I don't know the real cause yet. Bluescreen crashes from storahci? - Microsoft Q&A
I built a new Windows 11 Workstation PC recently and it has had 20+ bluescreen crashes. The error is always:
122922-10140-01.dmp
Date/Time: 29/12/2022 6:49:07...
AMD chipsets don't mess with hard drives by default. You just need the right Microsoft drivers, but SATA cables have been stuck since forever. Your drive isn't working because of a physical problem, not software. Here is your hard drive: Seagate Barracuda 1TB - ST1000DM003-1CH1.
What comes to mind when you think of hot swap SATA? Is that setting turned on in the BIOS? Maybe it's messing up your actual hot-swappable drive. You might also test a different SATA data cable, or try another SATA port on your motherboard.
Besides the other problem, there might be an issue with your SATA controller. When you check the minidump file, it shows "VEN_1B21&DEV_061", which is a device from an ASMedia 106X chip. That means one controller can handle two SATA ports, so if that specific controller fails, both of those ports could stop working. Your mainboard has six slots in total, but it uses three controllers to manage them: the first two for the first group, the next two for the second group, and a third for the last two.
If you move one of your drives to another slot or controller and the problem still happens, then the drive itself is likely broken. It's already been over 10 years old anyway, so that's probably not going to get fixed soon.
Thanks so much for helping me, hot swap is turned off in the BIOS. I changed the port and made sure all the cables were really pressed in. You are right, maybe it's just the drive. I am looking at ditching the HDD anyway to make a full SSD computer, but I wanted to keep trying as long as possible. Maybe I will just buy a Crucial 2TB and swap out that Seagate one. Honestly, I forgot how old that drive was.
I swapped the old Seagate hard drive for a new Crucial SSD, but it still acts like it has trouble. I have another 4TB Seagate HDD sitting here in my computer. When I used SeaTools to check it out and looked at its firmware, everything was fine—it's got the latest version. I found someone on Reddit with an identical problem too. It seems like maybe there is a specific mix of issues involving Seagate drives, AMD processors, and Windows 11 that causes this weird glitch.
I need to share something because there seems to be a problem with the SATA controllers. It looks like the ones from ASMedia might be the cause, and I've seen other posts about it too. Right now, the only fix is to use the chipset SATA ports and turn off the ASMedia ones completely. This was my old computer build with an AM4 setup where this never happened. I'm using a Samsung Evo 970 Plus SSD. I tried putting Windows on my Crucial P5 Plus and got the same crash, so it's probably not a drive issue at all. community.amd.com New computer coming together but getting a crash from DRIVER_POWER_STATE_FAILURE - Microsoft Q&A Hi, I run Windows 11 Pro for the main version of the work and get crashes every few hours. Bug check code: 0x0000009f Parameter 1: 00000000`00000003 Parameter 2: ffffdc89`5b9c9050 Parameter 3: fffff589`f0abf178 Parameter 4:… answers.microsoft.com