Error log bugcheck was: 0x0000009f when computer slees

takeoffeh · May 15, 2015

I have an Asus Zenbook with 8.1. Not all the time, but pretty regularly when I leave the device unattended overnight or it goes to sleep it reboots. the error logs show:

The computer has rebooted from a bugcheck. The bugcheck was: 0x0000009f...............

I've attached the SFdebugFiles. Thanks in advance.

SGT Oddball · May 18, 2015

Hi all your recent dumps are pointing towards dne64x.sys which appears to be some sort of Citrix network component Driver Reference Table - dne64x.sys

If you have any Citrix VPN etc software installed then check for updated versions at their site.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, ffffe001a99dbb70, ffffd00020538cb0, ffffe001b3457e10}

Unable to load image \SystemRoot\system32\DRIVERS\dne64x.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dne64x.sys
*** ERROR: Module load completed but symbols could not be loaded for [B]dne64x.sys[/B]
Probably caused by : ntkrnlmp

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: ffffe001a99dbb70, Physical Device Object of the stack
Arg3: ffffd00020538cb0, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: ffffe001b3457e10, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: fffff800f425d000 dne64x

IRP_ADDRESS: ffffe001b3457e10

DEVICE_OBJECT: ffffe001ae576050

DRIVER_OBJECT: ffffe001adcdd060

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre

DPC_STACK_BASE:  FFFFD00020538FB0

STACK_TEXT:  
ffffd000`20538c78 fffff801`34282782 : 00000000`0000009f 00000000`00000003 ffffe001`a99dbb70 ffffd000`20538cb0 : nt!KeBugCheckEx
ffffd000`20538c80 fffff801`342826a2 : ffffe001`b17d7120 00000000`00000000 ffffe001`b17d7158 fffff801`3411e391 : nt!PopIrpWatchdogBugcheck+0xde
ffffd000`20538ce0 fffff801`341202d8 : 00000000`00000000 ffffd000`20538e30 00000000`00000001 00000000`00000002 : nt!PopIrpWatchdog+0x32
ffffd000`20538d30 fffff801`341cddd5 : b8c7d841`9c490193 ffffd000`20507180 fffff801`3405ee00 ffffd000`40ea0000 : nt!KiRetireDpcList+0x4f8
ffffd000`20538fb0 fffff801`341cdbd9 : ffff1a4e`62af1504 00000000`000003ff 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffd000`3ba6e7f0 fffff801`341cfe45 : fffffa80`01657560 fffff801`341cc587 00000000`00140014 00000000`00000000 : nt!KiDispatchInterruptContinue
ffffd000`3ba6e820 fffff801`341cc587 : 00000000`00140014 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterruptBypass+0x25
ffffd000`3ba6e830 fffff801`342952f0 : 00000000`00000000 fffff6e8`002074f8 00000000`00040005 00000000`00000003 : nt!KiInterruptDispatchLBControl+0x197
ffffd000`3ba6e9c0 fffff801`34294bf6 : ffffd000`40e9f000 fffffa80`01655d00 ffffd000`3ba6eb00 00000000`ffffffff : nt!RtlpGenericRandomPatternWorker+0x214
ffffd000`3ba6e9f0 fffff801`34281c7a : ffffd000`40e9f000 ffffd000`3ba6eb00 fffffa80`01655d00 ffffd000`3ba6eb00 : nt!RtlScrubMemory+0x10e
ffffd000`3ba6ea30 fffff801`34281b1c : ffffd000`3ba6eb00 fffffa80`01655d00 ffffe001`a98ef828 fffffa80`01655d10 : nt!MiScrubPage+0x76
ffffd000`3ba6ea60 fffff801`3467cdc8 : ffffe001`00000000 ffffe001`00000000 00000000`00000000 00000000`00000000 : nt!MiScrubNode+0x110
ffffd000`3ba6eae0 fffff801`341276bc : fffff801`3467cd88 ffffe001`b84b7040 ffffe001`b84b7000 fffff801`00000000 : nt!MiScrubMemoryWorker+0x40
ffffd000`3ba6eb50 fffff801`3417a36c : 00000000`00f8ff1f ffffe001`b84b7040 00000000`00000080 ffffe001`b84b7040 : nt!ExpWorkerThread+0x28c
ffffd000`3ba6ec00 fffff801`341d12c6 : ffffd000`20584180 ffffe001`b84b7040 ffffd000`205903c0 ffffe001`b4ea4e50 : nt!PspSystemThreadStartup+0x58
ffffd000`3ba6ec60 00000000`00000000 : ffffd000`3ba6f000 ffffd000`3ba69000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ntkrnlmp

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:0x9f_3_power_down_image_ntkrnlmp

FAILURE_ID_HASH:  {678b3384-34e9-dafc-d401-53951e725571}

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

Error log bugcheck was: 0x0000009f when computer slees

takeoffeh

New Member

My Computer

System One

SGT Oddball

Member

My Computer

System One