BSOD 0x9F in NTOSKRNL.EXE

Anonymous
2013-04-19T06:40:47+00:00

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

 LegalCopyright: © Microsoft Corporation. All rights reserved.

 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)?

Windows for home | Previous Windows versions | Performance and system failures

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

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2015-05-31T08:59:20+00:00

    New BSOD upon restart... due to card inserted in SD slot not detected...

    (Automatic) dump at http://1drv.ms/1HDHWyu

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-31T05:35:43+00:00

    Thanks for the links about the "dedicated dump files." I was not aware of that Windows 8 feature. Just to be sure before I give it a try: is it supported also by 32-bit Windows 8?

    I'd expected you'd agree with me that reinstalling anything is not a good idea for now.

    I couldn't find any means in the Dell (Studio 1735, version A05) BIOS to disable the fingerprint device.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-05-30T17:02:42+00:00

    For "Automatic memory dump" you could a "System managed file" for the page file which should adjust the setting automatically.

    Also, for Windows 8 one should be able to use the Dedicated Dump File feature to set a page file reserved for crash dumps only even on a different drive:

    http://blogs.msdn.com/b/ntdebugging/archive/2010/04/02/how-to-use-the-dedicateddumpfile-registry-value-to-overcome-space-limitations-on-the-system-drive-when-capturing-a-system-memory-dump.aspx

    There is more on Automatic memory dump and Dedicated dump files in the following article:

    https://support.microsoft.com/en-us/kb/2860880

    I might suggest at this point not to reinstall Avast or the other drivers until the BSODs resolve.

    In the powercfg report there appears to be a reference to the Fingerprint Sensor although does not appear to be directly related to the BSOD.

    Can you disable the Fingerprint biometric device in the BIOS?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-05-29T05:25:42+00:00

    Thanks again for helping me out with this issue.

    The powercfg report is at http://1drv.ms/1AxGpg9. I don't see anything that would be problematic enough to justify ;-) a BSOD!

    Does it make sense at this point to reinstall Avast!, the Logitech driver and the fingerprint support (I will have to find out how to get the latter back to work....), or do you think it's better to finish determining (and removing!) the cause of the BSODs?

    About "Automatic memory dump": what are the requirements in terms of pagefile size on C:? I'd like to revert to a "SSD-friendly" pagefile configuration (I have another pagefile on HDD D: but only the C: pagefile can be used for dumps, although I never really understood why).

    Next time I cannot use an inserted USB key I'll look at the article, especially looking for "unknown" devices. But I have the feeling that would not be the case--I don't get an enumeration sound in that case, nothing happens. Does this hint at some other potential causes?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2015-05-29T01:12:41+00:00

    Change "Write debugging information" to "Automatic memory dump".

    That should produce a kernel dump file along with a minidump file.

    The kernel dump file should be much smaller than the complete memory dump.

    The latest dump files do not implicate any third party driver.

    The ATSwpWDF.sys is no longer a loaded driver so the issue does not appear to be with that driver or device.

    It may be useful to obtain an energy report:

    Right-click the Start menu and choose "Command Prompt (Admin)" and at the command prompt type the following and press "Enter"

    powercfg -energy

    Take a look at report generated and see if you can find any potential problem.

    You can provide the report via OneDrive if you wish.

    Also, the following link has some reason why a USB device is not enumerated:

    http://blogs.msdn.com/b/usbcoreblog/archive/2009/11/03/why-is-my-usb-device-not-detected-or-comes-up-as-unknown-device_3f00_.aspx

    Was this answer helpful?

    0 comments