BSOD During Sleep

Beelzebot · 06 Feb 2015

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033

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

Attached is the zip file containing the dm log connector output.

Really appreciate any help here. Thank you very much!

Golden · 06 Feb 2015

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000009F, {4, 258, fffffa800caa7040, fffff80004ad63d0}

Implicit thread is now fffffa80`0caa7040
Probably caused by : ntkrnlmp.exe ( nt!KiSwapContext+7a )

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

0: kd> !thread fffffa800caa7040
GetPointerFromAddress: unable to read from fffff800036bc000
THREAD fffffa800caa7040  Cid 0004.0058  Teb: 0000000000000000 Win32Thread: 0000000000000000 WAIT: (WrResource) KernelMode Non-Alertable
    fffffa800d492c10  NotificationEvent
Not impersonating
GetUlongFromAddress: unable to read from fffff800035fbba8
Owning Process            fffffa800ca0cae0       Image:         System
Attached Process          N/A            Image:         N/A
fffff78000000000: Unable to get shared data
Wait Start TickCount      1147181      
Context Switch Count      6931           IdealProcessor: 4  NoStackSwap
ReadMemory error: Cannot get nt!KeMaximumIncrement value.
UserTime                  00:00:00.000
KernelTime                00:00:00.000
Win32 Start Address nt!ExpWorkerThread (0xfffff8000348f450)
Stack Init fffff880035a8c70 Current fffff880035a85e0
Base fffff880035a9000 Limit fffff880035a3000 Call 0
Priority 12 BasePriority 12 UnusualBoost 0 ForegroundBoost 0 IoPriority 2 PagePriority 5
Child-SP          RetAddr           : Args to Child                                                           : Call Site
fffff880`035a8970 fffff800`03901b37 : 00000000`00000000 fffffa80`0ca64b60 fffff8a0`02cfa0f0 fffff880`035a8b78 : nt! ?? ::NNGAKEGL::`string'+0x1b83c
fffff880`035a89a0 fffff800`03902d4c : fffff880`035a8b78 fffffa80`199cb800 fffffa80`0caa7040 fffffa80`199cb850 : nt!PnpProcessQueryRemoveAndEject+0x77
fffff880`035a8ae0 fffff800`037ebd9e : 00000000`00000000 fffffa80`199cb850 fffff8a0`02cfa0f0 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0x4c
fffff880`035a8b10 fffff800`0348f561 : fffff800`036f0d08 fffff8a0`02cfa0f0 fffff800`0362a2d8 00000000`00000000 : nt! ?? ::NNGAKEGL::`string'+0x54d7b
nt!KxStartSystemThread+0x16

Looks like a problem with a plug-and-play USB device. With the exception of the mouse and keyboard, please list all devices that you connect via USB on a regular basis.