STOP 0x50 in aswsp.sys

Yesterday when starting up the computer, I had a similar issue to http://forum.avast.com/index.php?topic=40032.0 (old topic). I booted into safe mode, uninstalled avast, then rebooted normally. I then reinstalled avast, and rebooted again. So far, that seems to have fixed it. I just thought you should be aware of the issue. OS is Vista SP1 x64. Here’s the debugging information from the minidump:


Microsoft (R) Windows Debugger Version 6.9.0003.113 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\Mini051809-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 Server 2008 Kernel Version 6001 (Service Pack 1) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6001.18145.amd64fre.vistasp1_gdr.080917-1612
Kernel base = 0xfffff800`01c0c000 PsLoadedModuleList = 0xfffff800`01dd1db0
Debug session time: Mon May 18 19:39:55.125 2009 (GMT-4)
System Uptime: 0 days 0:00:11.921
Loading Kernel Symbols
................................................................................
............................................
Loading User Symbols
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff882009b872e, 0, fffffa6003ef67cd, 5}

Unable to load image 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

Could not read faulting driver name
Probably caused by : aswSP.SYS ( aswSP+77cd )

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

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

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff882009b872e, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffffa6003ef67cd, If non-zero, the instruction address which referenced th
e bad memory
        address.
Arg4: 0000000000000005, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80001e35080
 fffff882009b872e

FAULTING_IP:
aswSP+77cd
fffffa60`03ef67cd 66833c4300      cmp     word ptr [rbx+rax*2],0

MM_INTERNAL_CODE:  5

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  smss.exe

CURRENT_IRQL:  1

TRAP_FRAME:  fffffa6001b57740 -- (.trap 0xfffffa6001b57740)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000ffffffff rbx=fffff880001483f0 rcx=fffff880009b8730
rdx=0000077fff747920 rsi=fffffa6001b57b20 rdi=fffffa6003ef6c4a
rip=fffffa6003ef67cd rsp=fffffa6001b578d0 rbp=0000000000100050
 r8=0000000000000001  r9=00000000000006ed r10=0000000000010dc0
r11=fffff880009b8730 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
aswSP+0x77cd:
fffffa60`03ef67cd 66833c4300      cmp     word ptr [rbx+rax*2],0 ds:2000:fffff88
2`001483ee=????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80001c6f4e2 to fffff80001c61350

STACK_TEXT:
fffffa60`01b57648 fffff800`01c6f4e2 : 00000000`00000050 fffff882`009b872e 000000
00`00000000 fffffa60`01b57740 : nt!KeBugCheckEx
fffffa60`01b57650 fffff800`01c5fed9 : 00000000`00000000 fffffa60`01b57748 fffffa
60`01b57700 fffff880`009b8730 : nt!MmAccessFault+0x4f2
fffffa60`01b57740 fffffa60`03ef67cd : 00000000`00000000 fffffa60`01b57c01 000000
00`00000001 00000000`41735370 : nt!KiPageFault+0x119
fffffa60`01b578d0 00000000`00000000 : fffffa60`01b57c01 00000000`00000001 000000
00`41735370 00000000`00000000 : aswSP+0x77cd
fffffa60`01b578d8 fffffa60`01b57c01 : 00000000`00000001 00000000`41735370 000000
00`00000000 fffffa60`03ef7fe0 : 0x0
fffffa60`01b578e0 00000000`00000001 : 00000000`41735370 00000000`00000000 fffffa
60`03ef7fe0 00000000`00000000 : 0xfffffa60`01b57c01
fffffa60`01b578e8 00000000`41735370 : 00000000`00000000 fffffa60`03ef7fe0 000000
00`00000000 fffffa60`01b57ca0 : 0x1
fffffa60`01b578f0 00000000`00000000 : fffffa60`03ef7fe0 00000000`00000000 fffffa
60`01b57ca0 00000000`00100050 : 0x41735370
fffffa60`01b578f8 fffffa60`03ef7fe0 : 00000000`00000000 fffffa60`01b57ca0 000000
00`00100050 00000000`00000000 : 0x0
fffffa60`01b57900 00000000`00000000 : fffffa60`01b57ca0 00000000`00100050 000000
00`00000000 fffff880`00000000 : aswSP+0x8fe0
fffffa60`01b57908 fffffa60`01b57ca0 : 00000000`00100050 00000000`00000000 fffff8
80`00000000 fffff800`01f65aa4 : 0x0
fffffa60`01b57910 00000000`00100050 : 00000000`00000000 fffff880`00000000 fffff8
00`01f65aa4 fffffa60`01b57b20 : 0xfffffa60`01b57ca0
fffffa60`01b57918 00000000`00000000 : fffff880`00000000 fffff800`01f65aa4 fffffa
60`01b57b20 fffff880`00140210 : 0x100050
fffffa60`01b57920 fffff880`00000000 : fffff800`01f65aa4 fffffa60`01b57b20 fffff8
80`00140210 00000000`00000017 : 0x0
fffffa60`01b57928 fffff800`01f65aa4 : fffffa60`01b57b20 fffff880`00140210 000000
00`00000017 00000000`00000017 : 0xfffff880`00000000
fffffa60`01b57930 fffff800`01f97fd6 : fffff880`00140210 fffffa60`01b57901 fffff8
80`0013ced0 00000000`69634d43 : nt!CmpCallbackFillObjectContext+0x134
fffffa60`01b57960 fffff800`01f2a1af : 00000000`00000017 fffffa60`01b57b20 fffffa
60`00000000 00000000`00000017 : nt!CmpCallCallBacks+0x596
fffffa60`01b57a30 fffff800`01c60df3 : fffffa80`068bc500 00000000`0036f6f8 000000
00`00000001 00000000`00100000 : nt! ?? ::NNGAKEGL::`string'+0x28517
fffffa60`01b57bb0 00000000`00000000 : 00000000`00000000 00000000`00000000 000000
00`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13


STACK_COMMAND:  kb

FOLLOWUP_IP:
aswSP+77cd
fffffa60`03ef67cd 66833c4300      cmp     word ptr [rbx+rax*2],0

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  aswSP+77cd

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: aswSP

IMAGE_NAME:  aswSP.SYS

DEBUG_FLR_IMAGE_TIMESTAMP:  492d84bb

FAILURE_BUCKET_ID:  X64_0x50_aswSP+77cd

BUCKET_ID:  X64_0x50_aswSP+77cd

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

0: kd>

Can you please upload the minidump to ftp://ftp.avast.com/incoming ?
Thanks.

Sure, I renamed it Topic45421.dmp

Hello,
I had the same problem happening to me Today (21/5/09) and Yesterday (20/5/09).
I uploaded the 2 minidumps to ftp://ftp.avast.com/incoming:
Avi - debuglog - 20-5-09.txt
Avi - debuglog - 21-5-09.txt

What so you suggest I should do?
uninstall avast and then reinstall?

Thanks!
Avi