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-06-19T19:46:44+00:00

Another BSOD, upon rebooting 'cos I was not able to access a USB key...

Dump is at http://1drv.ms/1J8JFSg
Was this answer helpful?

0 comments No comments
Anonymous

2015-06-19T05:59:19+00:00

I couldn't find anything installed that would use Dokan, nor did I find any occurrence of the Dokan DLL on my system, so I just removed the driver.

I also disabled Driver Verifier (will get me a more responsive system--I suspect DV's sandboxing scheme to use quite some amount of memory, system was paging a lot).

Thanks again for your continued support.
Was this answer helpful?

0 comments No comments
Anonymous

2015-06-18T22:17:17+00:00

In this topic there was a similar 0x9F error and issue with USB detection.

Checking a dump file from that topic shows the dokan.sys as present on both that system and yours.

Can you uninstall the program that installed the dokan.sys which may be Dokan or it may have been bundled with another program.

I would also suggest to disable the Driver Verifier at this time.
Was this answer helpful?

0 comments No comments
Anonymous

2015-06-16T19:14:28+00:00

FWIW: after that BSOD (and a couple of others, most recent two are http://1drv.ms/1ffpdTd and http://1drv.ms/1ffpg12 ) I enabled DV for all non-MS drivers:

VerifyDriverLevel 0x209bb

VerifyDrivers pxhelp20.sys mpksl65ff1248.sys elbycdio.sys atikmpag.sys atikmdag.sys bcmwl63l.sys ndis.sys k57nd60x.sys rimmptsk.sys rimsptsk.sys rixdptsk.sys itecir.sys gearaspiwdm.sys cbfs3.sys vclone.sys atihdw73.sys atmfd.dll pdfsfilter.sys defragfs.sys dokan.sys npf.sys bcbtums.sys btwampfl.sys secdrv.sys btwavdt.sys btwaudio.sys btwl2cap.sys btwrchid.sys vstor2-mntapi20-shared.sys 000.fcl mpksl6727b278.sys

None of this driver has triggered a DV STOP so far; I'll keep running with these settings.

Any other suggestions?
Was this answer helpful?

0 comments No comments
Anonymous

2015-06-15T18:42:26+00:00

Seems the 0x9F is still here....

Latest dump at http://1drv.ms/1BifIMD
Was this answer helpful?

0 comments No comments