Question Need Help Figuring Out This Dump File?

Toggle sidebar Toggle sidebar
H

Heat_Fan89

Reputable
Jul 13, 2020
544
294
5,290
Based on the analysis it looks like it's related to Intel ME driver. At least that's what a Google search mentioned. Btw this is on my HP Omen 30L i9 10850K, WD 1TB NVME, 32GB 3200Mhz RAM, RTX 3080, Wifi 6. It's both Windows 10 and 11 on a fresh install which is producing BSOD's and they occur when Windows Update is downloading Intel drivers. IIRC the Intel SCSI driver fails to install so I am wondering if that also could be the problem. I restart and update 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.

Any insights would be much appreciated !
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Microsoft (R) Windows Debugger Version 10.0.22621.755 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\Heat_Fan89\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 = 0xfffff8025f000000 PsLoadedModuleList = 0xfffff8025fc133f0
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 ffff9f8f26d3b040 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: fffff98a2b7af6c8 fffff8025f54e0d8 : 000000000000009f 0000000000000004 000000000000012c ffff9f8f26d3b040 : nt!KeBugCheckEx fffff98a2b7af6d0 fffff8025fa92c3c : fffff98a00000000 fffff98a2b7af829 ffff800126051180 0000000000000000 : nt!PnpBugcheckPowerTimeout+0x70 fffff98a2b7af730 fffff8025f27f5fb : fffff98a2c66f230 ffff9f8f26fd8000 fffff98a2b7af9f8 ffffffff00000002 : nt!PopBuildDeviceNotifyListWatchdog+0x1c fffff98a2b7af760 fffff8025f28123e : 0000000000000000 0000000000000000 0000000000000000 fffff8025ad35b88 : nt!KiProcessExpiredTimerList+0x1eb fffff98a2b7af890 fffff8025f424f6e : ffff800126051180 ffff800126051180 ffff9f8f26db7040 ffff9f8f38e3c040 : nt!KiRetireDpcList+0x54e fffff98a2b7afb40 0000000000000000 : fffff98a2b7b0000 fffff98a2b7a9000 0000000000000000 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
---------
 
Sort by date Sort by votes
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .

have you run the HP Support Assistant?
https://support.hp.com/au-en/help/hp-support-assistant

another option since its intel drivers - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
 
Upvote 0 Downvote
Colif said:
Can you follow option one on the following link - here - and then do this step below: Small memory dumps - Have Windows Create a Small Memory Dump (Minidump) on BSOD - that creates a file in c windows/minidump after the next BSOD
  1. Open Windows File Explore
  2. Navigate to C:\Windows\Minidump
  3. Copy the mini-dump files out onto your Desktop
  4. Do not use Winzip, use the built in facility in Windows
  5. Select those files on your Desktop, right click them and choose 'Send to' - Compressed (zipped) folder
  6. Upload the zip file to the Cloud (OneDrive, DropBox . . . etc.)
  7. Then post a link here to the zip file, so we can take a look for you . . .
have you run the HP Support Assistant?
https://support.hp.com/au-en/help/hp-support-assistant

another option since its intel drivers - https://www.intel.com.au/content/www/au/en/support/intel-driver-support-assistant.html
Click to expand...
Is that compressing the 2.6GB memory dump or is that procedure prior to the memory dump taking place?

As far as HP Support Assistant, no I did not run or install it. I wasn't even aware of that, lol. Does that contain information on the memory dump problem or does that install the necessary drivers?

Here's essentially the sequence on when it happens. On a fresh install, Windows Update will download and install around 25 drivers to the Omen 30L. A system reboot is requested. Once rebooted the system is stable.

Where things go wrong is on the next series Windows Cumulative Updates and additional drivers updates. There is one in particular that says and I don't remember the name but something about Intel SCSI driver and gives a failed installation message. The next driver hangs at 0% install forever and I am then told to reboot.

When I do that, the screen stays in Restarting for roughly 15+ minutes. Shortly after the BSOD appears.

A BSOD will happen 100% on a fresh install and after Windows Updates. It appears if I disable WU altogether and set the PC connection on metered then I won't get any further updates and the system runs with no problems.

So I will need to start over because I wiped the NVME yesterday after the BSOD.

Thanks for the reply Colif !
 
Upvote 0 Downvote
if you set up the steps above, it will create a minidump after the next crash.

The contents of the 2.6gb file wouldn't give me any more that I can use that a 2mb minidump will.

Heat_Fan89 said:
does that install the necessary drivers?
Click to expand...
Yes

i would suggest running either the intel updater or the HP one just after installing windows
or just visit webpage for HP and run auto update - https://support.hp.com/us-en/drivers/selfservice/omen-desktop-pc-30l-gt13-0000i/33492325

the only drivers I think would be anything to do with scsi on there is the Intel RST drivers.

How many ssd/nvme in that PC? Does it have optane?
 
  • Like
Reactions: Heat_Fan89
Upvote 0 Downvote
Colif said:
if you set up the steps above, it will create a minidump after the next crash.

The contents of the 2.6gb file wouldn't give me any more that I can use that a 2mb minidump will.


Yes

i would suggest running either the intel updater or the HP one just after installing windows
or just visit webpage for HP and run auto update - https://support.hp.com/us-en/drivers/selfservice/omen-desktop-pc-30l-gt13-0000i/33492325

the only drivers I think would be anything to do with scsi on there is the Intel RST drivers.

How many ssd/nvme in that PC? Does it have optane?
Click to expand...
Oh, I remember seeing that explained when capturing a memory dump on a YT video. I will set it to C instead.

Currently, only 1 NVME which is the stock 1TB WD that came with the system. The NVME I had in the 2nd port unexpectedly failed when swapping them around in the Omen 30L. The 250GB was going to be for the OS and the 1TB WD for Microsoft Flight Simulator. That sequence led me to think started the BSOD problem. I tried that 250GB NVME on another non-gaming PC and it would not be recognized on the other PC.

Does it have Optane, good question? I don't believe so. How would I know?
 
Upvote 0 Downvote
johnbl said:
Intel Corporation8086SATA Controller [RAID mode]2822


kind of looks like plug and play was attempting to install a driver and it timed out.
looks like a SATA driver from the ID codes.
Click to expand...
Yeah, that sounds about right. The thing is, if I don't do any further driver updates, the system is stable. Should I look in the BIOS to see if I can turn off the RAID feature?

Man, I wish for the days prior to Windows 10 where you could install any driver you wanted to. Windows would only show it as an optional download. Now Windows 10/11 will even download and install a System BIOS. On some systems you can even disable BIOS updates within Windows. You just have to pray it doesn't blowout the motherboard and it has happened before.

Is there a utility where I can turn off Windows Update and manually choose what I want to download? I know there's O&OShutup but I am not aware of a utility that overrides Windows Update.
 
Upvote 0 Downvote
Heat_Fan89 said:
Yeah, that sounds about right. The thing is, if I don't do any further driver updates, the system is stable. Should I look in the BIOS to see if I can turn off the RAID feature?

Man, I wish for the days prior to Windows 10 where you could install any driver you wanted to. Windows would only show it as an optional download. Now Windows 10/11 will even download and install a System BIOS. On some systems you can even disable BIOS updates within Windows. You just have to pray it doesn't blowout the motherboard and it has happened before.

Is there a utility where I can turn off Windows Update and manually choose what I want to download? I know there's O&OShutup but I am not aware of a utility that overrides Windows Update.
Click to expand...
I would turn off the raid in bios. not the best idea for most people to run raid.

I keep the windows update running and avoid 3rd party drivers that are not included with windows.
 
  • Like
Reactions: Heat_Fan89
Upvote 0 Downvote
@Colif, I reinstalled Windows 11 and set the dump file to small 256K.

@johnbl, I turned off RAID in the BIOS and set it to AHCI. Then I reinstalled Windows 11. I also noticed that on the initial drivers installation from Windows Update, it downloaded a few less with RAID turned off.

I am waiting for Windows Update to do the second round of updates. I will keep you two posted.

Thanks again to the both of you for all the help !
 
Upvote 0 Downvote
It dawned on me on how the 250GB Samsung NVME possibly gave up the ghost? I think ESD took its life. I remember there was NO problems with that NVME until I removed it from SSD slot#2 and inserted it into slot#1. When I did that it no longer was recognized, which I found odd, prior to the BSOD episode.

After I set the BIOS from RAID to AHCI, I tried the Samsung NVME one last time and it was still dead. Oh well, lesson learned. I will need to be more careful and discharge myself on the metal chassis first before handling sensitive electronics.
 
Upvote 0 Downvote
Colif said:
the nvme being the problem. I prefer solutions that don't cost money to fix :)
Click to expand...
Ah, gotcha. Yeah, it was really weird that once I moved it from one slot to the other it instantly gave up the ghost. I live in humid Florida and ESD typically isn't a problem, even this time of the year but I guess I was a bit unlucky. It gave me an excuse to pickup a Gen 3 1TB Samsung 980 for $74.99 on sale part of Cyber Monday on Amazon. I'll use that for Microsoft Flight Simulator.

I'm hoping the 980 supports Samsung Magician so I can hopefully get a small boost in performance. Every little bit helps with MSFS 2020.
 
Upvote 0 Downvote
Heat_Fan89 said:
It dawned on me on how the 250GB Samsung NVME possibly gave up the ghost? I think ESD took its life. I remember there was NO problems with that NVME until I removed it from SSD slot#2 and inserted it into slot#1. When I did that it no longer was recognized, which I found odd, prior to the BSOD episode.

After I set the BIOS from RAID to AHCI, I tried the Samsung NVME one last time and it was still dead. Oh well, lesson learned. I will need to be more careful and discharge myself on the metal chassis first before handling sensitive electronics.
Click to expand...

One of the reasons I do not recommend raid mode is because it ties the drive and format to the raid controller of the motherboard (and sometimes the bios/firmware version). You can not move the drive to another machine and have it be recognized correctly with out reformatting. You might confirm your old drive is dead by going back into raid mode in BIOS and testing the suspect drive in the same slot it was originally in to see if it is detected.
 
Upvote 0 Downvote
johnbl said:
One of the reasons I do not recommend raid mode is because it ties the drive and format to the raid controller of the motherboard (and sometimes the bios/firmware version). You can not move the drive to another machine and have it be recognized correctly with out reformatting. You might confirm your old drive is dead by going back into raid mode in BIOS and testing the suspect drive in the same slot it was originally in to see if it is detected.
Click to expand...
Yeah, unfortunately I did that, prior to switching to ACHI in both slots. I also tried it on my Lenovo Mini PC and it also was unrecognizable. Actually that NVME came from that Lenovo ThinkCentre.

No biggie, it was too small for MSFS 2020 and I snagged a Samsung 980 1TB for $75 on Amazon. That's plenty of room for Microsoft Flight Simulator.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom