BSOD when coming out of Hibernate/Sleep

[justinds89]

Hello we are having an issue where the pc is blue screening when what appears to be coming out of sleep or hibernate. I can't not get it to BSOD if I manually set the computer to sleep or hibernate though. I analyzed the dump file to the best of my ability and it seems to point to the Intel NIC. I have uninstalled and installed an up to date driver however this has yet to fix the issue. Any help and/or thoughts would be greatly appreciated.

 

[koolkat77]

Security App

BHDrvx64.sys                Wed Apr 10 11:39:03 2013 (5164FAF7)
ENG64.SYS                   Thu Dec 20 15:24:21 2012 (50D2D945)
EX64.SYS                    Thu Dec 20 15:22:39 2012 (50D2D8DF)
EraserUtilRebootDrv.sys     Wed Aug  1 05:36:50 2012 (50186C12)
HECIx64.sys                 Fri Jul 13 08:18:26 2012 (4FFF8572)
IDSvia64.sys                Wed Aug 29 08:48:40 2012 (503D8308)
IntcDAud.sys                Fri Jan 11 19:55:16 2013 (50F019C4)
Ironx64.SYS                 Tue Apr 26 04:07:08 2011 (4DB5F08C)
RTDVHD64.sys                Tue Feb  7 13:47:37 2012 (4F30D719)
SRTSP64.SYS                 Sat May 28 04:34:08 2011 (4DE026E0)
SRTSPX64.SYS                Sat May 28 04:34:14 2011 (4DE026E6)
SYMDS64.SYS                 Fri Apr 29 04:42:29 2011 (4DB9ED55)
SYMEFA64.SYS                Wed May 18 04:29:43 2011 (4DD2F6D7)
SYMEVENT64x86.SYS           Thu May  5 09:16:30 2011 (4DC2168E)
SYMNETS.SYS                 Wed Apr 20 04:33:31 2011 (4DAE0DBB)
Teefer.sys                  Sat May 21 06:49:59 2011 (4DD70C37)

Crashes indicate Norton being a possible cause. Remove Norton and replace with Microsoft Security Essentials to see if it provides more stability. Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase

Microsoft Security Essentials and Malwarebytes, both recommended from a strict BSOD perspective.

Microsoft Security Essentials, Free antivirus for windows
Malwarebytes Anti-Malware Free

Please run these tests and report back the results

1. SFC /scannow to check windows for corruption - Use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7
2. Disk check for errors on the hard drive - Check a drive for errors
3. Troubleshoot applications by a clean boot - How to perform a clean boot to troubleshoot a problem in Windows 8, Windows 7, or Windows Vista
4. Ram test with Memtest86+ - https://www.sysnative.com/forums/hardware-tutorials/3909-test-ram-memtest86.html#post28391
5. Hard drive test from HDD mfg website - Hard Drive Diagnostic Procedure


Update or reinstall this driver: Intel(R) 82579V Gigabit Network Connection driver Driver Reference Table

BSOD SUMMARY

Debug session time: Sat Apr 27 03:34:55.579 2013 (UTC + 6:00)
Loading Dump File [C:\Users\Koolkat77\SysnativeBSODApps\042913-24148-01.dmp]
Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
System Uptime: 0 days 5:37:25.934
Probably caused by : pci.sys
BugCheck 9F, {3, fffffa80070c2060, fffff80000b9c3d8, fffffa800d036160}
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000009F]DRIVER_POWER_STATE_FAILURE (9f)[/url]
Bugcheck code 0000009F
Arguments: 
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80070c2060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800d036160, The blocked IRP
BUGCHECK_STR:  0x9F
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0x9F_3_e1c62x64_IMAGE_pci.sys
MaxSpeed:     3400
CurrentSpeed: 3392
BiosVersion = A12
BiosReleaseDate = 01/10/2013
SystemManufacturer = Dell Inc.
SystemProductName = OptiPlex 9010
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

[justinds89]

I appreciate the response. I have already reinstalled the driver as stated. I am considering just reinstalling/setting up this pc as it would take far less time and trouble than going through all that to be honest. I was just curious on what others thoughts may be on the given situation. Thanks again for your time and response.

 

[satrow]

I just dug a little more into the dump, it does point to the network card/driver, although that could easily be triggered by security software (Norton looks to be 1 version out of date?) or incorrect network card/Windows Power saving settings. We really need further dumps and related data collection to check (see https://www.sysnative.com/forums/bs...d-posting-instructions-windows-8-7-vista.html).

BugCheck 9F, {3, fffffa80070c2060, fffff80000b9c3d8, fffffa800d036160}

*** WARNING: Unable to verify timestamp for e1c62x64.sys
*** ERROR: Module load completed but symbols could not be loaded for e1c62x64.sys
Probably caused by : e1c62x64.sys

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

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

DRIVER_POWER_STATE_FAILURE (9f)
A driver is causing an inconsistent power state.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa80070c2060, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, Functional Device Object of the stack
Arg4: fffffa800d036160, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IRP_ADDRESS:  fffffa800d036160

DEVICE_OBJECT: fffffa800b254050

DRIVER_OBJECT: fffffa800b276940

IMAGE_NAME:  e1c62x64.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5125ad1a

MODULE_NAME: e1c62x64

FAULTING_MODULE: fffff88006004000 e1c62x64

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

LAST_CONTROL_TRANSFER:  from fffff80002d3b8c2 to fffff80002ccbc00

STACK_TEXT:  
fffff800`00b9c388 fffff800`02d3b8c2 : 00000000`0000009f 00000000`00000003 fffffa80`070c2060 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`02cd684c : fffff800`00b9c4d8 fffff800`00b9c4d8 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c430 fffff800`02cd66e6 : fffffa80`0af09c58 fffffa80`0af09c58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`02cd65ce : 0000002f`238479cb fffff800`00b9cb18 00000000`0013cd90 fffff800`02e4a488 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`02cd63b7 : 0000000f`9db053c4 0000000f`0013cd90 0000000f`9db053b8 00000000`00000090 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`02cc390a : fffff800`02e46e80 fffff800`02e54cc0 00000000`00000002 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cc40 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cc00 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

FAILURE_BUCKET_ID:  X64_0x9F_IMAGE_e1c62x64.sys

BUCKET_ID:  X64_0x9F_IMAGE_e1c62x64.sys

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

0: kd> !irp fffffa800d036160
Irp is active with 4 stacks 3 is current (= 0xfffffa800d0362c0)
 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
 [  0, 0]   0  0 00000000 00000000 00000000-00000000    

			Args: 00000000 00000000 00000000 00000000
[B]>[/B][ 16, 2]   0 e1 fffffa800b254050 00000000 fffff80002f18200-fffffa80068da4e0 Success Error Cancel pending
	       [B]\Driver\e1cexpress[/B]	nt!PopSystemIrpCompletion
			Args: 00015400 00000000 00000005 00000003
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa80068da4e0    

			Args: 00000000 00000000 00000000 00000000