I am using Avast! Pro 5.1 with Windows 7 and I get a systematic crash when launching a program which runs on 8 threads, each thread executing another .exe file.
The errors I can encounter are either:
SYSTEM_SERVICE_EXCEPTION
BAD_POOL_CALLER
complete freeze and I have to reboot
It seems that the problem only happens when using an Intel Core i7.
According to the minidumps and WinDbg.exe, the errors appear in aswSnx.SYS (for which I don’t have the symbols), and adding the directories that contain the concerned files to the “exclusion” category in Avast!'s Files Agent prevents the crashes from happening, so that I definitely think the problem comes from Avast!.
Please, zip and upload the C:\Windows\Memory.dmp file to this anonymous ftp server and name it uniquely: ftp.avast.com/incoming. Avast will analyze it and respond back to you in this thread or to your email. Thank you.
Actually I got an answer from Petr Kurtin, and I will try to isolate the problem and send it to him.
BTW, sorry for not having done it yet, I have been pretty busy today ^^.
I have the same BSOD problem with aswSnx.SYS. XP SP3 running the latest 6.0.1044 Avast Free, usually hangs when browsing but has sometimes done it when sat on the desktop. AMD X2 processor.
Memory dump uploaded to the FTP site - stu_allen_memory_dump.zip
As it was the same problem i thought it should go in the same thread rather than cluttering up the place.
I turned off auto sandbox.
Its happened 1-2 times per day since upgrading to V6 Avast.
Just this version.
Upgrade to v6, and then did another upgrade to the latest pre-release version in the failed hope that it would fix the issue. This seems to be happening with other people aswell!
Previous AV was AVG, uninstalled using add/remove programs. Had MS antispyware, uninstalled using add/remove programs.
Just the upgrade to Avast.
Dump from this morning uploaded : stu allen 3rd april MEMORY.zip
In the interim i seem to have circumvented the issue so am posting for the many other people with the same problem until Avast get around to fixing it.
I had auto sandbox turned off, so there shouldnt be any reason for aswsnx.sys to be accessed in any case, so i rebooted into safe mode, found the file in c:/windows/system32/drivers and renamed it. Reboot normally and my PC hasnt BSOD’ed since.
I guess this may need to be repeated for every program update that Avast do until this is fixed.