Crashed during Sleep, possible BSOD

Alextkexichi · 10 Aug 2011

Recently (approx 2 weeks old), fresh reinstall of Windows 7:

Put the computer to "Sleep' night of 8/8, gone all day on 8/9, attempted to wake computer up on 8/10. Had to press power button to start computer. Greeted with message saying "Windows has recovered from an unexpected shutdown"

This has happened at least one other time. I've run the Windows repair prior to booting into Windows 7 so it has not solved the problem. I submit this for assistance to help iron this out, because it's beyond me.

System specs can be found in my profile.
Zip file, per thread sticky has been attached.

Thanks!

Alextkexichi · 12 Aug 2011

Interesting twist on this situation: Put computer to sleep last night, woke up this morning and it was on, however it was unresponsive and nothing would show up on the screen. I've attached the file, per the forum sticky instructions.

FredeGail · 12 Aug 2011

Hello Alextkexichi & Welcome to SevenForums!

Have tried running a SFC /SCANNOW Command - System File Checker?

Best Regards,
FredeGail

Alextkexichi · 12 Aug 2011

I just ran scannow, but I didn't see any issues.

Alextkexichi · 15 Aug 2011

Since I have ran the scan, I've experienced the same problem. I managed to snap a picture of the BSOD - Internal_Power_Error

No idea what that is supposed to indicate or what to do about it.

Please help

Thanks,

Alextkexichi · 16 Aug 2011

Since my post 23 hours ago, I've now experienced two more crashes. One was while the computer was asleep and the other was while I was generating the System Health Report. I've since completed the Report and am reposting.

Alextkexichi · 16 Aug 2011

I'm not seeing a lot of particiption and I understand we're all busy, but let me know if I'm lacking in supplying infomraiton or anything that may help me resolve this problem. I really appreciate it everyone!

Alextkexichi · 18 Aug 2011

Any help? Did I not provide enough information?

LiquidSnak · 18 Aug 2011

Turn Off Hybrid Sleep in Windows 7 — MAXIMUMpcguides – Windows 7 tips, tricks, help, and how-to guides

If you follow those instructions to disable hybrid sleep, that could be the issue here. If it's already off, or you are still experiencing the same volume of crashes, let us know and we'll try something else.

**Capt.Jack Sparrow** · 18 Aug 2011

Hello and Welcome!

Sorry for the late response!

Seems like the crash is caused by scmndisp.sys which is NDIS Filter Driver belongs to Symantec Security Drivers(Part of Symantec Norton Internet Security suite). I would recommend to uninstall it completely. Also run the the Cleanup Tool from Symantec's Website. Download and run the Norton Removal Tool to uninstall your Norton product | Norton Support

Code:

BugCheck A, {0, 2, 1, fffff80002ee36ec}

Unable to load image \SystemRoot\system32\DRIVERS\scmndisp.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for scmndisp.sys
*** ERROR: Module load completed but symbols could not be loaded for scmndisp.sys
Probably caused by : scmndisp.sys ( scmndisp+16d1 )

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

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000001, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80002ee36ec, address which referenced memory

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


WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff8000310e100
 0000000000000000 

CURRENT_IRQL:  2

FAULTING_IP: 
nt!KeWaitForSingleObject+13c
fffff800`02ee36ec f00fba2e07      lock bts dword ptr [rsi],7

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xA

PROCESS_NAME:  System

TRAP_FRAME:  fffff880009e7e50 -- (.trap 0xfffff880009e7e50)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000002c5845 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002ee36ec rsp=fffff880009e7fe0 rbp=0000000000000000
 r8=fffff78000000008  r9=0000000000000000 r10=0000000000000000
r11=fffff80003051e80 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KeWaitForSingleObject+0x13c:
fffff800`02ee36ec f00fba2e07      lock bts dword ptr [rsi],7 ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002edb1e9 to fffff80002edbc40

STACK_TEXT:  
fffff880`009e7d08 fffff800`02edb1e9 : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000001 : nt!KeBugCheckEx
fffff880`009e7d10 fffff800`02ed9e60 : fffffa80`159635d0 00000000`00000001 fffff880`009e7ef0 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff880`009e7e50 fffff800`02ee36ec : 00000000`00000000 fffff880`0412819a 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x260
fffff880`009e7fe0 fffff880`0143c992 : 00000000`00000000 fffffa80`00000000 fffffa80`14bf7700 fffff800`02ed1e00 : nt!KeWaitForSingleObject+0x13c
fffff880`009e8080 fffff880`0187d6d1 : 00000000`00000000 fffffa80`0f02b0d0 00000000`00000000 00000000`00000000 : ndis!NdisWaitEvent+0x32
fffff880`009e80c0 00000000`00000000 : fffffa80`0f02b0d0 00000000`00000000 00000000`00000000 fffff880`013f63e0 : scmndisp+0x16d1


STACK_COMMAND:  kb

FOLLOWUP_IP: 
scmndisp+16d1
fffff880`0187d6d1 ??              ???

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  scmndisp+16d1

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: scmndisp

IMAGE_NAME:  scmndisp.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  45add4b3

FAILURE_BUCKET_ID:  X64_0xA_scmndisp+16d1

BUCKET_ID:  X64_0xA_scmndisp+16d1

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