My first post I really like Avast and been using it for years, thanks for the great free protection!
Ever since I updated to free version 9.0.2011 I started to see BSODs about once day. It’s always the same in the following stack:
Looking at the registers and assembly it seems aswSnx is passing a bad pointer to the compare function.
I have a kernel dump if needed, but was wondering if this bugcheck is known and if there’s a patch/fix.
I have the same thing… just had one right now and had one a couple of days ago within moments of updating to 2011 and NEVER had one on this computer before.
Would it be possible for someone from Avast to address this ASAP? Though Im very patient and will put up with bugs and glitches, crashing my computer is a big no no and will cause data loss and possible hardware damage and if this will take weeks to fix then I will have to install something else which I really dont want to do. Thanks
Question… have either of you tried a repair install of Avast? What about a clean install?
Whatever the cause of your problems may take time plus more information from you to solve, if it is indeed Avast and not something else on your system triggering this bad response in Avast. I am running Win 7 x64, SP1, with Avast IS 9.0.2011, and even through the beta tests previous to this, have never had a BSOD, let alone one caused by Avast. So what on your system is different? What are you running beside Avast? How about other security software? And of course, have you tried either of the two suggestions I began with, both of which have been known to correct strange, system-specific, problems.
I’ve done a repair… not a clean install. I’ve had this computer for 4 years and never once had a BSOD. This started the day I updated to 2011… almost immediately after the first reboot and I’ve now had it happen multiple times. As the other person advises so has he. As far as security… winpatrol, malwarebytes.
IE11 (AOS is off), Nvidia graphics, citrix, snag it are the only things always on per se.
As far a clean install… this has become very unfortunate, but in the 6-7 years that I’ve had Avast, I have never had a single problem with Avast’s software and never had any reason to come into this forum. Now since 2014 was released in the last month or so, I have spent so much time on here looking for answers that it has just become sad. If I go to the point of a clean install then seriously I may as well look elsewhere along with the multitudes of other folks that have stated they are leaving as well. At least until they get this thing tamed.
Speaking of which… the only thing I did differently on this install was remove all the extra bloatware that’s added during the custom install whereas previously I used to just add it…
If siquad verifies that installing WITHOUT all the extras is what he did… that would be my first guess as to what the problem is… something is looking for something that isn’t there.
I’ve uninstalled->cleaned->reinstalled yesterday before seeing the latest replies and, like dprout69, went with custom install and disabled the extras (and auto program update). No BSOD so far but it’s only been a day. I’ll give it a couple more days and report back. Must say that i’m disappointed with lack of response from an avast associate on a system crash.
if it is indeed Avast and not something else on your system triggering this bad response in Avast
That said, the issue is a clear bug, some condition leads to passing a bad pointer to compare, even if that’s exposed by an external input, not less of a bug. if I had symbol files for aswSnx I’d point out the file and line number (I work in this area). As I offered, I have a kernel dump if avast is interested, not mini dump, which is all you need as a (decent) developer to see what triggered the issue.
Hi, thanks for your report. Can you please upload your kernel dump somewhere? I found the place where this driver crashed thanks to your callstack (someone returned invalid unicode string name from kernel mode, NtQueryObject/ObjectTypeInformation) – this code didn’t change for ages, so it must be the 3rd party incompatibility issue and I’d like to see kernel dump to find out what it is. Thanks!
PK, let me know how i can send you a link to the dump, apparently I can’t send private messages yet.
I’ve been lazy and ignored these bsods since my last post, one just caught me in the wrong mood
thanks, for me sandbox shows (?) when I go to change the installation. I’m not sure if it’s installed. In my last re-install that I mentioned earlier in this thread, I went with bare minimum, but it’s been months and I can’t remember if I did anything with sandbox then.
Just my opinion but if it was me, & I had BSODs, I’d do a clean uninstall and re-install.
Here is complete how-to thread: http://forum.avast.com/index.php?topic=143284.0
During the “install” use Custom…this way your are sure.
At that point up to you but others have suggested to replace the Sandbox function with hardened mode…if so…set to “aggressive”…see attached.
I really like Avast and been using it for years, thanks for the great free protection!