I think that this is most likely a problem with your system drive - the Kingston NVMe SSD. Of the five dumps, four of them point at a RAM issue; there is an UNEXPECTED_STORE_EXCEPTION bugcheck, which is often caused by bad RAM, two SYSTEM_SERVICE_EXCEPTION bugchecks both with 0xC0000006 exception codes indicating a page in error, and a MEMORY_MANAGEMENT bugcheck with an exception indicating corrupted private memory. However, it's the final dump that provides the major clue, this is a DRIVER_POWER_STATE_FAILURE caused by a device taking 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: ffffe60b84949120, Physical Device Object of the stack
Arg3: fffff805331007f8, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe60b84a949a0, The blocked IRP
Argument 2 there is the address of the device object (DevObj) structure that Windows uses to manage the device...
Code:
0: kd> !devobj ffffe60b84949120
Device object (ffffe60b84949120) is for:
Cannot read info offset from nt!ObpInfoMaskToOffset
\Driver\pci DriverObject ffffe60b84850d50
Current Irp 00000000 RefCount 0 Type 00000004 Flags 00001040
SecurityDescriptor ffff800a8956c960 DevExt ffffe60b84949270 DevObjExt ffffe60b84949a38 DevNode ffffe60b84949ae0
ExtensionFlags (0000000000)
Characteristics (0x00000100) FILE_DEVICE_SECURE_OPEN
AttachedDevice (Upper) ffffe60b848dae00 \Driver\ACPI
Device queue is not busy.
The useful bit of data in there for us is the address of the device node (DevNode) which describes the actual device...
Code:
0: kd> !devnode ffffe60b84949ae0
DevNode 0xffffe60b84949ae0 for PDO 0xffffe60b84949120
Parent 0xffffe60b84990a20 Sibling 0000000000 Child 0xffffe60b830ea4a0
InstancePath is "PCI\VEN_2646&DEV_2263&SUBSYS_22632646&REV_03\6&2af5cd96&0&0020020A"
ServiceName is "stornvme"
State = DeviceNodeStarted (0x30a)
Previous State = DeviceNodeEnumerateCompletion (0x30f)
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)
StateHistory[12] = Unknown State (0x0)
StateHistory[11] = Unknown State (0x0)
StateHistory[10] = Unknown State (0x0)
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
UserFlags (0x00000008) DNUF_NOT_DISABLEABLE
CapabilityFlags (0x00002000) WakeFromD3
DisableableDepends = 2 (including self)
The VEN & DEV identifiers in the InstancePath describe the actual device. If you
lookup VEN_2646&DEV_2263 you'll find that it's your Kingston NVMe SSD.
This dump then suggests a problem with your Kingston NVMe, your system drive, which contains the paging file. The other four BSODs likely failed for what appear to be RAM issues because there has been problems paging memory in from your system drive. This is further confirmed by errors in your system log...
Code:
Event[208]
Log Name: System
Source: disk
Date: 2023-11-28T19:04:12.9620000Z
Event ID: 51
Task: N/A
Level: Warning
Opcode: N/A
Keyword: Classic,
User: N/A
User Name: N/A
Computer: ANS-LH343TX
Description:
An error was detected on device \Device\Harddisk2\DR2 during a paging operation.
There are a lot of these errors in your log, so I think you should look more closely at that Kingston NVMe SSD. Kingston have their own
SSD Manager tool which sadly doesn't contain a diagnostic tool. You can check the drive health with it though. Also use the tool to look for a firmware update for the drive.
On common issue I've seen with M.2 drives is that if they're not seated properly you see all sorts of niggly problems, so I would also suggest removing the drive and then re-seating it firmly.
