[SOLVED] Can anyone help me understand this dump file?

[tarogmats]

Spoiler: DMP Debug Info

***

• *
• 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: ffffb30449fe7040, The thread currently holding on to the Pnp lock.
Arg4: ffffda895c2a7880, nt!TRIAGE_9F_PNP on Win7 and higher

Debugging Details:
------------------

Implicit thread is now ffffb30449fe7040 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 2031 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2038 Key : Analysis.Init.CPU.mSec Value: 921 Key : Analysis.Init.Elapsed.mSec Value: 40717 Key : Analysis.Memory.CommitPeak.Mb Value: 76 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 9f BUGCHECK_P1: 4 BUGCHECK_P2: 12c BUGCHECK_P3: ffffb30449fe7040 BUGCHECK_P4: ffffda895c2a7880 DRVPOWERSTATE_SUBCODE: 4 FAULTING_THREAD: ffffb30449fe7040 BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 PROCESS_NAME: System STACK_TEXT: ffffda8961180520 fffff8043860c970 : ffff8081276d8180 00000000ffffffff 0000000000000000 ffff9e007ce00100 : nt!KiSwapContext+0x76 ffffda8961180660 fffff8043860be9f : 0000000100000007 0000000000000004 ffffda8961180820 ffff9e0000000000 : nt!KiSwapThread+0x500 ffffda8961180710 fffff8043860b743 : ffffb30400000000 0000000000000000 fffff8043841e100 ffffb30449fe7180 : nt!KiCommitThreadWait+0x14f ffffda89611807b0 fffff8043876b539 : ffffb3044d5d6690 0000000000000000 ffff9e00c50f8400 fffff80438b5bd00 : nt!KeWaitForSingleObject+0x233 ffffda89611808a0 fffff8043876b3e2 : ffff9e00c50f84b0 ffffb3044c2d5bf0 0000000000000000 0000000000000000 : nt!PopFxActivateDevice+0x149 ffffda89611808f0 fffff80438b31af4 : ffffb3044078a830 0000000000000000 0000000000000000 fffff80438b31a4f : nt!PoFxActivateDevice+0xe ffffda8961180920 fffff80438b31803 : ffffb3044c2d5bf0 ffffda89611809a0 0000000000000000 fffff80438b3149d : nt!PnpDeleteLockedDeviceNode+0x74 ffffda8961180960 fffff80438b2ff4e : ffffb3044d7d5dd0 0000000300000002 0000000000000000 0000000000000000 : nt!PnpDeleteLockedDeviceNodes+0xf7 ffffda89611809e0 fffff80438b2ad5b : ffffda8961180b20 ffffb30443d1ab00 ffffda8961180b00 ffff9e0000000003 : nt!PnpProcessQueryRemoveAndEject+0x1da ffffda8961180ac0 fffff80438a48ade : ffff9e00ba16a570 ffff9e00ac76f1b0 ffffb30436e8ba00 0000000000000000 : nt!PnpProcessTargetDeviceEvent+0xeb ffffda8961180af0 fffff80438741225 : ffffb30449fe7040 ffffb30449fe7040 ffffb30436e8ba20 ffffb30447bf9560 : nt!PnpDeviceEventWorker+0x2ce ffffda8961180b70 fffff804386f53b5 : ffffb30449fe7040 0000000000000080 ffffb30436ea3040 0000000000000001 : nt!ExpWorkerThread+0x105 ffffda8961180c10 fffff804387fe278 : ffff808127847180 ffffb30449fe7040 fffff804386f5360 000000000138b970 : nt!PspSystemThreadStartup+0x55 ffffda8961180c60 0000000000000000 : ffffda8961181000 ffffda896117b000 0000000000000000 00000000`00000000 : nt!KiStartSystemThread+0x28


STACK_COMMAND: .thread 0xffffb30449fe7040 ; kb

SYMBOL_NAME: nt!KiSwapContext+76

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 76

FAILURE_BUCKET_ID: 0x9F_4_nt!KiSwapContext

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {e8e4ff91-4633-fc99-d928-aa21c06c4344}

Followup: MachineOwner
---------

This is the message I got this morning. The system rebooted while I was asleep and I noticed everything had died, so it wasn't a fast boot, nothing had restarted.

This is the first time running my RAM at 3200, and I'm wondering if it's something to do with that OC or if it is purely driver based.

System specs are:

ASUS b450-f gaming II
Ryzen 5 2600x
Corsair Vengeance Pro 16GB
EVGA 700d PSU
GTX 1060 (6GB)

any help would be appreciated, because I'm drawing absolute blanks lol.

 

[Colif]

hard to tell.

could run in non xmp and see if you bsod again

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 . . .
   

 

[tarogmats]

hard to tell.

could run in non xmp and see if you bsod again

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 . . .

Hey, really sorry about the late reply.
The issue never replicated, and I actually never turned intentionally disabled XMP, it reset on me once after I powered off during a boot cycle and the system requested that I go into the bios because the RAM profile had changed.

https://drive.google.com/file/d/1QFAj5174tgFEUg4ZXENZMX0BcxJn3atQ/view?usp=sharing

https://drive.google.com/file/d/1_rsPW4hEx5AqpQm6WTjdapqEDk_0YJKD/view?usp=sharing

Still, I am very curious, so here are the dump files if you or anyone ever has the time. I tried to read them using a viewer, but I couldn't quite understand.

 

[jasonf2]

RAM overclocks with Ryzen can be finicky at best. Even when QVL has board listed OC I have not been able to get some to run stable especially with vengeance. I would not run XMP without doing normal stability testing. RAM operating right on the edge can mess with more than simple BSOD, especially when installing OS or updates.

 

[tarogmats]

RAM overclocks with Ryzen can be finicky at best. Even when QVL has board listed OC I have not been able to get some to run stable especially with vengeance. I would not run XMP without doing normal stability testing. RAM operating right on the edge can mess with more than simple BSOD, especially when installing OS or updates.

What'd you mean when you say "normal stability testing". Just run memtest or something with it at default?

 

[gardenman]

Hi, I ran the dump files through the debugger and got the following information: https://jsfiddle.net/6emot4az/show This link is for anyone wanting to help. You do not have to view it. It is safe to "run the fiddle" as the page asks.

Spoiler: Dump File Results

File information:	061621-13437-01.dmp (Jun 16 2021 - 18:47:26)
Bugcheck:	BugCheck 1000009F, {4, 12c, ffff9c0d883db580, ffffee08b54b5880} (1000009F)
Probably caused by:	memory_corruption (Process: System)
Uptime:	1 Day(s), 16 Hour(s), 50 Min(s), and 07 Sec(s)

File information:	061521-7234-01.dmp (Jun 15 2021 - 01:56:48)
Bugcheck:	BugCheck 1000009F, {4, 12c, ffffb30449fe7040, ffffda895c2a7880} (1000009F)
Probably caused by:	memory_corruption (Process: System)
Uptime:	0 Day(s), 12 Hour(s), 49 Min(s), and 03 Sec(s)

Comment: The GPU tweaking driver "iomap64.sys" was found on your system. (AI Suite or GPU Tweak 2)

Possible Motherboard page: https://rog.asus.com/us/motherboards/rog-strix/rog-strix-b450-f-gaming-ii-model/
There is a BIOS update available for your system. Wait for additional information before deciding to update or not. Important: Verify that I have linked to the correct motherboard. Updating your BIOS can be risky. Never try it when you might lose power (lightning storms, recent power outages, etc).

This information can be used by others to help you. Someone else will post with more information. Please wait for additional answers. Good luck.

 

[Colif]

both are driver power state errors.

can you run this for me, it will create a zip file. can you upload to same place as dump files - https://www.sysnative.com/forums/pages/bsodcollectionapp/
it might let me see what is causing the BSOD

I have seen that error recently with Nvidia gpu drivers so might be them.

 

[tarogmats]

@gardenman Oh wow, I'd actually uninstalled the whole AI suite stuff, cause I found out it was keeping my cores going all the time, so the system was never really "idle", and it's the correct mobo. Wasn't keen on the bios update as yet tbh, I don't even think it really applied to me cause I figured I wouldn't get any performance boosts from the update anyway.

@Colif https://drive.google.com/file/d/1-P9wKx19xaUDTACn0Q3Org23Lgv0a40X/view?usp=sharing here's the stuff generated.

 

[gardenman]

both are driver power state errors.

No, Driver Power State errors are bugcheck: 0x0000009F
These are undocumented: 0x1000009F

Edit: It might be a Driver Power State bugcheck. This info comes from other sites. But I'm still not sure because it is a different number.

 

[jasonf2]

What'd you mean when you say "normal stability testing". Just run memtest or something with it at default?

https://www.tomshardware.com/reviews/ram-overclocking-guide,4693.html

The link above gives a comprehensive guide to overclocking RAM. Memtest86+ is what I use.

 

[Colif]

No BSOD since the 16th

try updating razer drivers, one of the BSOD the game manager service also crashed at same time, it also crashed on the 14th, day before the other BSOD. So maybe.
Check synapse is up to date

 

[tarogmats]

Hi good afternoon, I did the automatic razer update a few days ago. Had a little hiccup today, we were having some bad weather and I'm pretty sure I had a power ripple. My lights flickered, my fan died, and my monitor got some screen fracturing going on for a quick minute, almost like the GPU was dying. It's the middle of a storm and power has been going out etc.
Afterwards I powered back up the system this a bit ago, and I got a BSOD during boot saying windows ran into an issue the code was MEMORY_MANAGEMENT.

I'm not sure if this counts as a new issue, or this is a symptom of the current issue. Either way, thanks for the advice and assistance.

 

[Colif]

Had a little hiccup today, we were having some bad weather and I'm pretty sure I had a power ripple. My lights flickered, my fan died, and my monitor got some screen fracturing going on for a quick minute, almost like the GPU was dying. It's the middle of a storm and power has been going out etc.

why is your PC on during a storm?

I unplug my pc from Ethernet and have it disconnected completely from power during storms as power surges are bad for computers. They may have protections but once the protections are used, they no good for next time. I even unplug my power board for same reason. I only have one PC and don't want unnecessary repairs. Easier to just use my phone while storms are around.

So do you get bsod every start up or just the once?

 

[tarogmats]

why is your PC on during a storm?

I unplug my pc from Ethernet and have it disconnected completely from power during storms as power surges are bad for computers. They may have protections but once the protections are used, they no good for next time. I even unplug my power board for same reason. I only have one PC and don't want unnecessary repairs. Easier to just use my phone while storms are around.

So do you get bsod every start up or just the once?

I went to bed and left it on, so when I woke up the storm was happening and I sat down to shut down but I was checking a few things first, and that's how the story begins.
It was only the once, I turned it off and on again. Also connected my modem to the UPS, didn't know about that it could fry the system as well until I googled a bit.