Solved!
Go to SolutionHelp With Memory Dump File Analysis
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 AMD64
Copyright (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 x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff802`5f000000 PsLoadedModuleList = 0xfffff802`5fc133f0
Debug session time: Fri Nov 25 17:01:06.697 2022 (UTC - 8:00)
System Uptime: 0 days 0:29:33.574
Loading Kernel Symbols
...............................................................
................................................................
........................................................
Loading User Symbols
Loading unloaded module list
................
For analysis of this file, run !analyze -v
16: 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 Pnp
subsystem.
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.mSec
Value: 1593
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 4436
Key : Analysis.Init.CPU.mSec
Value: 842
Key : Analysis.Init.Elapsed.mSec
Value: 120552
Key : Analysis.Memory.CommitPeak.Mb
Value: 100
Key : Hardware.BusType
Value: PCI
Key : Hardware.HardwareID
Value: PCI\VEN_8086&DEV_2822&SUBSYS_8703103C&REV_00
Key : WER.OS.Branch
Value: ni_release
Key : WER.OS.Timestamp
Value: 2022-05-06T12:50:00Z
Key : WER.OS.Version
Value: 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!KeBugCheckEx
fffff98a`2b7af6d0 fffff802`5fa92c3c : fffff98a`00000000 fffff98a`2b7af829 ffff8001`26051180 00000000`00000000 : nt!PnpBugcheckPowerTimeout+0x70
fffff98a`2b7af730 fffff802`5f27f5fb : fffff98a`2c66f230 ffff9f8f`26fd8000 fffff98a`2b7af9f8 ffffffff`00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x1c
fffff98a`2b7af760 fffff802`5f28123e : 00000000`00000000 00000000`00000000 00000000`00000000 fffff802`5ad35b88 : nt!KiProcessExpiredTimerList+0x1eb
fffff98a`2b7af890 fffff802`5f424f6e : ffff8001`26051180 ffff8001`26051180 ffff9f8f`26db7040 ffff9f8f`38e3c040 : nt!KiRetireDpcList+0x54e
fffff98a`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
---------
830
0
Posted November 25th, 2022 20:00
Well, as far as the fix ... not sure.
I think the cause is related to disk-signatures and the fact that Windows is not going to allow identical installations of Windows to co-exist in the same system.
People often run into this when cloning (poorly or with random procedures).
I think what it comes down to is the prior disk can not be re-introduced into the system until it is Diskpart-cleaned (sometimes on a separate system). I often just boot and do that with a Macrium Reflect Rescue Drive or a Windows Installer flash-drive.
In retrospect, I think I would have just installed MSFS on 1-tb NVMe C-Drive. Or, maybe bought another for D-Drive. The 256gb-SSD is not really big enough for most peoples C-Drive (now-days 480gb is minimum) as you want it to hold all Windows, and all apps/programs.
Dell Rockstar
Microsoft Windows and Apple iOS Developer (Retired)
- Like many of you, I can appreciate a good game-engine.
- I answer questions here, but I'm not a Dell employee.
- Consider giving posts you like a "thumbs-up"
- Posting models-numbers and software versions speeds trouble-shooting.
- Click "Mark as Accepted Answer" on any post that answers your question best.776
0
Posted November 26th, 2022 22:00
@RodsterB wrote:
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.
Think of Surface Tablets (and Surface Laptop). I think they want everything to online update like a mobile-phone, iPad, your TV ... well, basically everything now-days.
Dell Rockstar
Microsoft Windows and Apple iOS Developer (Retired)
- Like many of you, I can appreciate a good game-engine.
- I answer questions here, but I'm not a Dell employee.
- Consider giving posts you like a "thumbs-up"
- Posting models-numbers and software versions speeds trouble-shooting.
- Click "Mark as Accepted Answer" on any post that answers your question best.760
0
Posted November 27th, 2022 04:00
I see and understand your point and it's well taken and it makes a lot of sense, when it is your product, your hardware. The problem becomes, when it is NOT your product or hardware but you are only involved by means of your software. It created a ton of problems for me by making my system totally unstable, because they forced drivers that were not compatible with my hardware. That's where things tend to get wonky.
A month ago when Dell had their liquidation sale going on the R10's, I bought one on a huge discount. I wanted an all AMD setup with either a 6800 XT or 6900 XT. I forgot to disable the Windows BIOS setting and Windows 11 installed a new BIOS and blew out the motherboard. I tried every trick mentioned in this forum. I tried to reorder one but they were OOS.
That's my problem with Microsoft since Windows 10. Prior to that, you could pick and choose what drivers you wanted installed. Now, that is no longer an option unless you buy Windows Enterprise Edition. There are ways around it but that involves 3rd party software to override Windows Update and disabling WU.
755
0
Posted November 27th, 2022 05:00
I don't believe the issue lies with Microsoft. Anything on Windows update has to be submitted. So if a driver or BIOS update fails and bricks a motherboard, that's on the Company that submitted the files to Microsoft, for not testing them properly prior to release.
750
0
Posted November 27th, 2022 06:00
And that is a valid point you made. However, if the enduser would be allowed to install system drivers at their discretion then it would cause less problems in the long run for someone beyond novice abilities. I remember a situation in the past where an Nvidia WQHL driver caused the GPU to intermittently shut off the fans on the videocard.
I understand security updates but wholesale drivers should be allowed at the end users discretion or at the very least give that person the option. We can do that for you automatically or you the end user can take over.
I can count many times in the last 15-20 years where some certified drivers caused problems or were a downgrade in performance.
On this forum it is widely accepted that if your PC is stable, you might not want to upgrade the BIOS unless it fixes a problem you are experiencing. With Microsoft's approach those rules don't apply.
RodsterB
2 Intern
•
406 Posts
814
0
Posted November 26th, 2022 13:00
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.