What does the "DRIVER_POWER_STATE_FAILURE" BSOD indicate?
What does the "DRIVER_POWER_STATE_FAILURE" BSOD indicate?
Hello. I'm yet again requiring assistance. I tried to do analisys on my own (via WinDbf Preview) but with no success.
CPU: 7800x3d
GPU: Gigabyte 4090 Gaming OC
PSU: NZXT 1200 Gold
Mobo: Asrock b650e Taichi
RAM: G.Skill Trident Z5
Minidump
https://drive.google.com/file/d/1N2RE9c8...sp=sharing
I do understand that there is a driver issue but which exactly is to blame I have to clue. Before that I had crashes because of bad disk but since I unplugged it all was fine.
No OC applied.
Please help me to find the one who breaks and drags the whole system down.
This issue arises when a device does not respond within the required time to a power transition interrupt request. During the dump triage analysis, we identified the device object address of the problematic device and the IRP (interrupt request packet) currently held.
Code:
DRIVER_POWER_STATE_FAILURE (9f)
A software has missed completing a power IRP within a defined period.
Arguments:
Arg1: 0000000000000003 – A device object has been holding an IRP too long
Arg2: ffff9a05aa98e050 – Physical Device Object of the stack
Arg3: fffff807204a5178 – nt!TRIAGE_9F_POWER on Windows 7 and later, otherwise the Functional Device Object of the stack
Arg4: ffff9a05ae9b38a0 – The interrupted IRP
Upon inspecting the blocked IRP, we can determine which driver is not finishing the power transition...
Code:
0: kd> !irp ffff9a05ae9b38a0
The IRP is active across 6 stacks; the current one (3) is 0xffff9a05ae9b3a00.
No Mdl: No System Buffer – Thread 00000000: IRP stack trace.
[No relevant data]
The blocked IRP belongs to the driver responsible for power transitions, which appears to be partmgr.sys – indicating a disk-related failure.
This device object helps pinpoint the specific disk involved...
Code:
0: kd> !devobj ffff9a05aa98e050
The device object (ffff9a05aa98e050) is linked to:
Cannot read info offset from nt!ObpInfoMaskToOffset
DriverObject ffff9a05aa986d30
Current IRP 00000000, RefCount 0, Type 00000007, Flags 00001050
SecurityDescriptor, DeviceExt, DevNode, ExtensionFlags, Characteristics, AttachedDevice.
The device queue is idle.
This output reveals the device node address, which identifies the exact disk...
Code:
0: kd> !devnode ffff9a05aa9e0c20
Device Node 0xffff9a05aa9e0c20 for PDO 0xffff9a05aa98e050
Parent, Sibling, Child, InstancePath, ServiceName, State, etc.
StateHistory records show various transitions and pending states, but the core issue centers on the disk controller—likely the Seagate 1TB HDD.
It may be advisable to replace the drive or use CrystalDiskInfo to assess its SMART status.
Sorry for the delayed response. The report indicates there is just one uncorrectable sector.
smart report.csv
drive.google.com
I believe a single bad sector shouldn't cause a complete system failure, particularly if it isn't the main disk.
EDIT. Another application displayed additional bad sectors.
Screenshot 2023-06-16 222620.png
drive.google.com
The 'Current Pending Sector Count' represents the count of sectors needing a remap to a spare, serving as an important sign of a failing drive. Similarly, the 'Uncorrectable Sector Count' shows the total number of defective sectors. Both values are highlighted with a yellow warning. If this were my drive, I would replace it immediately.