View Full Version : Bug? imon crashing Avast web
lynchknot
February 21st, 2005, 03:20 PM
Even though NOD32 is disabled, imon crashes Avasts' ashwebsv.exe
-{ Quote: "Fault source
------------
C:\Program Files\Alwil Software\Avast4\ashWebSv.exe caused an Access Violation at location 20b0a93b in module imon.dll Writing to location 00000008." }-
-{ Quote: "
Anyway, it's a clear bug in NOD32 - ashWebSv.exe is quite standard Windows networking application, nothink special. Imon shoulndn't be crashing anyone in any case." }- Thread: http://forum.avast.com/index.php?topic=11345.0
lynchknot
February 22nd, 2005, 03:13 PM
Again, thanks for your help. That's what makes this a great forum - such knowledgeable members always willing to extend a helping hand. ::)
Here's another great thread I must thank you for: http://www.wilderssecurity.com/showthread.php?p=381098#post381098
ronjor
February 22nd, 2005, 03:28 PM
-{ Quote: "Even though NOD32 is disabled, imon crashes Avasts' ashwebsv.exe
Thread: http://forum.avast.com/index.php?topic=11345.0" }-
Uninstall and reinstall NOD without Imon.
I'm sure you know NOD recommends removing ANY other antivirus before installing NOD.
As an experiment, I have had four other antiviruses installed in on demand mode alongside NOD with no problems.
There are a couple of antivirus programs where this scenario won't work and will cause your computer to crash.
lynchknot
February 22nd, 2005, 03:50 PM
Thanks - finally a response after 65 views. I only had both installed because others here said there was no conflict - well, there was no conflict until Avast updated. Of course, Avast is saying, "it's a clear bug in NOD32"
ronjor
February 22nd, 2005, 03:58 PM
-{ Quote: ""it's a clear bug in NOD32"" }-
I'll let the programmers reply to that statement. :D
vlk
February 22nd, 2005, 04:07 PM
-{ Quote: " ...Of course, Avast is saying, "it's a clear bug in NOD32"" }-
"Of course", lynchknot. :)
Well IMON works as a hook (LSP) that injects its DLL to each networking [winsock] app (well technically not injects, it is injected automatically by the winsock layer). But if it crashes, it's a bug - no matter if the host application is a tiny ping program, huge database server or (say) avast WebShield..
That's just my oppinion, of course. ;)
BTW lynchknot I believe that for the Eset guys to solve the problem it would be helpful to have the crash dump files avast generated.
Or maybe I could communicate it with the folks @Eset myself, I know them pretty well...
Thanks
Vlk
lynchknot
February 22nd, 2005, 04:21 PM
hehe, I did not mean, "of course" sarcastically.
Crash dumps were sent: http://forum.avast.com/index.php?topic=11345.msg96582#msg96582
Marcos
February 22nd, 2005, 04:47 PM
No probs here, but I'm curious as to why to have Avast's web checker running given that IMON's HTTP scanner gets files in the first place. Having two scanners running at Winsock level is likely to result in issues. That's probably the same like having two resident protections running at a time.
lynchknot
February 22nd, 2005, 04:50 PM
wasn't running IMON - and there were no problems running both as resident - only prob. with ashweb.
vBulletin® Copyright ©2000-2012, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2012, Wilders Security Forums