View Single Post
22 Nov 2012  
koolkat77

Microsoft Community Contributor Award Recipient

Windows 7 Home Premium 64Bit
 
 

Welcome to SevenForums.

It looks like Avast! antivirus is creating the problems itself.

Code:
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 88db3d2b, aba27600, 0}

*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.SYS
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
Probably caused by : aswSnx.SYS ( aswSnx+22d93 )

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

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

KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 88db3d2b, The address that the exception occurred at
Arg3: aba27600, Trap Frame
Arg4: 00000000

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
fltmgr!FltpProcessOperationStatusCallbacks+25
88db3d2b ff7718          push    dword ptr [edi+18h]

TRAP_FRAME:  aba27600 -- (.trap 0xffffffffaba27600)
ErrCode = 00000000
eax=aba276e8 ebx=00000000 ecx=00000000 edx=00000012 esi=c00000b5 edi=00000000
eip=88db3d2b esp=aba27674 ebp=aba2769c iopl=0         nv up ei ng nz na po nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010282
fltmgr!FltpProcessOperationStatusCallbacks+0x25:
88db3d2b ff7718          push    dword ptr [edi+18h]  ds:0023:00000018=????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x8E

PROCESS_NAME:  AvastSvc.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 88db8220 to 88db3d2b

STACK_TEXT:  
aba2769c 88db8220 aba276e8 00000000 8622da28 fltmgr!FltpProcessOperationStatusCallbacks+0x25
aba276c8 88db83cb aba276e8 00000000 00000000 fltmgr!FltpLegacyProcessingAfterPreCallbacksCompleted+0x2be
aba27700 8368bc29 8622da28 85540b10 85540b10 fltmgr!FltpDispatch+0xc5
aba27718 8371a126 adb35038 84bb4a44 00000fff nt!IofCallDriver+0x63
aba27734 838db24d adb35038 adab8d48 aba27850 nt!IoPageRead+0x1f5
aba2788c 8387ad47 adb35038 00000000 00000002 nt!MiCreateImageFileMap+0x11e
aba279c0 8387a1db aba27a14 0000000f 00000000 nt!MmCreateSection+0x62f
aba27a34 8e25ad93 0c25d2e8 0000000f 00000000 nt!NtCreateSection+0x16e
WARNING: Stack unwind information not available. Following frames may be wrong.
aba27cb4 8e25b068 00000013 0c25d2e8 0000000f aswSnx+0x22d93
aba27ce0 8ee2fda8 0c25d2e8 0000000f 00000000 aswSnx+0x23068
aba27d10 836928fa 0c25d2e8 0000000f 00000000 aswSP+0x25da8
aba27d10 77907094 0c25d2e8 0000000f 00000000 nt!KiFastCallEntry+0x12a
0c25d2fc 00000000 00000000 00000000 00000000 0x77907094


STACK_COMMAND:  kb

FOLLOWUP_IP: 
aswSnx+22d93
8e25ad93 ??              ???

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  aswSnx+22d93

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSnx

IMAGE_NAME:  aswSnx.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  5090582a

FAILURE_BUCKET_ID:  0x8E_aswSnx+22d93

BUCKET_ID:  0x8E_aswSnx+22d93

Followup: MachineOwner
---------
Uninstall Avast! and replace with Microsoft security essentials (To Test)
Run Disk Check on your hard disk for file system errors and bad sectors on it:Let us know if the stability returns.
My System SpecsSystem Spec