Solved BSOD: STOP: 0X0000008E crash dump

[leejay99]

Hi,

I have an eMachines laptop running Win7 Home 32-bit and get the BSOD every time I boot it up, unless I go into Safe Mode. Here is the dump file:

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Master\desktop\032213-22729-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.18044.x86fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0x82c07000 PsLoadedModuleList = 0x82d504d0
Debug session time: Fri Mar 22 11:29:20.596 2013 (UTC - 4:00)
System Uptime: 0 days 0:03:03.796
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\System32\Drivers\aswSP.SYS, Win32 error 0n2
*** WARNING: Unable to verify timestamp for aswSP.SYS
*** ERROR: Module load completed but symbols could not be loaded for aswSP.SYS
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000008E, {c0000005, 44005c, 9f4c669c, 0}

Probably caused by : aswSP.SYS ( aswSP+3b816 )

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

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: 0044005c, The address that the exception occurred at
Arg3: 9f4c669c, 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:
+19
0044005c ?? ???

TRAP_FRAME: 9f4c669c -- (.trap 0xffffffff9f4c669c)
ErrCode = 00000010
eax=0044005c ebx=00000000 ecx=860a6500 edx=00000000 esi=a44be120 edi=82c89f70
eip=0044005c esp=9f4c6710 ebp=9f4c6808 iopl=0 nv up ei pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206
0044005c ?? ???
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0x8E

PROCESS_NAME: wermgr.exe

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from 8f8e1816 to 0044005c

STACK_TEXT:
WARNING: Frame IP not in any known module. Following frames may be wrong.
9f4c670c 8f8e1816 00000002 10c28788 9f4c6834 0x44005c
9f4c6808 8f8b59e5 8619b6c0 00f4cee0 86b1994c aswSP+0x3b816
9f4c6838 8f8b359d 00f40000 00010000 8727c014 aswSP+0xf9e5
9f4c6b14 8f8b49a3 874988a4 8f8f1864 8619c0b0 aswSP+0xd59d
9f4c6b68 8f8d1f54 87b19bd8 00000b80 9f4c6c84 aswSP+0xe9a3
9f4c6b8c 82e75523 87b19bd8 00000b80 9f4c6c84 aswSP+0x2bf54
9f4c6bb4 82e6054e 87b19bd8 00000b80 82d48848 nt!PsCallImageNotifyRoutines+0x62
9f4c6cd4 82e603ed 86e39030 bfad6b82 00000000 nt!DbgkCreateThread+0xcf
9f4c6d20 82cb7529 00000000 770a7078 00000001 nt!PspUserThreadStartup+0xf1
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19

STACK_COMMAND: kb

FOLLOWUP_IP:
aswSP+3b816
8f8e1816 ?? ???

SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: aswSP+3b816
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: aswSP
IMAGE_NAME: aswSP.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 50334f5c
FAILURE_BUCKET_ID: 0x8E_aswSP+3b816
BUCKET_ID: 0x8E_aswSP+3b816
Followup: MachineOwner
---------

Any help would be greatly appreciated!

Thanks!!!!!

 

[koolkat77]

Welcome.

avast! Self Protection Driver Driver Reference Table - aswSP.SYS

Remove Avast! using its removal tool from here: Uninstallers (removal tools) for common antivirus software - ESET Knowledgebase and replace with Microsoft Security Essentials, Free antivirus for windows

 

[leejay99]

Thank you for your help! It works great now. Is this a problem that I am going to have with Win7 and Avast on my other computers? Is it something I did or maybe opened?

Thanks again!

 

[koolkat77]

On some systems yes, avast! does cause BSODs.