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

[atomicWAR]

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 piece meal finds on other forums throughout the net that I don't properly remember who to source or I would. Anyways I'd like to save you the time with a condensed walk-through of my coalesced knowledge over the last five months. There are only a few things your going to need to do so you can fix this crash.

1. Download and install the latest AMD chipset drivers here.

2. Download and install this Asmedia 106x SATA driver here.

Mod Edit: Asmedia link updated as per post 22

 

[Gunhawk4711]

Hi,
I can also confirm that this has fixed my identical problem.

I only experiencing the BSOD problems when connecting SATA Harddisks to the ASMedia Ports SATA_A1-4 and not on the regular ones (SATA1-4). In addition the problem seem to only arise when Harddisk-Energy Saving mode is on - if you keep them running at all times, you won't trigger the error even if HDs were connected to the ASMedia SATA ports.

I have contacted ASRock with these observations and they are looking into this.

However, I do have some suspicion whether the Asmedia 106x SATA driver simply ignores the Energy Settings made in the OS and keeps the drives running anyway.

In my observation and when running the system without it, I could hear the Hard Drives turning on spinning (making some noise) whilst with the Asmedia driver they don't and they seem to be always accessible without any delays.
For example, without the driver it takes a while from showing the Hard Drive's content when changing the mode from sleep to awake.

 

[CalabazasBike]

Just registered for this issue. Will be getting the RMA motherboard back later this week. Will update my test status here.

One simple question - Why Windows 11 does BSOD simply because SATA power management setting? If a HDD can go to power saving mode, that's fine. If HDD cannot, why making it such a big deal and crash OS itself? Not so smart, isn't it!

 

[atomicWAR]

Just registered for this issue. Will be getting the RMA motherboard back later this week. Will update my test status here.

One simple question - Why Windows 11 does BSOD simply because SATA power management setting? If a HDD can go to power saving mode, that's fine. If HDD cannot, why making it such a big deal and crash OS itself? Not so smart, isn't it!

Lmk how the fix goes. I hope this helps more users out.

 

[Gunhawk4711]

Lmk how the fix goes. I hope this helps more users out.

I am not yet sure if RMA-ring the Board will fix that. I think it is more a SW/Driver/BIOS-related thing. There is a new Beta Bios out for the board that would allow to install the latest AMD Chipset Drivers, which create issues in Device Manager when installing with the current release BIOS.
I am wondering (and hoping) that one day the Chipset drivers will fix the SATA controller issue without having the need to install the (quite outdated ASM-106 SATA Drivers) as they are for Win 10 - not sure if there are more recent ones out and since ASROCK did not reference them, they think the standard drivers will suite the needs

 

[atomicWAR]

I am not yet sure if RMA-ring the Board will fix that. I think it is more a SW/Driver/BIOS-related thing. There is a new Beta Bios out for the board that would allow to install the latest AMD Chipset Drivers, which create issues in Device Manager when installing with the current release BIOS.
I am wondering (and hoping) that one day the Chipset drivers will fix the SATA controller issue without having the need to install the (quite outdated ASM-106 SATA Drivers) as they are for Win 10 - not sure if there are more recent ones out and since ASROCK did not reference them, they think the standard drivers will suite the needs

Actually from my research...that old driver, is actually the latest driver. Sad but true. That said you find a newer version lmk I'll post it.

 

[CalabazasBike]

I am not yet sure if RMA-ring the Board will fix that. I think it is more a SW/Driver/BIOS-related thing. There is a new Beta Bios out for the board that would allow to install the latest AMD Chipset Drivers, which create issues in Device Manager when installing with the current release BIOS.
I am wondering (and hoping) that one day the Chipset drivers will fix the SATA controller issue without having the need to install the (quite outdated ASM-106 SATA Drivers) as they are for Win 10 - not sure if there are more recent ones out and since ASROCK did not reference them, they think the standard drivers will suite the needs

Idle-BSOD issue didn't appear until after 2-3 months of light usage. Didn't want to load big engineering SW until I'm confident. Something turned bad that's not there before. Whether the fix posted here can resolve it? Have to test to confirm today.

Tried a dozen BIOS settings before motherboard RMA. I might need to RMA the CPU later if it still fails. Another thread pointed that out. AMD knows something but not disclosing the root cause. It's annoying to me after spending thousands of after-tax dollars.

Have designed PC for 30+ years. However, this PC is a tool. I don't gain anything debugging it. Tearing it down and RMA is quite a hassle.

 

[atomicWAR]

Idle-BSOD issue didn't not appear until after 2-3 months of light usage. Didn't want to load big engineering SW until I'm confident. Something turned bad that's not there before. Whether the fix posted here can resolve it? Have to test to confirm today.

Tried a dozen BIOS settings before motherboard RMA. I might need to RMA the CPU later if it still fails. Another thread pointed that out. AMD knows something but not disclosing the root cause. It's annoying to me after spending thousands of after-tax dollars.

Have designed PC for 30+ years. However, this PC is a tool. I don't gain anything debugging it. Tearing it down and RMA is quite a hassle.

I usually like ASRock but these x670E Taichi boards and Ryzen 7000 chips are having some serious teething issues. I was 'mostly' stable the first month or so as well (didn't check the minidumps ATP as I was testing a lot of things I expected to cause crashes). Then it was ram crashing everything until the first X3D bios dropped. But that took months to nail down because it frequently showed up as an Nvidia driver issue causing the crash while others hinted at the ram stability being in question (passed memtest with flying colors though?) peppered in with some storahci crashes which still weren't as common since I was crashing ALL the time at first. I always suspected a hardware bug (or maybe driver to OS level if software) as everyone else was having the same issues from my research. So I skipped RMA process as I was already locked in past the return period and soldiered on fixing issues as their sources became more clear.

Now with current bios and since I came up with the storahci fix I think I had one crash in the weeks since while gaming in what was a hot office which oddly didn't give me a minidump, I checked. At this point I could recommend this board if someone is made aware of its quirks and was leaning AMD. But I wouldn't have even given it a thumbs up 2 months ago. I figure its both AMD and ASRocks fault. Certainly Asrock could have these Asmedia drivers up but last I checked, which was now, they don't. I suspect Microsoft isn't free of guilt either but they seem low down the list. I feel very much like a beta tester, except I am not getting paid or early access, quite the opposite sadly.

 

[CalabazasBike]

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 piece meal finds on other forums throughout the net that I don't properly remember who to source or I would. Anyways I'd like to save you the time with a condensed walk-through of my coalesced knowledge over the last five months. There are only a few things your going to need to do so you can fix this crash.

1. Download and install the latest AMD chipset drivers here.

2. Download and install this Asmedia 106x SATA driver here. (note: ASRock does not have these on their main page.)

3. You may also need/I highly encourage you to enable HIPM in your power profile. There is a great walk-through you can follow on how to do this here.

My ASRock X670E Taichi Carrara RMA board arrived. To ensure clean test, I've striped down everything to a "safe" start.

[Configuration]
CPU - AMD 7950X
Motherboard - ASRock X760E Taichi Carrara
BIOS - 1.24 with AGESA ComboAM5 1.0.0.7a; No OC setting; fan and storage configured; lowered to DDR5-3600 for test
RAM - (to cross out this factor) one stick running at 3600 of Corsair Vengeance 64 GB (2 x 32 GB) DDR5-6600 CL32
PSU - Thermaltake Toughpower GF3 1000W
GPU - Dell 86RMK Nvidia Geforce RTX 3060 TI 8GB GDDR6 PCIe
C: - RAID 0 of 2 M.2 WD Black 1TB SN850X NVMe
D: - HDD WD Red Pro 20 TB on 2nd AMD PROM21
E: - HDD WD Red Pro 20 TB on ASM1061 on 1st AMD PROM21
OS - Win11 Pro; all update till now
AMD chipset driver - 5.05.16.529 (as recommended action 1)
ASMedia 106x driver - Tried both ASRock stock & 3.2.3.0 WHQL (as recommended action 2)
AHCI HIPM - enabled (as recommended action 3)
OS Sleep mode - off

[Test steps]
Boot Win11 Pro, login, let it sit there idle.

[Test result]
Idle-crash issue repeated in 2 hours.

[Re-Test]
Change power setting of ThunderBolt PWR Management to allow power-down device.

My conclusion so far - crash under idle state after login is unacceptable. Root cause should be power management related of AMD Ryzen 9 7950X. Need to RMA CPU.

 

[atomicWAR]

Update. Confirmed this fix works on MSI MPG B650 Edge Wifi motherboard as well. Likely this is true for any AM5 board using an Asmedia 106x SATA controller.

 

[CalabazasBike]

In my system, the only reliable condition is (tested 72 hrs):

- Apply 3 steps as the beginning of this thread. (otherwise: idle-crash within 4 hrs)​

- Change power setting of ThunderBolt PWR Management to allow power-down device. (otherwise: idle-crash within 12 hrs)​

- Change BIOS Global C-State setting to Disabled.​

Drawback of such setup is high cpu clock rate even under low utilization. Don't like the high power consumption and the potential future C-State incurred issue. Upon receiving RMA CPU, I'll test it in backward steps.

 

[atomicWAR]

In my system, the only reliable condition is (tested 72 hrs):

- Apply 3 steps as the beginning of this thread. (otherwise: idle-crash within 4 hrs)​

- Change power setting of ThunderBolt PWR Management to allow power-down device. (otherwise: idle-crash within 12 hrs)​

- Change BIOS Global C-State setting to Disabled.​

Drawback of such setup is high cpu clock rate even under low utilization. Don't like the high power consumption and the potential future C-State incurred issue. Upon receiving RMA CPU, I'll test it in backward steps.

Interesting. I didn't need to disable C states or intentionally screw with thunderbolt settings, as I naturally set to allow power down after getting stable as I didn't want to waste juice, for the fix to work. That said prior to my fix I did need to disable C states/thunderbolt power down/ no HDD idle state in pwer profile etc etc to be somewhat stable (minutes-24+ hours between BSOD extremely variable...even got a full week once). But once I was 'stable' I wanted my power savings so I re-enabled everything in c states, power profiles (ie hdd power down after 20min), thunderbolt power. So far no issues for me, yet. That said there is clearly some sleep issues with storahci using the Asmedia 106x (possibly other vendors as well) on the default SATA driver. From what I can tell this fix works for most x670e Taichi users (and others mobos using the asmedia sata) but not everyone. Sadly AM5 users are beta testers...I had hoped for better but should have known BETTER as well with a new AMD socket as it isn't my first rodeo. Regardless some of this is drivers but I also suspect some of this is the either CPU or IO controller related as this was only the LAST issue I had getting my system stable, thankfully. First it was ram/cpu stability (three bios to fix?) which gave you video driver issues at random making it hard to parse what the REAL problem was. I love AMD but I miss the days of 64FX when every board I bought was stable from the word go. Phenom onwards I had bios and other issues...and the OG 1st 1GHz CPU which loved to lock up in a warm room. Thunderbird-64FX though was rock solid for me.

Anyways I look forward to hearing back from you after getting your CPU RMA'd tested. LMK if there is anything you need!

 

[CalabazasBike]

Tested 1 week with the RMA'd CPU. Same thing. System crashed during idle unless Global C-State is disabled.

The C-state incompatible of AMD 7950x is real. AMD managed to send me another CPU with same bug. Frustrated.

 

[atomicWAR]

Tested 1 week with the RMA'd CPU. Same thing. System crashed during idle unless Global C-State is disabled.

The C-state incompatible of AMD 7950x is real. AMD managed to send me another CPU with same bug. Frustrated.

That's a real bummer. My wife is putting her rig together next week with an x670e taichi and a 7950X3D. It'll will double as my storage back (80TB) up so it will be heavily populated with SATA drives. I'll let you know if she has issues with c states like you or if she slides by with my fix alone like I did and some others. Keep me posted on your rigs stablity and I'll do the same on ours.

 

[CalabazasBike]

AMD suggested me of below steps. To my surprise, it runs fine for 48 hours under Global C-State enabled.

1. Update ASRock bios to the latest version 1.28 from the below link:

https://www.asrock.com/mb/AMD/X670E Taichi Carrara/index.asp#BIOS​

2. Update 7950x CPU driver.

https://www.amd.com/en/support/apu/amd-ryzen-processors/amd-ryzen-9-desktop-processors/amd-ryzen-9-7950x

3. Update Nvidia driver. (if you have it)

NVIDIA Studio Driver | 536.67 | Windows 10 64-bit, Windows 11​

NVIDIA Studio Driver | 536.67 | Windows 10 64-bit, Windows 11 | NVIDIA

Download the English (US) NVIDIA Studio Driver for Windows 10 64-bit, Windows 11 systems. Released 2023.7.18

www.nvidia.com

​

GeForce Game Ready Driver | 536.67 | Windows 10 64-bit, Windows 11​

GeForce Game Ready Driver | 536.67 | Windows 10 64-bit, Windows 11 | NVIDIA

Download the English (US) GeForce Game Ready Driver for Windows 10 64-bit, Windows 11 systems. Released 2023.7.18

www.nvidia.com

4. Remove ASRock Tuning application.

Will give it a week to see if it really works reliably. Didn't expect myself to be beta tester for 4 months...

 

[CalabazasBike]

It crashed again after 150 hours. Although an improvement over previous 2-4 hours, it's unacceptable that a PC can crash during idle. Asking AMD to swap a 7950x which is c-state compatible.

 

[CalabazasBike]

Disabled Global C-State in BIOS and retest. It runs (idle with near 1% load) for 8 days straight and is still going. That confirms that the 7950x under test has C-state compatibility issue, same as previous one. 5 months has passed and I still don't feel comfortable installing any app.

 

[kadour]

I registered just to say thanks!!! This 100% solved the issues I've been having for months. Same exact symptoms. DRIVER_POWER_STATE_FAILURE BSOD's. I used WinDbg to confirm it was storeahci. It seemed to be made especially worse running VMWare containers. I followed steps 1-3 and not a single BSOD since. I haven't had to mess with C-state. Really appreciate you figuring this out atomicWAR. ;-)

 

[atomicWAR]

I registered just to say thanks!!! This 100% solved the issues I've been having for months. Same exact symptoms. DRIVER_POWER_STATE_FAILURE BSOD's. I used WinDbg to confirm it was storeahci. It seemed to be made especially worse running VMWare containers. I followed steps 1-3 and not a single BSOD since. I haven't had to mess with C-state. Really appreciate you figuring this out atomicWAR. ;-)

So very glad I could help you out. Please keep me looped in on any issues that may or may not crop up so I can 'try' to adjust my fix accordingly.

 

[kadour]

Do you think there is any benefit / risk to updating the driver further? If I'm reading this correctly, 3.3.5.0 is out. I'm not sure if this is the same chipset we're running or not.
https://www.techpowerup.com/forums/...d-firmware-for-asmedia-asm106x-series.264571/

After suffering with this for months, I'm not eager to destabilize things. On the other hand, I like being up to date.

 

[atomicWAR]

Do you think there is any benefit / risk to updating the driver further? If I'm reading this correctly, 3.3.5.0 is out. I'm not sure if this is the same chipset we're running or not.
https://www.techpowerup.com/forums/...d-firmware-for-asmedia-asm106x-series.264571/

After suffering with this for months, I'm not eager to destabilize things. On the other hand, I like being up to date.

I would love an updated driver. Lmc the legitimacy of the post/driver. Plenty of hack stuff out there. Thx for the heads up, I'll reply again soon.

 

[atomicWAR]

Looks good but IDK if I'd trust a random forum driver. I am likely going to try this version. Great find thank you so much for posting it.

Asmedia ASM-1x6x Sata 6G controller Drivers Version 3.3.5.0 WHQL

Windows 7/8/10/11

www.station-drivers.com

Edit: update...well I did an oopsie. When I went to DL this driver, I realized I had already downloaded it and installed it. I apparently linked the wrong driver page in my walkthrough. I was surprised I didn't have the latest driver as I am anal abvout such things for security. So anyone still having trouble with my fix I apologize. Plz use this latest driver posted above. I'd 'fix' my fix but I can no longer update that post....I am not even sure being an ambassador can help me but I'll talk to the mods to see if I can get the original post updated...thx for your time and patience.

 

[0xDEADFED5]

those looking for this driver can find it here at the top:

Microsoft Update Catalog

direct link for 3.3.5.0:

https://catalog.s.download.windowsupdate.com/d/msdownload/update/driver/drvs/2023/05/771e9dc9-cb36-4972-8b61-5a1b80592762_e552db9917483dfb84cb8e9b50d3750b449d9c13.cab