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).
