It turns out RAID was causing the problem as it was trying to download drivers that were not compatible with my Omen 30L. I disabled it in the BIOS and switched to AHCI instead. Problem solved. I'm puzzled how Microsoft convinced the PC builders to force install drivers on their systems. Some on this forum have reported ruined motherboards because of Microsoft's Windows Updater.
Based on the analysis it looks like it's related to Intel ME driver. Btw this is on my HP Omen 30L Windows 11 which is producing BSOD's and they occur when Windows Update is downloading drivers. IIRC the Intel SCSI driver fails to install. I restart the PC and it sits for 15+ minutes displaying Restarting. After the timeout it goes into BSOD.  The dump file is 2.6GB so I am going to copy the contents at the point where it detected an error. It seems it is either a driver or motherboard problem, although i'm not too confident on that. Back story: I swapped a small secondary NVME on this PC and moved it to the primary slot because it was 250GB and the primary NVME was 1TB (Microsoft Flight Simulator). I wanted the 250GB (OS) and the 1TB for Flight Simulator. Somehow the 250GB NVME unexpectedly quit/failed. It's not recognized in Windows installation setup, BIOS or in Windows, disk mgr. I tested the 250GB NVME on another system and the same result, dead, so it follows the NVME. The 1TB NVME works in either slot, so the slots appear to be good. I ran internal diagnostics, and everything passed (extensive testing).  I downloaded the Windows SDK debugging tool. -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\RodsterB\Desktop\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available; User address space may not be available. Dump completed successfully, progress percentage: 100 Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 22621 MP (20 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 22621.1.amd64fre.ni_release.220506-1250Machine Name:Kernel base = 0xfffff802`5f000000 PsLoadedModuleList = 0xfffff802`5fc133f0Debug session time: Fri Nov 25 17:01:06.697 2022 (UTC - 8:00)System Uptime: 0 days 0:29:33.574Loading Kernel Symbols.......................................................................................................................................................................................Loading User Symbols Loading unloaded module list................For analysis of this file, run !analyze -v16: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ******************************************************************************** DRIVER_POWER_STATE_FAILURE (9f)A driver has failed to complete a power IRP within a specific time.Arguments:Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnpsubsystem.Arg2: 000000000000012c, Timeout in seconds.Arg3: ffff9f8f26d3b040, The thread currently holding on to the Pnp lock.Arg4: fffff98a2b7af700, nt!TRIAGE_9F_PNP on Win7 and higher Debugging Details:------------------ Implicit thread is now ffff9f8f`26d3b040 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSecValue: 1593 Key : Analysis.DebugAnalysisManagerValue: Create Key : Analysis.Elapsed.mSecValue: 4436 Key : Analysis.Init.CPU.mSecValue: 842 Key : Analysis.Init.Elapsed.mSecValue: 120552 Key : Analysis.Memory.CommitPeak.MbValue: 100 Key : Hardware.BusTypeValue: PCI Key : Hardware.HardwareIDValue: PCI\VEN_8086&DEV_2822&SUBSYS_8703103C&REV_00 Key : WER.OS.BranchValue: ni_release Key : WER.OS.TimestampValue: 2022-05-06T12:50:00Z Key : WER.OS.VersionValue: 10.0.22621.1 FILE_IN_CAB: MEMORY.DMP TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x1800 BUGCHECK_CODE: 9f BUGCHECK_P1: 4 BUGCHECK_P2: 12c BUGCHECK_P3: ffff9f8f26d3b040 BUGCHECK_P4: fffff98a2b7af700 DRVPOWERSTATE_SUBCODE: 4 HARDWARE_ID_BUS_TYPE: PCI HARDWARE_VENDOR_ID: VEN_8086 HARDWARE_DEVICE_ID: DEV_2822 HARDWARE_SUBSYS_ID: SUBSYS_8703103C HARDWARE_REV_ID: REV_00 HARDWARE_ID: PCI\VEN_8086&DEV_2822&SUBSYS_8703103C&REV_00 IMAGE_NAME: pci.sys MODULE_NAME: pci FAULTING_MODULE: fffff80261470000 pci BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: fffff98a`2b7af6c8 fffff802`5f54e0d8 : 00000000`0000009f 00000000`00000004 00000000`0000012c ffff9f8f`26d3b040 : nt!KeBugCheckExfffff98a`2b7af6d0 fffff802`5fa92c3c : fffff98a`00000000 fffff98a`2b7af829 ffff8001`26051180 00000000`00000000 : nt!PnpBugcheckPowerTimeout+0x70fffff98a`2b7af730 fffff802`5f27f5fb : fffff98a`2c66f230 ffff9f8f`26fd8000 fffff98a`2b7af9f8 ffffffff`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x1cfffff98a`2b7af760 fffff802`5f28123e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`5ad35b88 : nt!KiProcessExpiredTimerList+0x1ebfffff98a`2b7af890 fffff802`5f424f6e : ffff8001`26051180 ffff8001`26051180 ffff9f8f`26db7040 ffff9f8f`38e3c040 : nt!KiRetireDpcList+0x54efffff98a`2b7afb40 00000000`00000000 : fffff98a`2b7b0000 fffff98a`2b7a9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e IMAGE_VERSION: 10.0.22621.457 STACK_COMMAND: .cxr; .ecxr ; kb FAILURE_BUCKET_ID: 0x9F_4_PCI_iaStorAVC_IMAGE_pci.sys OS_VERSION: 10.0.22621.1 BUILDLAB_STR: ni_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {0f9073da-e0c1-bb25-bd2e-1085722d6131} Followup: MachineOwner---------
Help With Memory Dump File Analysis