Windows 7: BSOD coming out of Hibernate

EzBulka · 15 Jul 2013

Truth is, I often don't actually see the Blue Screen. But for a long time now my Lenovo laptop running Windows 7 x64 Home Premium will sometimes successfully come out of hibernation ... and sometimes not. Sometimes I'll catch a message on the screen explaining that it couldn't come out of hibernation properly.
I've uploaded my ZIP file with the Grab from the Diag Tool.
Any help would be appreciated.
Thanks.

Arc · 15 Jul 2013

Specs says it is dell, but it looks like a lenovo?

Update Citrix Deterministic Network Enhancer Miniport or Cisco Systems VPN Client driver. Its too old.

Code:

fffff880`03e8a000 fffff880`03eb6000   dne64x   T (no symbols)           
    Loaded symbol image file: dne64x.sys
    Image path: \SystemRoot\system32\DRIVERS\dne64x.sys
    Image name: dne64x.sys
    Timestamp:        Tue Nov 11 06:31:24 2008 (4918D964)
    CheckSum:         000359DA
    ImageSize:        0002C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get it from Cisco Systems, Inc

Also update Atheros AR9285 Wireless Network Adapter. Its old, too

Code:

fffff880`04043000 fffff880`042d0000   athrx      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Sun Nov 14 10:02:38 2010 (4CDF6666)
    CheckSum:         0028FB5F
    ImageSize:        0028D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Get it from Drivers for Atheros AR9285 and Windows 7

Let us know the results.
___________________________________________________________________________________
BSOD ANALYSIS:

Code:

..............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa8006457980, fffff80000b9c518, fffffa800a1c1e10}

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 dne64x.sys
Probably caused by : ntkrnlmp

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: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8006457980, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800a1c1e10, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: fffff88003e8a000 dne64x

DEVICE_OBJECT: fffffa800846d050

DRIVER_OBJECT: fffffa8007bb5e70

IRP_ADDRESS:  fffffa800a1c1e10

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

TAG_NOT_DEFINED_c000000f:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`035358c2 : 00000000`0000009f 00000000`00000003 fffffa80`06457980 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`034d084c : fffff800`00b9c618 fffff800`00b9c618 00000000`00000000 00000000`00000002 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`034d06e6 : fffffa80`06d04868 fffffa80`06d04868 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`034d05ce : 00000059`39a4cbfd fffff800`00b9cc58 00000000`00257bc5 fffff800`03644b28 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`034d03b7 : 00000014`dc3a93c4 00000014`00257bc5 00000014`dc3a9373 00000000`000000c5 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034bd90a : fffff800`03640e80 fffff800`0364ecc0 00000000`00000000 fffff880`053c04d0 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ntkrnlmp

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

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

0: kd> lmvm dne64x
start             end                 module name
fffff880`03e8a000 fffff880`03eb6000   dne64x   T (no symbols)           
    Loaded symbol image file: dne64x.sys
    Image path: \SystemRoot\system32\DRIVERS\dne64x.sys
    Image name: dne64x.sys
    Timestamp:        Tue Nov 11 06:31:24 2008 (4918D964)
    CheckSum:         000359DA
    ImageSize:        0002C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> !irp fffffa800a1c1e10
Irp is active with 3 stacks 2 is current (= 0xfffffa800a1c1f28)
 No Mdl: No System Buffer: Thread 00000000:  Irp stack trace.  
     cmd  flg cl Device   File     Completion-Context
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

            Args: 00000000 00000000 00000000 00000000
>[ 16, 2]   0 e1 fffffa800846d050 00000000 fffff80003712200-fffffa800987a860 Success Error Cancel pending
           \Driver\DNE    nt!PopSystemIrpCompletion
            Args: 00015500 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa800987a860    

            Args: 00000000 00000000 00000000 00000000
0: kd> lmvm dne64x
start             end                 module name
fffff880`03e8a000 fffff880`03eb6000   dne64x   T (no symbols)           
    Loaded symbol image file: dne64x.sys
    Image path: \SystemRoot\system32\DRIVERS\dne64x.sys
    Image name: dne64x.sys
    Timestamp:        Tue Nov 11 06:31:24 2008 (4918D964)
    CheckSum:         000359DA
    ImageSize:        0002C000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
0: kd> lmvm athrx
start             end                 module name
fffff880`04043000 fffff880`042d0000   athrx      (deferred)             
    Image path: \SystemRoot\system32\DRIVERS\athrx.sys
    Image name: athrx.sys
    Timestamp:        Sun Nov 14 10:02:38 2010 (4CDF6666)
    CheckSum:         0028FB5F
    ImageSize:        0028D000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

EzBulka · 15 Jul 2013

Wow, Arc again! Thanks for saving me once more. I will do as you have suggested.
Understandably, it will take some time to be able to confirm that this has fixed the issue since it was occurring intermittently.

EzBulka · 05 Aug 2013

I have updated those drivers as per your recommendation. I don't think it's crashed since then. However, it seems that it has replaced that issue with another more annoying hibernate-related issue. I know cannot connect to any network after the machine comes out of sleep/standby or hibernate. It's not the Wireless. Even if I connect to the router with a network cable, I am unable to establish a connection. When the WiFi sees and attempts to connect to my network I get a connection with Limited Connectivity. I have seen numerous posts with people experiencing similar symptoms but none of the solutions suggested have helped. Would another diagnostic upload help because I did one just in case.

Arc · 06 Aug 2013

Actually I have a very least to do with networking .... apparently my job is done here lol :)

I am requesting chev65 to check your thread .... he has the right command on networking.