ashWebSv.exe has encountered a problem and needs to close!

[Omar]

This problem started yesterday but occasionally when I am in the middle of using the computer, I get a message which says:

"ashWebSv.exe has encountered a problem and needs to close".

I only receive this message when i`m using the computer. It does not happen on shut down!

What is going on? Can it be fixed? Does avast need to be re-installed?

[Vlk]

What OS are you using?

[Omar]

What OS are you using?

Windows XP Home Edition.

I`m using the latest version of avast, programme is up to date!

[lukor]

What OS are you using?

Windows XP Home Edition.

I`m using the latest version of avast, programme is up to date!

There should be a file called UNPxxx.mdmp (where xxx is some number) in the c:\program files\alwil software\avast4\data\log folder. Can you send me this by email?

Lukor.

[Omar]

what is your e-mail address?

[Omar]

plus I can see 9 differant "UNPxxx.mdmp"

which one do I need to send you?

[DavidR]

what is your e-mail address?

Use the email icon (envelope) in his details displayed to the left of his post.

For the time being, I would suggest that you only send the last one or possibly two that related to the web shield problem. If lukor needs more he will most likely ask.

[Omar]

the error signature is:

ashwebsv.exe


SZAPPName: ashwebsv.exe szappver: 4.6.6650    SZModName: xfilter.dll

SZmodver:    3.0.0.3644   offset: 00010d13




The "xfilter.dll" belongs to the new firewall i installed yesterday.

http://www.filseclab.com/eng/products/firewall.htm

The firewall download file which is saved on my computer as a zip file has "xfilter" written directly below it.


Could the new firewall be causing the problem? I have allowed complete access to everything from avast.

I made sure that I DID NOT block avast by mistake. Avast was granted access, i am sure of that.

The file that lukor wanted is:

 unp180292414.mdmp

I`ll-email it to him just in case!

[lukor]

:'( I don't like these: faulty LSP.

It's apparently a firewall module (the xfilter.dll), either LSP or hooking of winsock. This is the way, how they got loaded into our process and there they behave incorrectly. If you'll send me the dump file, I can have a look in which function the error occurs, but most probably I will not be able to fix it in any way (it's inside the Winsock calls where these parasites coexist) - we can both send this incident to filseclab team, hopefully they'll be willing to spend some time with it.

[Omar]

Hi Lukor,

Thanks for your assistance so far. I have just sent you in a e-mail attachment the "unp180292414.mdmp" file.

The file is zip password protected, the password is contained in the e-mail.

I am going to e-mail "filseclab" right now and report the problem, hopefully they can sort this out.

[lukor]

As I have expected, this seems like a reentrancy problem of their firewall module xfilter.dll. I've also forwarded this issue to the filseclab email. We'll see what are their comments.

Lukor.

[Omar]

Filseclab, replied to my e-mail and wrote:


"Thanks for your notification. We will test it as soon as possible and try to get a way to resolve it. thank you very much.
 
Please feel free to contact us if you have any further questions".

[Omar]

Filseclab replied as follows today:

Hi,
 
Yes, the problem has been found, we can resolve it. but, we need take some time to do because the problem is not always occurs, this is a little trouble for debug. we will resolve it as soon as possible and notify you after it resovled. thank you.
 
Best Regards,
 
Tom Liu
Filseclab > Customer Support

[DavidR]

What a pleasant change for a software company to acknowledge a problem, respond promptly and make a commitment to rectify it.

A bit like Alwil and avast! in these forums really

[lukor]

What a pleasant change for a software company to acknowledge a problem, respond promptly and make a commitment to rectify it.

Yes, really very nice and quick.