Go Back   Tech Support Forum > Microsoft Support > BSOD, App Crashes And Hangs

User Tag List

BSOD BugCheck 9F Probably caused by : ntkrnlmp.exe

This is a discussion on BSOD BugCheck 9F Probably caused by : ntkrnlmp.exe within the BSOD, App Crashes And Hangs forums, part of the Tech Support Forum category. Hello, Hope someone can help with this. I have recently been getting a long delay when shutting down my computer,

Closed Thread
Thread Tools Search this Thread
Old 05-01-2015, 12:52 PM   #1
Registered Member
Join Date: May 2015
Posts: 1
OS: Windows 7 Pro 64bit SP1


Hope someone can help with this. I have recently been getting a long delay when shutting down my computer, followed by a BSOD. It restarts, loads into Windows and then states it has recovered from an unexpected shutdown, with the following info:

Problem Event Name: BlueScreen
OS Version: 6.1.7601.
Locale ID: 2057

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000004
BCP2: 0000000000000258
BCP3: 0000000000000000
BCP4: FFFFF80000B9A510
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

I've tried looking at the dump (have never done this before...) and using WinDbg found this:

BugCheck 9F, {4, 258, 0, fffff80000b9a510}
Probably caused by : ntkrnlmp.exe ( nt!PnpBugcheckPowerTimeout+76 )


A driver is causing an inconsistent power state.
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
Arg2: 0000000000000258, Timeout in seconds.
Arg3: 0000000000000000, The thread currently holding on to the Pnp lock.
Arg4: fffff80000b9a510

I can understand it's caused by a driver, but no idea how to trace it.... Can someone help please? I make music so have a few midi controllers (3) and external soundcard attached. I can list this all if needs be, but hopefully the attached files will tell a better, more detailed story than I

Many thanks in advance with any help I can get with this.
Attached Files
File Type: zip SysnativeFileCollectionApp.zip (1.00 MB, 22 views)
File Type: zip Perfmon.zip (142.4 KB, 22 views)
RedCatz is offline  
Sponsored Links
Old 05-09-2015, 01:57 PM   #2
TSF Enthusiast
Join Date: Apr 2015
Posts: 325
OS: Windows 7 SP1 x64

Hi, sorry for the delay.

The BSOD logs aren't conclusive. The constant thing is that it's probably caused by a driver (it just never lists which one).

First, please uninstall AVG and substitute it for MSE temporarily (you can switch back to AVG if you'd once we find the culprit).

I'd like you to go through this list, and attempt to update each driver, prioritizing those with an older date. Information about most of the drivers can be found below this code box.

3rd party drivers - Sorted by Date
**************************Tue Apr 28 13:21:03.058 2015 (UTC - 5:00)**************************
e1e6032e.sys                Tue Mar 24 13:17:23 2009 (49C923B3)
atikmdag.sys                Fri Apr 24 05:51:57 2009 (49F199CD)
intelppm.sys                Mon Jul 13 18:19:25 2009 (4A5BC0FD)
mafw.sys                    Wed Jul 29 16:26:58 2009 (4A70BEA2)
rdwm1027.sys                Thu Sep 17 20:25:49 2009 (4AB2E19D)
bomebus.sys                 Thu Oct 15 06:50:17 2009 (4AD70C79)
bomemidi.sys                Thu Oct 15 06:50:21 2009 (4AD70C7D)
MAudioLegacyKeyboard.sys    Tue Feb  9 11:53:15 2010 (4B71A10B)
amdxata.sys                 Fri Mar 19 11:18:18 2010 (4BA3A3CA)
iaStorV.sys                 Thu Jun 10 19:46:19 2010 (4C11875B)
athrx.sys                   Tue Nov 23 18:11:58 2010 (4CEC584E)
KORGUM64.SYS                Mon Jan 23 01:28:15 2012 (4F1D0C0F)
NIWinCDEmu.sys              Wed Sep 26 06:40:33 2012 (5062E9B1)
mafw.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
rdwm1027.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
MAudioLegacyKeyboard.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
NIWinCDEmu.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.


If this does not stop the BSOD's, then please run Driver Verifier according to these instructions:

Driver Verifier:

What is Driver Verifier?

Driver Verifier monitors Windows kernel-mode drivers, graphics drivers, and even 3rd party drivers to detect illegal function calls or actions that might corrupt the system. Driver Verifier can subject the Windows drivers to a variety of stresses and tests to find improper behavior.

Essentially, if there's a 3rd party driver believed to be causing the issues at hand, enabling Driver Verifier will help us see which specific driver is causing the problem.

Before enabling Driver Verifier, it is recommended to create a System Restore Point:

Vista - START | type rstrui - create a restore point
Windows 7 - START | type create | select "Create a Restore Point"
Windows 8/8.1 - Restore Point - Create in Windows 8

How to enable Driver Verifier:

Start > type "verifier" without the quotes > Select the following options -

1. Select - "Create custom settings (for code developers)"
2. Select - "Select individual settings from a full list"
3. Check the following boxes -
- Special Pool
- Pool Tracking
- Force IRQL Checking
- Deadlock Detection
- Security Checks (only on Windows 7 & 8/8.1)
- DDI compliance checking (only on Windows 8/8.1)
- Miscellaneous Checks
4. Select - "Select driver names from a list"
5. Click on the "Provider" tab. This will sort all of the drivers by the provider.
6. Check EVERY box that is NOT provided by Microsoft / Microsoft Corporation.
7. Click on Finish.
8. Restart.

Important information regarding Driver Verifier:

- Perhaps the most important which I will now clarify as this has been misunderstood often, enabling Driver Verifier by itself is not! a solution, but instead a diagnostic utility. It will tell us if a driver is causing your issues, but again it will not outright solve your issues.

- If Driver Verifier finds a violation, the system will BSOD. To expand on this a bit more for the interested, specifically what Driver Verifier actually does is it looks for any driver making illegal function calls, causing memory leaks, etc. When and/if this happens, system corruption occurs if allowed to continue. When Driver Verifier is enabled per my instructions above, it is monitoring all 3rd party drivers (as we have it set that way) and when it catches a driver attempting to do this, it will quickly flag that driver as being a troublemaker, and bring down the system safely before any corruption can occur.

- After enabling Driver Verifier and restarting the system, depending on the culprit, if for example the driver is on start-up, you may not be able to get back into normal Windows because Driver Verifier will detect it in violation almost straight away, and as stated above, that will cause / force a BSOD.

If this happens, do not panic, do the following:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > Search > type "cmd" without the quotes.

- To turn off Driver Verifier, type in cmd "verifier /reset" without the quotes.

- Restart and boot into normal Windows.

If your OS became corrupt or you cannot boot into Windows after disabling verifier via Safe Mode:

- Boot into Safe Mode by repeatedly tapping the F8 key during boot-up.

- Once in Safe Mode - Start > type "system restore" without the quotes.

- Choose the restore point you created earlier.

-- Note that Safe Mode for Windows 8/8.1 is a bit different, and you may need to try different methods: 5 Ways to Boot into Safe Mode in Windows 8 & Windows 8.1

How long should I keep Driver Verifier enabled for?

I recommend keeping it enabled for at least 24 hours. If you don't BSOD by then, disable Driver Verifier. I will usually say whether or not I'd like for you to keep it enabled any longer.

My system BSOD'd with Driver Verifier enabled, where can I find the crash dumps?

- If you have the system set to generate Small Memory Dumps, they will be located in %systemroot%\Minidump.

- If you have the system set to generate Kernel Memory Dumps, it will be located in %systemroot% and labeled MEMORY.DMP.

Any other questions can most likely be answered by this article:

Using Driver Verifier to identify issues with Windows drivers for advanced users
thisisu is offline  
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Similar Threads
Thread Thread Starter Forum Replies Last Post
BSOD intermittently during Windows 7 Startup
Hello, I m new to this forum. I am using this computer on everyday basis. however, BSOD happens to it once in a while during start up to boot into windows. Found this during BSOD, "0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s." I have...
hunterz86 BSOD, App Crashes And Hangs 3 03-13-2013 07:31 AM
BSOD 0x0000007e PLZ HELP ME :(
Hey guys, I'm new to this forum hoping you could help me out with my BSOD problem. Here's the problem : The Bsod occured a few months ago and i've been running in safe mode ever since ( Witch is possible without any problems ). If i try and start it in normal mode, it gives me a system...
Rowbance BSOD, App Crashes And Hangs 13 01-09-2013 07:35 PM
BSOD on Asus Laptop
Hey, I'm experiencing the BSOD with increasing frequency since I performed some updates in June. It's happening on an almost daily basis now and I'm afraid might be a hardware issue due to increased frequency when PC's been on for a while. The error code is always the same: "The bugcheck...
tuttiface BSOD, App Crashes And Hangs 6 12-01-2012 08:39 PM
I have been getting BSOD, Mainly when I am watching video from any source (Mpeg, AVI, youtube, Hulu). As far as I can tell my drivers are all up to date. I am not the best at this stuff but have tried everything I can think of and everthing I have found online before asking for help. Any help would...
jon33jon2003 BSOD, App Crashes And Hangs 5 09-27-2011 04:22 PM
[SOLVED] BSOD 0x9f Vista Home Basic
I am working on my gfs computer trying to get rid of getting a BSOD on a near daily basis. I tried to attach the files requested as one zip but it was too large. OS: Vista x86 (32-bit) or x64 ? 32bit What was original installed OS on system? Vista Home Basic SP 1 Is the OS an OEM version?...
lius69 BSOD, App Crashes And Hangs 5 08-18-2011 12:25 PM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is on
Smilies are on
[IMG] code is on
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off

Post a Question

» Site Navigation
 > FAQ
Powered by vBadvanced CMPS v3.2.3

All times are GMT -7. The time now is 02:40 AM.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2020, vBulletin Solutions, Inc.
vBulletin Security provided by vBSecurity v2.2.2 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.1.0 (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
Copyright 2001 - 2018, Tech Support Forum

Windows 10 - Windows 7 - Windows XP - Windows Vista - Trojan Removal - Spyware Removal - Virus Removal - Networking - Security - Top Web Hosts