Whilst your major problem most likely lies in the storage area as mentioned above, the BSOD was something different. It's always risky making a diagnosis based on just one dump, this may just have been a glitch. In any event, unless this BSOD happens again, I would concentrate on the advice from
@SQx.
Your BSOD occurred because a 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: ffff8e8e91409060, Physical Device Object of the stack
Arg3: ffff8c0cd929f110, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffff8e8e9c0554c0, The blocked IRP
The address of the IRP managing the power transition is in argument 4 above, displaying that IRP gives...
Code:
8: kd> !irp ffff8e8e9c0554c0
Irp is active with 4 stacks 3 is current (= 0xffff8e8e9c055620)
No Mdl: No System Buffer: Thread 00000000: Irp stack trace. Pending has been returned
cmd flg cl Device File Completion-Context
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-00000000
Args: 00000000 00000000 00000000 00000000
[IRP_MJ_POWER(16), IRP_MN_WAIT_WAKE(0)]
0 0 ffff8e8e91409060 00000000 fffff8056e14fd00-ffff8c0cdff17138
\Driver\pci dxgkrnl!DpiFdoPowerCompletionRoutine
Args: 00000000 00000000 00000000 00000002
>[IRP_MJ_POWER(16), IRP_MN_SET_POWER(2)]
0 e1 ffff8e8ea61a6030 00000000 fffff80557179330-ffff8e8ea1ef8070 Success Error Cancel pending
\Driver\nvlddmkm nt!PopRequestCompletion
Args: 00051100 00000001 00000001 00000002
[N/A(0), N/A(0)]
0 0 00000000 00000000 00000000-ffff8e8ea1ef8070
Args: 00000000 00000000 00000000 00000000
The drivers on the IRP list (dxgkrnl.sys and nvlddmkm.sys) are graphics drivers, so we know already that this is an issue with the graphics card or driver. The IRP_MJ_POWER(16) and IRP_MN_SET_POWER(2) function calls clearly show that this was a power IRP, as expected from the dump bugcheck.
Argument 2 in the dump gives us the address of the device object that Windows uses to manage the device (that was having the power transistion problem). Displaying that gives...
Code:
8: kd> !devobj ffff8e8e91409060
Device object (ffff8e8e91409060) is for:
Cannot read info offset from nt!ObpInfoMaskToOffset
\Driver\pci DriverObject ffff8e8e8da99720
Current Irp 00000000 RefCount 0 Type 00000023 Flags 00001040
SecurityDescriptor ffffb1857bc79c60 DevExt ffff8e8e914091b0 DevObjExt ffff8e8e914098f8 DevNode ffff8e8e91402c90
ExtensionFlags (0000000000)
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffff8e8e913b4e00 \Driver\ACPI
Device queue is not busy.
The most useful bit of data in there for us is the address of the device node (DevNode). Displaying that gives...
Code:
8: kd> !devnode ffff8e8e91402c90
DevNode 0xffff8e8e91402c90 for PDO 0xffff8e8e91409060
Parent 0xffff8e8e912e3ca0 Sibling 0xffff8e8e914099a0 Child 0xffff8e8ea7a31a20
InstancePath is "PCI\VEN_10DE&DEV_1F07&SUBSYS_21723842&REV_A1\4&30c250c0&0&0000"
ServiceName is "nvlddmkm"
State = DeviceNodeStarted (0x308)
Previous State = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[06] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[05] = DeviceNodeEnumeratePending (0x30c)
StateHistory[04] = DeviceNodeStarted (0x308)
StateHistory[03] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[02] = DeviceNodeEnumeratePending (0x30c)
StateHistory[01] = DeviceNodeStarted (0x308)
StateHistory[00] = DeviceNodeStartPostWork (0x307)
StateHistory[19] = DeviceNodeStartCompletion (0x306)
StateHistory[18] = DeviceNodeStartPending (0x305)
StateHistory[17] = DeviceNodeResourcesAssigned (0x304)
StateHistory[16] = DeviceNodeDriversAdded (0x303)
StateHistory[15] = DeviceNodeInitialized (0x302)
StateHistory[14] = DeviceNodeUninitialized (0x301)
StateHistory[13] = DeviceNodeRemoved (0x312)
StateHistory[12] = DeviceNodeQueryRemoved (0x310)
StateHistory[11] = DeviceNodeStarted (0x308)
StateHistory[10] = DeviceNodeEnumerateCompletion (0x30d)
StateHistory[09] = DeviceNodeEnumeratePending (0x30c)
StateHistory[08] = DeviceNodeStarted (0x308)
StateHistory[07] = DeviceNodeEnumerateCompletion (0x30d)
Flags (0x6c0000f0) DNF_ENUMERATED, DNF_IDS_QUERIED,
DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
CapabilityFlags (0x00600400) WakeFromD0
Unknown flags 0x00600000
The InstancePath value in these gives the VEN & DEV identifier for the device in question. If you
lookup VEN_10DE&DEV_1F07 you'll see it's your RTX 2070, this gells with the IRP data above and confirms that this BSOD was caused by a graphics driver or graphics card that failed to complete a power transition in time...
The version of the graphics driver that you have installed (nvlddmkm.sys) dates from July 2022...
Code:
8: kd> lmDvm nvlddmkm
Browse full module list
start end module name
fffff807`cef90000 fffff807`d1a3e000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_ee20464bb4ac57f4\nvlddmkm.sys
Image name: nvlddmkm.sys
Browse all global symbols functions data
Timestamp: Fri Jul 22 03:04:08 2022 (62D9E978)
CheckSum: 029B8575
ImageSize: 02AAE000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4
Information from resource tables:
The
Nvidia driver website has a more recent driver (546.17) dated 14th November 2023, which (amongst other things) 'fixes a random BSOD'. I suggest that you update to this driver at some point - when you have resolved the storage issue. Be sure to do a clean install (via a Custom (Advanced) install. If the BSODs continue afterwards please run the file collection app again and upload a new zip file.