Error code BSOD DRIVER_POWER_STATE_FAILURE (9f) indicates a driver power state failure.
Error code BSOD DRIVER_POWER_STATE_FAILURE (9f) indicates a driver power state failure.
Mostly new build from back in January 4th. I randomly seem to get this BSOD. I might notice it when I do long sessions of games. Initially happened twice at the beginning of the month then happened again today. Was playing MH Wilds and using the Nvidia app to try and force DLSS 4. I stopped playing and stepped away for a little bit then came back after maybe 10 minutes to a bsod.
*edit* I've tried running scannow/sfc and it didn't come back with any issues. I had a previous 8 year old HDD connected and thought that might be the issue and removed it. The bsods stopped but now its happening again.
*edit 2* This is my first time building with a modular PSU and don't know if maybe there is a potential issue with how the cables are plugged in.
Specs:
Microsoft Windows 10 Pro Version 10.0.19045 Build 19045
MOBO ASRock X870 Pro RS
BIOS Version/Date American Megatrends International, LLC. 3.11, 11/1/2024
GPU: RTX MSI Gaming Trio 3070ti
GPU Driver: 32.0.15.7260
CPU: AMD Ryzen 7 9800X3D 8-Core Processor, 4700 Mhz, 8 Core(s), 16 Logical Processor(s)
RAM: Corsair Vengeance 32gb
https://pcpartpicker.com/product/Jk...6-...m2b6000c30
Hard Drives:
C: WD_BLACK SN770 1TB
D: Samsung SSD 970 EVO Plus 1tb
F: WD_BLACK SN770 2TB
G: Seagate Barracuda 4TB Internal Hard Drive 3.5 Inch SATA 6Gb/s
CD Rom drive.
PSU: Corsair RM850e (2023) 850 W 80+ Gold
Parts from the old build are the GPU, the Samsung SSD, the HDD, and the CD Rom Drive.
Two monitors one 2560x1440 the other 1920x1080
Memory Dump Link:
https://drive.google.com/file/d/1pIx_zrD...sp=sharing
*******************************************************************************
* *
* 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: ffff9e0d10ef9050, Physical Device Object of the stack
Arg3: ffffc70d4227f1d0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff9e0d17c368a0, The blocked IRP
Debugging Details:
------------------
Spoiler:
Memory Debug Info
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 796
Key : Analysis.Elapsed.mSec
Value: 1744
Key : Analysis.IO.Other.Mb
Value: 12
Key : Analysis.IO.Read.Mb
Value: 1
Key : Analysis.IO.Write.Mb
Value: 21
Key : Analysis.Init.CPU.mSec
Value: 453
Key : Analysis.Init.Elapsed.mSec
Value: 11428
Key : Analysis.Memory.CommitPeak.Mb
Value: 94
Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000
Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre
Key : Analysis.Version.Ext
Value: 1.2408.27.1
Key : Bugcheck.Code.KiBugCheckData
Value: 0x9f
Key : Bugcheck.Code.LegacyAPI
Value: 0x9f
Key : Bugcheck.Code.TargetModel
Value: 0x9f
Key : Failure.Bucket
Value: 0x9F_3_IMAGE_storahci.sys
Key : Failure.Hash
Value: {21defffd-4d1f-b62d-8f72-d4892aa9cff8}
Key : Hypervisor.Enlightenments.Value
Value: 0
Key : Hypervisor.Enlightenments.ValueHex
Value: 0
Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 0
Key : Hypervisor.Flags.ApicEnlightened
Value: 0
Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1
Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0
Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0
Key : Hypervisor.Flags.CpuManager
Value: 0
Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 0
Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 0
Key : Hypervisor.Flags.Epf
Value: 0
Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 0
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: 0
Key : Hypervisor.Flags.Phase0InitDone
Value: 0
Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0
Key : Hypervisor.Flags.RootScheduler
Value: 0
Key : Hypervisor.Flags.SynicAvailable
Value: 0
Key : Hypervisor.Flags.UseQpcBias
Value: 0
Key : Hypervisor.Flags.Value
Value: 16908288
Key : Hypervisor.Flags.ValueHex
Value: 1020000
Key : Hypervisor.Flags.VpAssistPage
Value: 0
Key : Hypervisor.Flags.VsmAvailable
Value: 0
Key : Hypervisor.RootFlags.AccessStats
Value: 0
Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 0
Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0
Key : Hypervisor.RootFlags.HostTimelineSync
Value: 0
Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0
Key : Hypervisor.RootFlags.IsHyperV
Value: 0
Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 0
Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 0
Key : Hypervisor.RootFlags.MceEnlightened
Value: 0
Key : Hypervisor.RootFlags.Nested
Value: 0
Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 0
Key : Hypervisor.RootFlags.Value
Value: 0
Key : Hypervisor.RootFlags.ValueHex
Value: 0
Key : SecureKernel.HalpHvciEnabled
Value: 0
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 9f
BUGCHECK_P1: 3
BUGCHECK_P2: ffff9e0d10ef9050
BUGCHECK_P3: ffffc70d4227f1d0
BUGCHECK_P4: ffff9e0d17c368a0
FILE_IN_CAB: MEMORY.DMP
FAULTING_THREAD: ffffb480c184b440
DRVPOWERSTATE_SUBCODE: 3
DRIVER_OBJECT: ffff9e0d10eba060
IMAGE_NAME: storahci.sys
MODULE_NAME: storahci
FAULTING_MODULE: fffff8024d790000 storahci
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
PROCESS_NAME: System
STACK_TEXT:
ffffc70d`4227f5e0 00000000`00000000 : ffffc70d`42280000 ffffc70d`42279000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e
STACK_COMMAND: .process /r /p 0xfffff8024c724a00; .thread 0xffffb480c184b440 ; kb
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_storahci.sys
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {21defffd-4d1f-b62d-8f72-d4892aa9cff8}
Microsoft Windows 10 Pro Version 10.0.19045 Build 19045
Did you regenerate the installer to eliminate a faulty setup? Was the operating system installed in offline mode?
MOBO ASRock X870 Pro RS
BIOS Version/Date American Megatrends International, LLC. 3.11, 11/1/2024
https://www.asrock.com/mb/AMD/X870 Pro RS/index.asp#BIOS
Update BIOS to version 3.20, then reset the CMOS and check if the problem continues.
RAM: Corsair Vengeance 32gb
https://pcpartpicker.com/product/Jk...6-...m2b6000c30
The RAM you selected lacks AMD's E.X.P.O. on the board.
Microsoft Windows 10 Pro Version 10.0.19045 Build 19045
Did you regenerate the installer to eliminate a faulty setup? Was the installation performed without network connection?
MOBO ASRock X870 Pro RS
BIOS Version/Date American Megatrends International, LLC. 3.11, 11/1/2024
https://www.asrock.com/mb/AMD/X870 Pro RS/index.asp#BIOS
Update BIOS to version 3.20, then reset CMOS and check if the problem continues.
RAM: Corsair Vengeance 32gb
https://pcpartpicker.com/product/Jk...6-...m2b6000c30
The RAM you selected lacks AMD's E.X.P.O.
FAILURE_BUCKET_ID: 0x9F_3_IMAGE_storahci.sys
Are you using a RAID configuration?
Components from the previous build include the GPU, Samsung SSD, HDD, and CD-ROM drive.
If the older operating system resided on the Samsung drive, did you erase it before transferring it to your current system? Were all drives removed except the one containing the OS?
Did you recreate the installer to check for a faulty one? Did you set up the OS without using any network connection?
Yes, I built the installer on my previous system using a flash drive and installed it offline so I could create a local user account.
I updated the BIOS to version 3.20, then reset the CMOS, and checked again if the problem continued.
I wasn’t certain whether to use the BIOS since it was just a few days old, intended for a boot issue with x3d CPUs, and I wanted to wait for a non-beta release. I plan to flash it this weekend.
The RAM kit you chose doesn’t include AMD’s E.X.P.O.
That wasn’t something I knew before. Many sources suggest it’s acceptable even if it isn’t the QVL. I’ll consider replacing it soon unless it’s crucial. It’s currently running at 6000MHz.
Are you using a RAID setup?
No, should I be using one? I’m only relying on the other two M.2 drives for game storage and the HDD for media.
If the older OS was stored on the Samsung drive, did you erase it completely before replacing it on your new system? Were all drives removed except the one where the OS was installed?
The Samsung drive was solely used for games, including Steam and GOG titles. The M.2 drives were installed during installation because I didn’t want to complicate things if I didn’t need them.
I noticed in disk D: there’s a 1MB Recovery Partition on the Samsung drive, which I assumed was a tool partition.
I made changes to the bios yesterday without encountering a bsod after 10 hours of operation. Today, when I powered on my computer from shutdown, I observed a generic Kernel-Power error event ID 41. No new memory dump was generated. My computer is connected to an UPS that's only eight months old.
I also noticed numerous errors related to DeviceSetupManager. Metadata staging failed with result 0x80070490 for the container '{0A7A1CBC-AE89-5D7B-997A-89CDAACBEB5D}'. From my research, it appears the issue stems from an outdated link windows usage, which can be resolved by manually editing a register. sfc/scannow still doesn't detect any problems.