Crash caused aswSnx.SYS on Win7 x64 AIS Pro

I’ve looked around this forum and found numerous references to aswSnx.SYS causing problems but none of the threads I’ve looked at offer any resolution. My Acer aspire 5740G is an iCore5 and it recently froze and had to be switched off. Avast Version is 5.1.889. looking at the minidumps and analyzing the most recent one:

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

Loading Dump File [C:\Windows\Minidump\New folder\022411-21684-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\Debug

\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff80003462000 PsLoadedModuleList = 0xfffff8000369fe50
Debug session time: Thu Feb 24 11:32:51.516 2011 (UTC + 11:00)
System Uptime: 1 days 2:28:04.061
Loading Kernel Symbols




Loading User Symbols
Loading unloaded module list



  •                    Bugcheck Analysis                                 
    


Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, 1097, 5040205, fffff8a0162729a0}

Unable to load image \SystemRoot\System32\Drivers\aswSnx.SYS, Win32 error

0n2
*** WARNING: Unable to verify timestamp for aswSnx.SYS
*** ERROR: Module load completed but symbols could not be loaded for

aswSnx.SYS
Unable to load image \SystemRoot\System32\Drivers\sptd.sys, Win32 error

0n2
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for

sptd.sys
GetPointerFromAddress: unable to read from fffff8000370a0e0
Probably caused by : aswSnx.SYS ( aswSnx+1f51f )

Followup: MachineOwner

0: kd> !analyze -v



  •                    Bugcheck Analysis                                 
    


BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a

bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 0000000000001097, (reserved)
Arg3: 0000000005040205, Memory contents of the pool block
Arg4: fffff8a0162729a0, Address of the block of pool being deallocated

Debugging Details:

POOL_ADDRESS: fffff8a0162729a0

FREED_POOL_TAG: Snx

BUGCHECK_STR: 0xc2_7_Snx

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

PROCESS_NAME: FsynSrvStarter

CURRENT_IRQL: 0

LAST_CONTROL_TRANSFER: from fffff8000360560e to fffff800034d2740

STACK_TEXT:
fffff8800c56d4a8 fffff8000360560e : 00000000000000c2 0000000000000007

0000000000001097 0000000005040205 : nt!KeBugCheckEx
fffff8800c56d4b0 fffff880040a051f : 0000000000000004 fffff800034b2872

0000000000041000 0000000000400100 : nt!ExDeferredFreePool+0x11eb
fffff8800c56d560 0000000000000004 : fffff800034b2872 0000000000041000

0000000000400100 0000000000000001 : aswSnx+0x1f51f
fffff8800c56d568 fffff800034b2872 : 0000000000041000 0000000000400100

0000000000000001 0000000000400000 : 0x4
fffff8800c56d570 fffff880010d70f8 : 0000000000000000 fffff800036814a8

0000000000000198 fffff8800c56d720 : nt!RtlImageNtHeader+0x1e
fffff8800c56d5a0 0000000000000000 : fffff800036814a8 0000000000000198

fffff8800c56d720 fffff8800c56d5f8 : sptd+0x5c0f8

STACK_COMMAND: kb

FOLLOWUP_IP:
aswSnx+1f51f
fffff880`040a051f ?? ???

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: aswSnx+1f51f

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: aswSnx

IMAGE_NAME: aswSnx.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 4d2ebac5

FAILURE_BUCKET_ID: X64_0xc2_7_Snx__aswSnx+1f51f

BUCKET_ID: X64_0xc2_7_Snx__aswSnx+1f51f

Followup: MachineOwner

I can upload the minidump file to the ftp server if required.
One site I saw tried to tell me it was spyware and tried to sell me antispyware to remove it!!!
Thanks for your kind attention to this problem.

The first thing I’d suggest would be to update to the latest version of avast! (6.0). If it is a problem in avast!, it might be already fixed there.

Thanks I’ve just applied SP1 after having a few issues with the install, just on this machine I had to disable avast and firewall, and I have just updated to v 6 Avast. Hopefully it’s fixed…
Interestingly or not, MS Security Essentials is now identifying an avast 6.0 file as suspicious and wanted to submit it to MS for eval (I unchecked this box).

please upload the minidump (or minidumps) related to the incident to ftp.avast.com/incoming
ideally compressed into archive with unique name
dump files are usually located in C:\Windows\Minidump

Hi,
unfortunately for me the same problem occurs.
I sometimes get a blue screen.
STOP: 0x000003B […]
aswSnx.sys […]

Here is the minidump.
http://ge.tt/5YdQgFY

Can you to do something and solve the problem?

Best regards,
Georg

Please upload minidump to : ftp.avast.com/incoming (just type that into adress bar of Windows 7 Explorer and drag the file there)

What Avast version are you running? AIS 6.0.1091?

Sorry, my version was 6.0.1.
I’ve now updated.
Have the file but still sometimes pushed to the FTP.

Is your problem solved with 6.0.1091?

Try the latest beta to solve.
http://forum.avast.com/index.php?topic=77580.msg642267#msg642267