BSOD when in Sleep/Hibernate

[vinee89]

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 16393

Additional information about the problem:
BCCode: 9f
BCP1: 0000000000000003
BCP2: FFFFFA800553DBB0
BCP3: FFFFF80000B9C3D8
BCP4: FFFFFA800A73FAB0
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\090413-30264-01.dmp
C:\Users\****\AppData\Local\Temp\WER-149838-0.sysdata.xml

Read our privacy statement online:
Windows 7 Privacy Statement - Microsoft Windows

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

 

[koolkat77]

Kaspersky tends to cause bsods. Please remove it for the time being.
Microsoft Security Essentials & the Free version of Malwarebytes, update and make full scans separately:

• Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase
• Help protect your PC with Microsoft Security Essentials
• Malwarebytes Free

   Note

:info: Do not start the trial version of MalwareBytes

You may also take a look at:

• Good & Free System Security Combination

------------------------
Reduce the start-up items, Antivirus software is basically whats required.

• Remove Startup Programs in Windows 7
• Clean Startup in Windows 7

------------------------
Run the System File Checker that scans the of all protected Windows 7 system files and replaces incorrect corrupted, changed/modified, or damaged versions with the correct versions if possible:

• Click on the rb:
• Type CMD on Search
• Left click and Run as Administrator
• Type SFC /scannow - read here

Run Disk Check on your Hard Drive for file system errors and bad sectors on it - read here
Let us know the results.

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

Use !analyze -v to get detailed debugging information.

BugCheck 9F, {3, fffffa800553dbb0, fffff80000b9c3d8, fffffa800a73fab0}

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: fffffa800553dbb0, Physical Device Object of the stack
Arg3: fffff80000b9c3d8, nt!TRIAGE_9F_POWER on Win7, otherwise the Functional Device Object of the stack
Arg4: fffffa800a73fab0, The blocked IRP

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


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAULTING_MODULE: fffff88006441000 ndiswan

DEVICE_OBJECT: fffffa8008d71050

DRIVER_OBJECT: fffffa8008d63a70

IRP_ADDRESS:  fffffa800a73fab0

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`00b9c388 fffff800`0353c092 : 00000000`0000009f 00000000`00000003 fffffa80`0553dbb0 fffff800`00b9c3d8 : nt!KeBugCheckEx
fffff800`00b9c390 fffff800`034d995c : fffff800`00b9c4c0 fffff800`00b9c4c0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x34040
fffff800`00b9c430 fffff800`034d97f6 : fffffa80`0c707c68 fffffa80`0c707c68 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c4a0 fffff800`034d96de : 00000014`d3d61e9a fffff800`00b9cb18 00000000`0008bfe7 fffff800`03647f68 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9caf0 fffff800`034d94c7 : 00000004`aaf730c2 00000004`0008bfe7 00000004`aaf730b6 00000000`000000e7 : nt!KiTimerExpiration+0x1be
fffff800`00b9cb90 fffff800`034c698a : fffff800`03643e80 fffff800`03651cc0 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

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> !irp fffffa800a73fab0
Irp is active with 3 stacks 2 is current (= 0xfffffa800a73fbc8)
 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 fffffa8008d71050 00000000 fffff80003715200-fffffa8005612710 Success Error Cancel pending
	       \Driver\NdisWan	nt!PopSystemIrpCompletion
			Args: 00014400 00000000 00000004 00000002
 [  0, 0]   0  0 00000000 00000000 00000000-fffffa8005612710    

			Args: 00000000 00000000 00000000 00000000