driver_power_state_failure nt!TRIAGE_9F_POWER on Win11

samtoryu · Sep 7, 2023

Hi everyone, i'm new. Someone on Microsoft support website suggested me to post my problem here. I got the V2 log on onedrive, here's the link: https://1drv.ms/f/s!Ap8M80K9KM43jVb7...l2Naw?e=dDcZ62

My new PC keeps restarting for no reason and giving me blue screens. I checked with event viewer and analyzed the minidump file with winDBG. I got this far, some say that is most probably an issue with the storage devices or some chipset not working properly but I can't figure out the problem by myself

Thanks from the bottom of my heart to anyone who will help me in this process, you are a good person.

Have a good day, you all!

glasskuter · Sep 7, 2023

samtoryu said:
My new PC keeps restarting for no reason and giving me blue screens.

It would be helpful if you would completely fill out your computer specs in your forum profile so we can know what hardware you are working with. If it is an OEM machine give make and model, also version and build of windows. Click on MY COMPUTER below for an example or for a self build complete all entries.

ubuysa · Sep 7, 2023

Hello and welcome to the forum!

Whoever pointed you at the chipset drivers and/or a storage drive is right. All the dumps are identical, they are all DRIVER_POWER_STATE_FAILURE bugcheck indicating that a device has held a power IRP for too long. An IRP is an Interrupt Request Packet and they are used (in this particular case) to represent a power transition request. Because IRPs are a system resource they can't be held for too long. What's happened here is that a power transition request for a device took too long and the IRP timed out.

In the dump we can see the IRP that's been held for too long...

Code:

14: kd> !irp ffffc704985a77e0
Irp is active with 6 stacks 3 is current (= 0xffffc704985a7940)
 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 ffffc704945ae050 00000000 fffff806698b8510-ffffc704988aa730 Success Error Cancel pending
           \Driver\storahci    CLASSPNP!ClasspPowerUpCompletion
            Args: 00000000 00000001 00000001 00000000
 [IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
            0 e1 ffffc704988aa1f0 00000000 fffff8066871ec60-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 ffffc704986e98d0 00000000 fffff80664927760-ffffc70498863228 Success Error Cancel pending
           \Driver\partmgr    nt!PopRequestCompletion
            Args: 00000000 00000001 00000001 00000000
 [N/A(0), N/A(0)]
            0  0 00000000 00000000 00000000-ffffc70498863228

            Args: 00000000 00000000 00000000 00000000

At the bottom of that output you can see the driver that's holding the IRP, it's partmgr.sys. This is the Windows driver that manages the use of storage drive partitions, so we know that there has been an issue with a storage drive. We can also see the storage drive in question in the dump, though we needs to follow a chain. The dump gives us the device object address, this is the kernel representation of the device...

Code:

14: kd> !devobj ffffc704945ae050
Device object (ffffc704945ae050) is for:
 Cannot read info offset from nt!ObpInfoMaskToOffset
 \Driver\storahci DriverObject ffffc70494515ca0
Current Irp 00000000 RefCount 0 Type 00000007 Flags 00001050
SecurityDescriptor ffff8008c6afd420 DevExt ffffc704945ae1a0 DevObjExt ffffc704945af3a0 DevNode ffffc704944c64a0
ExtensionFlags (0000000000)
Characteristics (0x00000180)  FILE_AUTOGENERATED_DEVICE_NAME, FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffc704988aa1f0 \Driver\disk
Device queue is not busy.

The main item of information we want here is the device node address (the DevNode), this is the representation of the actual device...

Code:

14: kd> !devnode ffffc704944c64a0
DevNode 0xffffc704944c64a0 for PDO 0xffffc704945ae050
  Parent 0xffffc704944d7a20   Sibling 0000000000   Child 0000000000
  InstancePath is "SCSI\Disk&Ven_Samsung&Prod_SSD_860_QVO_1TB\7&35f8e2bf&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 (0x00002180)  SilentInstall, RawDeviceOK,
                                WakeFromD3

You can see clearly that the device in question is the Samsung 860 QVO NVMe SSD, your D: drive.

There seems to be a problem with power transitions on that Samsung drive. I would suggest you download Samsung Magician and use that to perform a full diagnostic test on the drive. Also use Magician to look for firmware and/or driver updates for that drive.

Also download the Intel Driver & Support Assistant and use that to look for driver updates for all your Intel devices (which will include the chipset drivers).

zbook · Sep 7, 2023

There were 5 collected mini dump files.

All BSOD were bugcheck 9F and were caused by problems related to the Samsung disk drive.

SCSI\Disk&Ven_Samsung&Prod_SSD_860_QVO_1TB

1) Run Tuneup plus > post a share link into this thread

https://www.tenforums.com/attachments/bsod-crashes-debugging/360139d1645183596-batch-files-use-bsod-debugging-tuneup_plus_log.zip

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

2) If possible, detach this drive and monitor the computer for stability /instability.

3) Open administrative command prompt and copy and paste:

msdt.exe -id BITSDiagnostic

msdt.exe -id DeviceDiagnostic

msdt.exe -id WindowsUpdateDiagnostic

For each Microsoft Windows troubleshooter click view detailed information > post images or share links into this thread.

4) Run:
Reset_Reregister_Windows_Update_Components_for_Windows11.bat

https://www.elevenforum.com/attachments/reset_reregister_windows_update_components_for_windows11-bat.17838/?hash=880cbfb2a5146d8063c69bfdbe10e1c7

Reset Windows Update in Windows 11 Tutorial

This tutorial will show you how to completely reset Windows Update components and policies to default in Windows 10 and Windows 11. Windows Update keeps Windows 11 updated by automatically downloading and installing the latest updates, drivers, and hotfixes released by Microsoft. Sometimes you...

www.elevenforum.com

Code:

------------------------
Disk & DVD/CD-ROM Drives
------------------------
      Drive: C:
 Free Space: 710.1 GB
Total Space: 953.1 GB
File System: NTFS
      Model: CT1000P5PSSD8

      Drive: D:
 Free Space: 952.4 GB
Total Space: 953.9 GB
File System: NTFS
      Model: Samsung SSD 860 QVO 1TB

samtoryu · Sep 9, 2023

Thank you folks, I do really appreciate you spending some of your time helping me! It seems that all the BSODs were indeed caused by the Samsung QVO Sata SSD! Thanks to you my PC ran for 24+ hours without any blue screen.
@ubuysa I ran some diagnostics on the SSD and it all seems fine with it :/
Could it be that the SSD is healthy and the problem was with a corrupted SATA cable?
Thanks again you all, you were very helpful, have a good good day :)

ubuysa · Sep 9, 2023

A bad SATA cable certainly could be the problem. What makes you ask?

samtoryu · Sep 9, 2023

I dunno, since the SSD has no apparent problem, maybe the problem is with the cables. I'll try with another cable or another port as soon as I can get my hands on one of those.

zbook · Sep 9, 2023

Was the computer tested without the attached drive?

There were no drive test images or share links posted.

Which drive tests were performed?

Was Samsung Magician supported or unsupported for this drive?

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

samtoryu · Sep 13, 2023

Hi everyone, here I am again, unfortunately. It seems that the SSD wasn-t the only problem with my PC. I got another blue screen just minutes ago on restarting. It was yet another time a driver power state failure. Faulty SSD is still detached, so that cannot be the problem. I've got the new V2 logger analisys on one drive: DESKTOP-(2023-09-13_18-21-26).zip

Do you guys see anything strange? Thanks for the helping hand

zbook · Sep 13, 2023

1) Please run:

a) https://www.tenforums.com/attachmen...-files-use-bsod-debugging-tuneup_plus_log.bat

b) https://www.tenforums.com/attachmen...od-debugging-gather_additional_dump_files.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Post share links into this thread.

2) Create a new restore point:

Create System Restore Point in Windows 11 Tutorial

This tutorial will show you how to manually create a restore point in Windows 11. Turning on system protection for a drive allows System Restore to include the drive when restore points are created so you can undo undesired system changes by reverting to a previous point in time. System...

www.elevenforum.com

3) Read this link on Windows Driver Verifier (WDV):

Enable and Disable Driver Verifier in Windows 10

4) Learn the methods to recover from using the tool by booting into safe mode and running one or more of these commands:

verifier /reset

verifier/bootmode resetonbootfail

5) If there is no immediate BSOD then open Administrative command prompt and copy and paste:

verifier /querysettings

Post a share link into this thread using one drive, drop box, or google drive.

6) For any BSOD post a new V2 share link into the newest post

7) Plan to run WDV for 24 - 48 hours with various customized test settings

samtoryu · Sep 15, 2023

Hi @zbook, thanks for answering! I've run the batch files, I got the results on onedrive. Here: MYPC v2 log

For WDV, my first question was: do you suggest restarting the PC after WDV is enabled since that is when the system gives a BSOD or just let it run for a while?
But then I read the instruction thread for it and it seems I need to restart the PC and only after rebooting the WDV will start working. My question now is, if on reboot I get a blue screen, will the WDV start anyway or not? Will it store the dump anyway even if it gets the blue screen before it starts running? Thanks for your time! Have a good day :)

zbook · Sep 15, 2023

Code:

There is a system repair pending which requires reboot to complete.  
Restart Windows and run sfc again.

Please reboot the computer then:

1) Run Tuneup plus

2) Run V2 after completing 1)

Post new share links.

samtoryu · Sep 15, 2023

Ok, here is the new link for onedrive: MYPC v2 log

PS: No BSOD on reboot, twice. Tell me what you think. Thank you very much as always.

Katana1074 · Sep 15, 2023

Hi there, I Have an x670e Taichi, I Had no end of bother with this, the fix is an easy one:

you need to install Asmedia 1061 drivers, and change AHCI Link Power management to HIPM

https://www.reddit.com/r/ASRock/comments/10a0dkw

this will cure the problem your having

Regards

zbook · Sep 15, 2023

Today is 09/15.

The last reported BSOD was on 09/13.

1) Please run using ACP

msdt.exe -id BITSDiagnostic
msdt.exe -id WindowsUpdateDiagnostic
msdt.exe -id DeviceDiagnostic

If available click view detailed information > post images or share links into this thread

2) Run:

Download .NET Framework Repair Tool from Official Microsoft Download Center

This tool detects and tries to fix some frequently occurring issues with the setup of Microsoft .NET Framework or with updates to the Microsoft .NET Framework.

www.microsoft.com

Code:

Event[5088]
  Log Name: System
  Source: Microsoft-Windows-WindowsUpdateClient
  Date: 2023-09-15T21:06:00.2400000Z
  Event ID: 20
  Task: Windows Update Agent
  Level: Error s
  Opcode: Installation
  Keyword: Installation,Failure,
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-QT7JV9G
  Description:
Installation Failure: Windows failed to install the following update with error 0x80070490: 2023-09 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11, version 22H2 for x64 (KB5031217).

ubuysa · Sep 16, 2023

Sorry for not getting back earlier. The most recent BSOD on 13th Sept is a 0x9F again, but this time with an argument 1 value 0f 0x4 - these can only be analysed with a kernel dump. If you've had no BSODs since that one please upload the file C:\Windows\Memory.dump to the cloud with a link to it here.

zbook · Sep 16, 2023

If the computer has any new BSOD or unexpected shutdowns and restarts a memory dump unfortunately may be required for more than one crash.
In addition, memory dumps come in very varied sizes.

There was a recent thread where x bluerobot requested a memory dump.
The OP spent time uploading the 32 GB file.
Yet nobody debugged the file.

In contrast, WDV is more likely to find a misbehaving driver.
And mini dump files are easier to upload and download.

See post #10 for using WDV.

ubuysa · Sep 16, 2023

I advised the OP not to upload the complete memory dump and @x BlueRobot agreed in the next post.

I'll say it again, the 0x9F 0x4 can ONLY be analysed with a kernel dump. If you think you know different then go for it.

zbook · Sep 16, 2023

There were threads in which there were comments that BSOD 9F and 133 can only be analyzed with a kernel dump.

If the computers only produced large dump files would you not be able troubleshoot?

Memory dumps if available are additional troubleshooting files.

Most often the computers with these crashes can be troubleshooted without memory dump files.

ubuysa · Sep 16, 2023

Actually what wrote was that 0x9F with an argument 1 value of 0x4 and a 0x133 with an argument 1 value of 0x1 can only be analysed with a kernel dump. These are special cases.

I would be able to analyse a complete memory dump, if I were prepared to download a 32GB file. Which I'm not.

BSODs produce dump files for a reason. If you are able to properly troubleshoot 0x9F and/or 0x133 BSODs without looking at the dump I'd be interested to learn how.