System keeps bluescreening with DRIVER_POWER_STATE_FAILURE 0x0000009f

Although I'm working in IT I am hitting a wall with the computer I built at home. I'm getting bluescreens randomly, while gaming, while browsing, while AFK. My drivers are up to date and I have checked WinDbg already, but I am not sure what to do with that information presented in there. I can't seem to figure it out on my own and would appreciate some help.

System Specs section is filled in on my profile page.

Windows version:
Windows 11 Version 2382 (OS Build 22631.2428)

Link to logfiles:
https://1drv.ms/u/s!Aqysyy3RzzOogkFj...5H4YZ?e=wX3sVw

The problem drive is the WD Black 2TB HDD. We can see this from the dumps, which are all identical. The 0x9F (DRIVER_POWER_STATE_FAILURE) indicates that a hardware device took too long to complete a power transition...

Code:

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: ffffab01b1c25050, Physical Device Object of the stack
Arg3: ffffbd80b7997178, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffab01b5cce9f0, The blocked IRP

The IRP, whose address is in argument 4 and which manages the power transition, shows that it's a disk device...

Code:

15: kd> !irp ffffab01b5cce9f0
Irp is active with 6 stacks 3 is current (= 0xffffab01b5cceb50)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffab01b1c25050 00000000 fffff804262c8510-ffffab01b5c6e5c0 Success Error Cancel pending
	       \Driver\storahci	CLASSPNP!ClasspPowerUpCompletion
			Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffab01b5c6e080 00000000 fffff8042519ec60-00000000 Success Error Cancel pending
	       \Driver\disk	partmgr!PmPowerCompletion
			Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffab01b5aca8d0 00000000 fffff80422cb5450-ffffab01b5c66208 Success Error Cancel pending
	       \Driver\partmgr	nt!PopRequestCompletion
			Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffab01b5c66208    

			Args: 00000000 00000000 00000000 00000000

Note that the Windows drivers storachi.sys, disk.sys and partmgr.sys are all on the IRP queue and all are trying to change the power state (IRP_MN_SET_POWER). It's the driver at the bottom (partmgr.sys) that's holding everything up.

Argument 2 in the bugcheck is the address of the device object, which identifies the Windows management structure for the device having power transition problems...

Code:

15: kd> !devobj ffffab01b1c25050
Device object (ffffab01b1c25050) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\storahci DriverObject ffffab01b1be28a0
Current Irp 00000000 RefCount 0 Type 00000007 Flags 00001050
SecurityDescriptor ffffc10c01416c60 DevExt ffffab01b1c251a0 DevObjExt ffffab01b1c263a0 DevNode ffffab01b1c48c20 
ExtensionFlags (0000000000)  
Characteristics (0x00000180)  FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffab01b5c6e080 \Driver\disk
Device queue is not busy.

The key bit of information in there that's useful for us is the device node address (DevNode), this describes the actual physical device...

Code:

15: kd> !devnode ffffab01b1c48c20
DevNode 0xffffab01b1c48c20 for PDO 0xffffab01b1c25050
  Parent 0xffffab01b19bba20   Sibling 0000000000   Child 0000000000   
  InstancePath is "SCSI\Disk&Ven_WDC&Prod_WD2003FZEX-00SRL\7&3611b6d6&0&010000"
  ServiceName is "disk"
  State = DeviceNodeStarted (0x30a)
  Previous State = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[12] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[11] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[10] = DeviceNodeStarted (0x30a)
  StateHistory[09] = DeviceNodeEnumerateCompletion (0x30f)
  StateHistory[08] = DeviceNodeEnumeratePending (0x30e)
  StateHistory[07] = DeviceNodeStarted (0x30a)
  StateHistory[06] = DeviceNodeStartPostWork (0x309)
  StateHistory[05] = DeviceNodeStartCompletion (0x308)
  StateHistory[04] = DeviceNodeStartPending (0x307)
  StateHistory[03] = DeviceNodeResourcesAssigned (0x306)
  StateHistory[02] = DeviceNodeDriversAdded (0x305)
  StateHistory[01] = DeviceNodeInitialized (0x304)
  StateHistory[00] = DeviceNodeUninitialized (0x301)
  StateHistory[19] = Unknown State (0x0)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  StateHistory[15] = Unknown State (0x0)
  StateHistory[14] = Unknown State (0x0)
  StateHistory[13] = Unknown State (0x0)
  Flags (0x24000130)  DNF_ENUMERATED, DNF_IDS_QUERIED, 
                      DNF_NO_RESOURCE_REQUIRED, DNF_NO_LOWER_DEVICE_FILTERS, 
                      DNF_NO_UPPER_DEVICE_FILTERS
  CapabilityFlags (0x00402180)  SilentInstall, RawDeviceOK, 
                                WakeFromD3
                                Unknown flags 0x00400000

The 'InstancePath' there shows the actual device - WD2003FZEX-00SRL - if you look that up it's a WD Black 2TB HDD. Note also from the 'CapabilityFlags' that it supports the D3 (low power state), so it should be able to handle transitioning from D3 to D0 (full power).

I don't think that this is necessarily a problem with the disk surface or data, it's a disk controller problem (because it's failing a power transition). One workaround would be to change the hard disk power off time in Power & Sleep Settings to 0, so that the drives never power down.

If you're experiencing many of these BSODs when gaming then perhaps it's a power issue? What PSU do you have? I would also check that the SATA power cables are fully home at both ends. It might also be worth trying a different HDD in there....

Please make sure that all drives are tested as per post #2.

Thanks ubuysa and zbook, very insightful answers and more than I could have hoped for. Now I know which device is causing the trouble. Since this error occurs on a change in power state, this might also explain the behavior where sometimes, my computer powers down completely (no bluescreen, no minidump). Although this only happened two times so far, more often the bluescreen happens with the 0x9F error code. Just wondering if that might be the same root cause of the drive (or drive controller) acting up.

Yesterday I have already done the following.
- in device manager, uninstall all "Standard SATA AHCI Controller" devices utilizing the storahci.sys driver, reboot, so they get initialized fresh
- opened the case and replugged every cable and card besides CPU
- changed to another power strip

My PSU is:
be quiet! STRAIGHT POWER 11 750W black 80PLUS Platinum BN307

Will keep you updated.

The problematic drive (WDC WD2003FZEX-00SRLA0) was identified using V2 log files.

This is an ideal opportunity to test all drives.

Once all drives are tested you can detach the problematic drive.

It would be useful for rule in / rule out by:

a) Sea Tools
b) HD Tune
c) chkdsk /b /v
d) HD Sentinel
e) computer stability without an attached drive
etc.

Disk checks looks good

Code:

Chkdsk /b /v C:
The type of the file system is NTFS.
Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) y

This volume will be checked the next time the system restarts.

Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  320256 file records processed.                                                         
File verification completed.
 Phase duration (File record verification): 2.20 seconds.
  15786 large file records processed.                                    
 Phase duration (Orphan file record recovery): 6.45 milliseconds.
  0 bad file records processed.                                      
 Phase duration (Bad file record checking): 1.69 milliseconds.

Stage 2: Examining file name linkage ...
  215 reparse records processed.                                       
  448580 index entries processed.                                                        
Index verification completed.
 Phase duration (Index verification): 4.38 seconds.
  0 unindexed files scanned.                                         
 Phase duration (Orphan reconnection): 174.01 milliseconds.
  0 unindexed files recovered to lost and found.                     
 Phase duration (Orphan recovery to lost and found): 46.18 milliseconds.
  215 reparse records processed.                                       
 Phase duration (Reparse point and Object ID verification): 4.77 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 254 unused index entries from index $SII of file 0x9.
Cleaning up 254 unused index entries from index $SDH of file 0x9.
Cleaning up 254 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 21.57 milliseconds.
  64163 data files processed.                                            
 Phase duration (Data attribute verification): 1.73 milliseconds.
CHKDSK is verifying Usn Journal...
  34612152 USN bytes processed.                                                            
Usn Journal verification completed.
 Phase duration (USN journal verification): 62.69 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  320240 files processed.                                                                
File data verification completed.
 Phase duration (User file recovery): 7.55 minutes.

Stage 5: Looking for bad, free clusters ...
  130375033 free clusters processed.                                                        
Free space verification is complete.
 Phase duration (Free space recovery): 54.17 seconds.

Windows has scanned the file system and found no problems.
No further action is required.

 975950847 KB total disk space.
 453845412 KB in 219964 files.
    148980 KB in 64164 indexes.
         0 KB in bad sectors.
    456323 KB in use by the system.
     65536 KB occupied by the log file.
 521500132 KB available on disk.

      4096 bytes in each allocation unit.
 243987711 total allocation units on disk.
 130375033 allocation units available on disk.
Total duration: 8.57 minutes (514428 ms).

Internal Info:
00 e3 04 00 4b 55 04 00 f1 8c 07 00 00 00 00 00  ....KU..........
77 00 00 00 60 00 00 00 00 00 00 00 00 00 00 00  w...`...........


C:\Windows\System32>Chkdsk /b /v D:
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is Data.

Stage 1: Examining basic file system structure ...
  188160 file records processed.
File verification completed.
 Phase duration (File record verification): 1.17 seconds.
  50 large file records processed.
 Phase duration (Orphan file record recovery): 0.27 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.22 milliseconds.

Stage 2: Examining file name linkage ...
  482 reparse records processed.
  193350 index entries processed.
Index verification completed.
 Phase duration (Index verification): 8.34 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 7.90 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 1.30 milliseconds.
  482 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 2.08 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 65 unused index entries from index $SII of file 9.
Cleaning up 65 unused index entries from index $SDH of file 9.
Cleaning up 65 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 22.41 milliseconds.
  2596 data files processed.
 Phase duration (Data attribute verification): 0.19 milliseconds.
CHKDSK is verifying Usn Journal...
  40748416 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 550.66 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  188144 files processed.
File data verification completed.
 Phase duration (User file recovery): 30.23 minutes.

Stage 5: Looking for bad, free clusters ...
  412716851 free clusters processed.
Free space verification is complete.
 Phase duration (Free space recovery): 2.98 hours.

Windows has scanned the file system and found no problems.
No further action is required.

1953497087 KB total disk space.
 302260640 KB in 42899 files.
     15464 KB in 2597 indexes.
         0 KB in bad sectors.
    353575 KB in use by the system.
     65536 KB occupied by the log file.
1650867408 KB available on disk.

      4096 bytes in each allocation unit.
 488374271 total allocation units on disk.
 412716852 allocation units available on disk.
Total duration: 3.49 hours (12588259 ms).


C:\Windows\System32>Chkdsk /b /v E:
The type of the file system is NTFS.
Volume label is BACKUP.

Stage 1: Examining basic file system structure ...
  45568 file records processed.
File verification completed.
 Phase duration (File record verification): 456.86 milliseconds.
  1 large file records processed.
 Phase duration (Orphan file record recovery): 0.30 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.21 milliseconds.

Stage 2: Examining file name linkage ...
  2 reparse records processed.
  50754 index entries processed.
Index verification completed.
 Phase duration (Index verification): 12.25 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 2.40 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.57 milliseconds.
  2 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 0.60 milliseconds.

Stage 3: Examining security descriptors ...
Cleaning up 5 unused index entries from index $SII of file 9.
Cleaning up 5 unused index entries from index $SDH of file 9.
Cleaning up 5 unused security descriptors.
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 26.51 milliseconds.
  2593 data files processed.
 Phase duration (Data attribute verification): 0.38 milliseconds.

Stage 4: Looking for bad clusters in user file data ...
  45552 files processed.
File data verification completed.
 Phase duration (User file recovery): 52.08 minutes.

Stage 5: Looking for bad, free clusters ...
  168584593 free clusters processed.
Free space verification is complete.
 Phase duration (Free space recovery): 2.48 hours.

Windows has scanned the file system and found no problems.
No further action is required.

 976751968 KB total disk space.
 302259296 KB in 42898 files.
     12960 KB in 2595 indexes.
         0 KB in bad sectors.
    141336 KB in use by the system.
     65536 KB occupied by the log file.
 674338376 KB available on disk.

      4096 bytes in each allocation unit.
 244187992 total allocation units on disk.
 168584594 allocation units available on disk.
Total duration: 3.35 hours (12094364 ms).

Drive file systems C,D, and E displayed cleaning.

When available update the progress with the steps in post #2.

How fragmented is that WD Black? We're looking for something that would stop it powering up (it's a 0x9F BSOD remember).

Long generic run of the SeaTools completed successful for the two HDDs.
Ran the repair commands as well (shown below).

Maybe the problem is already fixed? the PC was running for very many hours during the night for the disk tests and did not bluescreen during that, which it might have done a week ago. I would wait if it happens again.

Code:

C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

C:\Windows\System32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Image Version: 10.0.22631.2428

[==========================100.0%==========================] The component store is repairable.
The operation completed successfully.

C:\Windows\System32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Image Version: 10.0.22631.2428

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\System32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\System32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows.

Stage 1: Examining basic file system structure ...
  422144 file records processed.
File verification completed.
 Phase duration (File record verification): 2.63 seconds.
  15787 large file records processed.
 Phase duration (Orphan file record recovery): 7.24 milliseconds.
  0 bad file records processed.
 Phase duration (Bad file record checking): 0.51 milliseconds.

Stage 2: Examining file name linkage ...
  213 reparse records processed.
  556052 index entries processed.
Index verification completed.
 Phase duration (Index verification): 5.08 seconds.
  0 unindexed files scanned.
 Phase duration (Orphan reconnection): 250.24 milliseconds.
  0 unindexed files recovered to lost and found.
 Phase duration (Orphan recovery to lost and found): 0.45 milliseconds.
  213 reparse records processed.
 Phase duration (Reparse point and Object ID verification): 2.07 milliseconds.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
 Phase duration (Security descriptor verification): 19.94 milliseconds.
  66955 data files processed.
 Phase duration (Data attribute verification): 0.26 milliseconds.
CHKDSK is verifying Usn Journal...
  39464424 USN bytes processed.
Usn Journal verification completed.
 Phase duration (USN journal verification): 76.25 milliseconds.

Windows has scanned the file system and found no problems.
No further action is required.

 975950847 KB total disk space.
 458372636 KB in 226631 files.
    156728 KB in 66956 indexes.
         0 KB in bad sectors.
    563351 KB in use by the system.
     65536 KB occupied by the log file.
 516858132 KB available on disk.

      4096 bytes in each allocation unit.
 243987711 total allocation units on disk.
 129214533 allocation units available on disk.
Total duration: 8.08 seconds (8085 ms).

C:\Windows\System32>wmic recoveros get autoreboot
AutoReboot
TRUE


C:\Windows\System32>wmic recoveros get DebugInfoType
DebugInfoType
1


C:\Windows\System32>wmic pagefile list /format:list


AllocatedBaseSize=32768
CurrentUsage=0
Description=C:\pagefile.sys
InstallDate=20230708113447.484165+120
Name=C:\pagefile.sys
PeakUsage=1
Status=
TempPageFile=FALSE




C:\Windows\System32>wmic Computersystem where name="%computername%" get AutomaticManagedPagefile
AutomaticManagedPagefile
TRUE


C:\Windows\System32>bcdedit /enum {badmemory}

RAM Defects
-----------
identifier              {badmemory}