BSOD 0x9F in NTOSKRNL.EXE

Anonymous

I'm getting somewhat frequent BSODs these days.

WinDbg reports:

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {4, 12c, 86a6c340, 809b4b54}

Implicit thread is now 86a6c340

Probably caused by : ntkrpamp.exe ( nt!KiSwapContext+19 )

Followup: MachineOwner

0: kd> !analyze -v

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)

A driver has failed to complete a power IRP within a specific time (usually 10 minutes).

Arguments:

Arg1: 00000004, The power transition timed out waiting to synchronize with the Pnp

subsystem.

Arg2: 0000012c, Timeout in seconds.

Arg3: 86a6c340, The thread currently holding on to the Pnp lock.

Arg4: 809b4b54, nt!TRIAGE_9F_PNP on Win7

Debugging Details:

Implicit thread is now 86a6c340

DRVPOWERSTATE_SUBCODE: 4

FAULTING_THREAD: 86a6c340

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: 0x9F

PROCESS_NAME: System

CURRENT_IRQL: 2

LAST_CONTROL_TRANSFER: from 81bfb22f to 81ba3699

STACK_TEXT:

d88f7aec 81bfb22f 00002000 86a6c398 86a6c340 nt!KiSwapContext+0x19

d88f7b60 81bfd058 86a6c340 86a6c420 00000002 nt!KiCommitThreadWait+0x280

d88f7bfc 81c19a81 84ef4710 0000001b 00000000 nt!KeWaitForSingleObject+0x26c

d88f7c60 81c02406 81c54ee0 84ef4710 81c39578 nt!ExpWaitForResource+0xd2

d88f7ca8 81d04d68 81c54ee0 00000001 81c39578 nt!ExAcquireResourceExclusiveLite+0x191

d88f7cc4 81ad36f9 00000001 81c39578 86a6c340 nt!PpDevNodeLockTree+0x43

d88f7d1c 81c01c95 00000000 86a6c340 00000000 nt!PnpDeviceActionWorker+0x3d

d88f7d74 81ae5aaa 00010000 c8c30dc3 00000000 nt!ExpWorkerThread+0x111

d88f7db0 81ba3f19 81c01b88 00010000 00000000 nt!PspSystemThreadStartup+0x4a

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND: .thread 0xffffffff86a6c340 ; kb

FOLLOWUP_IP:

nt!KiSwapContext+19

81ba3699 8b2c24 mov ebp,dword ptr [esp]

SYMBOL_STACK_INDEX: 0

SYMBOL_NAME: nt!KiSwapContext+19

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrpamp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 513809e8

BUCKET_ID_FUNC_OFFSET: 19

FAILURE_BUCKET_ID: 0x9F_4_nt!KiSwapContext

BUCKET_ID: 0x9F_4_nt!KiSwapContext

Followup: MachineOwner

The file ntoskrnl.exe is dated March 7 and has the following version information:

c:/windows/system32/ntoskrnl.exe:

File Version: 6.2.9200.16551

Product Version: 6.2.9200.16551

File Flags:

File OS: NT_WINDOWS32

File Type: APP

Language: English (United States), Code Page: Unicode

CompanyName: Microsoft Corporation

FileDescription: NT Kernel & System

FileVersion: 6.2.9200.16551 (win8_gdr.130306-1502)

InternalName: ntkrpamp.exe

OriginalFilename: ntkrpamp.exe

ProductName: Microsoft® Windows® Operating System

ProductVersion: 6.2.9200.16551

I have a full memory dump available.

How should I troubleshoot this (other than the tedious msconfig / disable stuff / enable stuff /... process)?

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

79 answers

Anonymous

2015-04-27T06:14:11+00:00

Problem's occurring again from time to time these days.

still no idea as to how to pinpoint the offending driver?
Was this answer helpful?

0 comments No comments
Anonymous

2013-12-05T06:47:39+00:00

So? Has anyone got a clue as to how to extract useful information from the full kernel memory dump?
Was this answer helpful?

0 comments No comments
Anonymous

2013-04-20T05:29:57+00:00

The problem with all these troubleshooting techniques is that they more or less require that the problem be reproducible. I just restarted the offending machine, and it worked like a charm. If I would try e.g. safe mode, maybe the problem wouldn't show up in days, and I wouldn't be able to use the machine for days because most of the apps I use daily wouldn't work in safe mode...

Is there something I could extract from the dump that would tell me more than "ntoskrnl.exe is holding the PnP lock"? Maybe: who else is trying to acquire the lock?
Was this answer helpful?

0 comments No comments
Anonymous

2013-04-19T21:51:44+00:00

Hi,

This problem occurs due to device are not cleaned up or the requests are canceled.

To resolve the error and prevent the error from recurring, update or remove the offending driver. This error can occur because of a device driver, but it can also occur because of a file system filter driver (for example, a driver that is installed by an antivirus, remote control or backup program).

I would recommend you to install the latest drives from the manufactures’ website and check.

Refer to the following Microsoft article.

Bug Check 0x9F: DRIVER_POWER_STATE_FAILURE: http://msdn.microsoft.com/en-us/library/windows/hardware/ff559329(v=vs.85).aspx

Note: The above article is for Windows 7 however you might and go-ahead and performs the steps which are applicable for Windows 8.

Such as: (System Restore, Update Drivers, Software update, Safe mode, Memory error, Startup repair)

Safe Mode:

Follow these steps to start the computer in safe mode.

a)    Press the ‘Windows + C’ key on the keyboard.

b)    Click on settings, more pc settings and then general.

c)     Scroll down to advanced startup, click restart now.

d)    Click on troubleshoot, advanced options, Windows Startup Settings.

e)    Click restart, select safe mode and then press enter.

Note: Restart the computer to start in normal mode.

Hard disk/Memory errors:

a.     Open Computer, right-click the drive that you want to check, and then click Properties.

b.     Click the Tools tab, and then, under Error-checking, click Check now.

Note: While performing chkdsk on the hard drive if any bad sectors are found on the hard drive when chkdsk tries to repair that sector if any data available on that might be lost.

Startup Repair:

Startup Repair is a Windows 8 system recovery tool that can fix certain problems, such as missing or damaged system files.

To perform Automatic repair on Windows 8 computer follow these steps:

a.     Insert the media such as (USB or DVD) and restart your computer.

b.     Press F12 key (typically this is F12, but it can differ between computer manufacturers) and choose the drive that you inserted the installation media into.

c.     Once the Windows Setup window appears, follow these steps:

d.     Click next and select Repair your computer.

e.     You will then see a blue screen and an option to choose. Choose the option Troubleshoot and select advanced options.

f.      You may choose Automatic Repair from Advanced boot option.

Note: Modifying BIOS/ complementary metal oxide semiconductor (CMOS) settings incorrectly can cause serious problems that may prevent your computer from booting properly. Microsoft cannot guarantee that any problems resulting from the configuring of BIOS/CMOS settings can be solved. Modifications of the settings are at your own risk.

Keep us posted on the status of the issue.
Was this answer helpful?

0 comments No comments