Error code BSOD driver_power_state_failure in storage system OS
Error code BSOD driver_power_state_failure in storage system OS
I get 5 BSODs in 3 days. All of them are DRIVER_POWER_STATE_FAILURE and IMAGE_NAME: storahci.sys . I tried two differend chipset drivers and ssd utility but couldn't fix. Here are all minidump files. Example (last one): ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true -- Configuring repositories ----> Repository : LocalInstalled, Enabled: true ----> Repository : UserExtensions, Enabled: true >>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds ************* Waiting for Debugger Extensions Gallery to Initialize ************** >>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds ----> Repository : UserExtensions, Enabled: true, Packages count: 0 ----> Repository : LocalInstalled, Enabled: true, Packages count: 36 Microsoft ® Windows Debugger Version 10.0.25877.1004 AMD64 Copyright © Microsoft Corporation. All rights reserved. Loading Dump File [G:\Belgelerim\My Programs\BSOD\082223-16218-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Kernel base = 0xfffff806`06e00000 PsLoadedModuleList = 0xfffff806`07a130e0 Debug session time: Tue Aug 22 02:16:18.606 2023 (UTC + 3:00) System Uptime: 0 days 2:54:02.395 Loading Kernel Symbols .. Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long. Run !sym noisy before .reload to track down problems loading symbols. ............................................................. ................................................................ ................................................................ .... Loading User Symbols Loading unloaded module list .................. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff806`07231250 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffffb0b`6f65f130=000000000000009f 2: 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: ffffbe8319962050, Physical Device Object of the stack Arg3: fffffb0b6f65f178, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack Arg4: ffffbe8319c8e9c0, The blocked IRP Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 1187 Key : Analysis.Elapsed.mSec Value: 2727 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: 125 Key : Analysis.Init.Elapsed.mSec Value: 10032 Key : Analysis.Memory.CommitPeak.Mb Value: 104 Key : Bugcheck.Code.LegacyAPI Value: 0x9f Key : Dump.Attributes.AsUlong Value: 1808 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 Key : Failure.Bucket Value: 0x9F_3_IMAGE_storahci.sys Key : Failure.Hash Value: {21defffd-4d1f-b62d-8f72-d4892aa9cff8} Key : Hypervisor.Enlightenments.ValueHex Value: 1497cf94 Key : Hypervisor.Flags.AnyHypervisorPresent Value: 1 Key : Hypervisor.Flags.ApicEnlightened Value: 1 Key : Hypervisor.Flags.ApicVirtualizationAvailable Value: 0 Key : Hypervisor.Flags.AsyncMemoryHint Value: 0 Key : Hypervisor.Flags.CoreSchedulerRequested Value: 0 Key : Hypervisor.Flags.CpuManager Value: 1 Key : Hypervisor.Flags.DeprecateAutoEoi Value: 0 Key : Hypervisor.Flags.DynamicCpuDisabled Value: 1 Key : Hypervisor.Flags.Epf Value: 0 Key : Hypervisor.Flags.ExtendedProcessorMasks Value: 1 Key : Hypervisor.Flags.HardwareMbecAvailable Value: 1 Key : Hypervisor.Flags.MaxBankNumber Value: 0 Key : Hypervisor.Flags.MemoryZeroingControl Value: 0 Key : Hypervisor.Flags.NoExtendedRangeFlush Value: 0 Key : Hypervisor.Flags.NoNonArchCoreSharing Value: 1 Key : Hypervisor.Flags.Phase0InitDone Value: 1 Key : Hypervisor.Flags.PowerSchedulerQos Value: 0 Key : Hypervisor.Flags.RootScheduler Value: 0 Key : Hypervisor.Flags.SynicAvailable Value: 1 Key : Hypervisor.Flags.UseQpcBias Value: 0 Key : Hypervisor.Flags.Value Value: 4853999 Key : Hypervisor.Flags.ValueHex Value: 4a10ef Key : Hypervisor.Flags.VpAssistPage Value: 1 Key : Hypervisor.Flags.VsmAvailable Value: 1 Key : Hypervisor.RootFlags.AccessStats Value: 1 Key : Hypervisor.RootFlags.CrashdumpEnlightened Value: 1 Key : Hypervisor.RootFlags.CreateVirtualProcessor Value: 1 Key : Hypervisor.RootFlags.DisableHyperthreading Value: 0 Key : Hypervisor.RootFlags.HostTimelineSync Value: 1 Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled Value: 0 Key : Hypervisor.RootFlags.IsHyperV Value: 1 Key : Hypervisor.RootFlags.LivedumpEnlightened Value: 1 Key : Hypervisor.RootFlags.MapDeviceInterrupt Value: 1 Key : Hypervisor.RootFlags.MceEnlightened Value: 1 Key : Hypervisor.RootFlags.Nested Value: 0 Key : Hypervisor.RootFlags.StartLogicalProcessor Value: 1 Key : Hypervisor.RootFlags.Value Value: 1015 Key : Hypervisor.RootFlags.ValueHex Value: 3f7 BUGCHECK_CODE: 9f BUGCHECK_P1: 3 BUGCHECK_P2: ffffbe8319962050 BUGCHECK_P3: fffffb0b6f65f178 BUGCHECK_P4: ffffbe8319c8e9c0 FILE_IN_CAB: 082223-16218-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump DRVPOWERSTATE_SUBCODE: 3 DRIVER_OBJECT: ffffbe8316b8dd50 IMAGE_NAME: storahci.sys MODULE_NAME: storahci FAULTING_MODULE: fffff806098c0000 storahci BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffffb0b`6f65f128 fffff806`0739d456 : 00000000`0000009f 00000000`00000003 ffffbe83`19962050 fffffb0b`6f65f178 : nt!KeBugCheckEx fffffb0b`6f65f130 fffff806`0739d32c : 00000000`00000002 ffff9a00`15ed1180 ffff9a00`15ed1180 ffff9a00`15ed1100 : nt!PopIrpWatchdogBugcheck+0x122 fffffb0b`6f65f1b0 fffff806`0714575b : ffffbe83`19c8e260 00000000`00000000 fffffb0b`6f65f478 00000000`00000000 : nt!PopIrpWatchdog+0xc fffffb0b`6f65f1e0 fffff806`071432c4 : 00000000`00000000 00000000`00000000 00000000`00000000 fffff806`020e93a8 : nt!KiProcessExpiredTimerList+0x1eb fffffb0b`6f65f310 fffff806`0723604e : 00000000`00000876 ffff9a00`15ed1180 ffffbe83`16b5e200 ffffbe83`2927d080 : nt!KiRetireDpcList+0xa94 fffffb0b`6f65f5c0 00000000`00000000 : fffffb0b`6f660000 fffffb0b`6f659000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e 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 --------- New system and new installed Windows 11 x64 from Microsoft site MSI MAG B650 Tomahawk Wifi (latest beta bios) G.Skill 2x16GB 6000MHz CL32 DDR5 Ryzen 7 7700 GTX 1080 Seasonic M12II EVO 750W bronze Storage: Two sata SSDs, Three HDDs 081923-17062-01.dmp 081923-17109-01.dmp 082023-16343-01.dmp 082123-16703-01.dmp 082223-16218-01.dmp
Check the MSI motherboard page for the AMD RAID driver information. Since you don’t have disks in RAID mode, focus on configuring the driver settings. Review any associated files for necessary parameters and follow the instructions provided. If unsure, consult the official documentation or support resources for guidance.
I discovered the problem might be linked to SATA drives' power settings after sleep or entering low power mode. For a few days, I adjusted the power options: 1. "Turn on fast startup" unchecked 2. Set the computer to sleep: never 3. Disable hard disk after use: never Also added two optional driver updates: 1. Advanced Micro Devices Inc. - SecurityDevices - 5.23.0.0 2. Micro-Star INT'L CO., LTD. - System - 1.0.0.12
I’d change the storage setting in BIOS from AHCI to RAID, even if you’re not actively using RAID.
It means storing data across multiple drives in a way that improves reliability and performance.
Following these adjustments for three days without using sleep mode, I didn't encounter any BSODs. The problem seems to be related to the SATA driver not activating correctly after sleep mode.
Sorry for the negative feedback on this entry. I've faced similar problems with my system due to a SATA SSD triggering a BSOD. I'm also encountering the error code 0x9F_3_IMAGE_storahci.sys, indicating an issue with the system hardware. My setup includes an MSI TOMAHWAK B650 WI-FI RYZEN 7 7700X RTX 4070, a 750W PSU from Kingstons Fury 6000MHZ, RAM from WD Blue SA510 (2.5TB), and a WD Black SN770 TB. I'm curious if there are any drawbacks to using RAID for storage.