ashMaiSv crashes

system · 2007-02-05T20:01:12.000Z

There error is the usual Windows apology for the application
crashing. It is sending something to Microsoft about the crash
which I would assume you get at some point.

This is the first time I’ve installed Avast4 and it is on a brand
new machine. There is no ashMaiSv application running
which is what I would expect from the crash message.

Internet Mail has no scanned files. The count is 0 and there is nothing
after the Last scanned: item.

DavidR · 2007-02-05T20:24:18.000Z

I don’t know if MS would bother sending anything to Alwil Software somehow I doubt it.

Secondly I’m just and avast user like you.

Did you send the unpSOMETHING.mdmp to vojtech if it exists ?
This could help in tracking the problem.

There may also be more information in the windows event viewer, application or system logs, you could paste that here.

system · 2007-02-05T22:37:49.000Z

I did send the dump files but didn’t see anything
special in the event log other than that ashMaiSv
had crashed.

DavidR · 2007-02-05T23:23:47.000Z

But what was the complete text of the event log entry, it may give some additional information.
Does this happen on every boot or haven’t you rebooted since the crash ?

I guess we will have to see what comes of the mdmp file.

What other avast processes are running, they begin with ash or asw ?
It may be that this extends further than just the email scanner.

system · 2007-02-06T00:06:17.000Z

ashDisp.exe
ashServ.exe
ashWebSv.exe
aswUpdSv.exe

are the relevant apps that are running.
The event log is:
"Faulting application ashMaiSv.exe, version 4.7.936.0, faulting module vlsp.dll, version 1.0.0.1, fault address 0x00007510.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp."

It happens every time I reboot.

Dave

system · 2007-02-06T00:29:54.000Z

Well I stopped the mail scan service from avast (which
actually wasn’t running). Then I started it up from
avast and it now seems to be running. Perhaps
the crash is associated with not everything in the
system being up when it starts up on a reboot?

system · 2007-02-06T00:31:57.000Z

Well I spoke a little too soon. I came up and seemed
to be checking email and then it crashed as before.

DavidR · 2007-02-06T00:41:32.000Z

The event log is: "Faulting application ashMaiSv.exe, version 4.7.936.0, faulting module vlsp.dll, version 1.0.0.1, fault address 0x00007510.

That is what I was after the faulting application may be tagged as ashMaiSv.exe but the real culprit is the faulting module vlsp.dll that as far as I’m aware in and avast dll.

A google search for vlsp.dll returns many hits, http://www.google.com/search?q=vlsp.dll some relating to a wireless card, do any of them ring any bells, if so you could try to update the software/vlsp.dll

http://www.greatis.com/appdata/a/v/vlsp.dll.htm
http://www.castlecops.com/lsp-73.html

A forum search for vlsp.dll also returns a couple of hits, other than yours.
http://forum.avast.com/index.php?topic=22768.msg189752#msg189752
http://forum.avast.com/index.php?topic=18324.msg155944#msg155944

system · 2007-02-06T03:38:16.000Z

Well then the problem is related to the Venturi software. I’m a Verizon customer and use the Motorola Phone Tools to connect to my V3C telephone to manage the phone directory and related items on the phone. I really don’t want to remove that application as it is quite useful to me. So I need to see how I can use Avast and the Motorola software. I don’t understand how or why the two are related.
That software is fully updated, so I’m not sure how to get a better version.

DavidR · 2007-02-06T13:00:06.000Z

It certainly look that way, I don’t know if they have software updates for the tools and in particular the vlsp.dll.

I’m taking a swag (scientific wild a***d guess) that the v in vlsp is virtual (Label Switched Path) and somehow hook all applications connecting to the internet to monitor the traffic.
http://en.wikipedia.org/wiki/Label_switched_path

If it is what I’m thinking a process that hooks all program connecting to the internet then ashMaiSv.exe can’t avoid it, again I would be guessing that the vlsp.dll is somehow not able to handle the localhost proxy used by ashMaiSv.ex, something more common with AVs. I don’t know if there is any way to exclude processes in the phone tools so it doesn’t monitor ashMaiSv.exe and possibly the ashWebSv.exe as that to uses the localhost proxy means of filtering content.

vojtech · 2007-02-06T14:10:36.000Z

I have built a version that ignores the vlsp.dll. How to test it:

Download http://www2.avast.com/~peterka/4.7.942/ashMaiSv.zip
unzip it and put both files to avast4 folder
start the ‘Internet Mail’ provider

Please report if it works and scans mail.

system · 2007-02-07T04:14:42.000Z

That seems to be working now. It has scanned a number
of email messages with this new version without any
errors or crashes!

system · 2007-02-19T23:12:38.000Z

I would like to report that ashMaiSv hasn’t crashed since I did this update in the previous post.

However, periodically, ashWebSv crashes on some web sites. The
Event Viewer says:

Faulting application ashWebSv.exe, version 4.7.936.0, faulting module vlsp.dll, version 1.0.0.1, fault address 0x00007510.

So it looks like the vlsp.dll is the guilty party again. I can restart ashwebSv and it usually runs fine after that. This has occurred a couple of times, but I thought you ought to know. Perhaps a similar fix as for ashMaiSv?

DavidR · 2007-02-20T00:07:18.000Z

This is the problem, faulting module vlsp.dll, this isn’t an avast file but something that hooks all LSP connections.

As for your other post relating to this perhaps it is time to try and remove the vlsp.dll from equation again.

vojtech post:14:

I have built a version that ignores the vlsp.dll. How to test it:

Download http://www2.avast.com/~peterka/4.7.942/ashMaiSv.zip

unzip it and put both files to avast4 folder

start the ‘Internet Mail’ provider

Please report if it works and scans mail.

The problem may have been cause by a program update, to forced a program update to version 4.7.942, if did didn’t have this version, the update may have undune the above work around. Nether the less trying it again shouldn’t hurt.

Either that or you are going to try and see about updating your wireless software, http://forum.avast.com/index.php?topic=26475.msg216435#msg216435.

system · 2007-02-20T00:19:07.000Z

I don’t think your analysis applies. I’ve had no problem with the ashMaiSv application since
I updated the program from the zip file. I’m reporting on a less frequent crash of the ashWebSv
application apparently caused by vlsp.dll. I don’t have the option of removing vlsp.dll since
I want to use my cell phone with my computer, and there is no other software option that
I’m aware of that will enable me to share data with my cell phone and use it as an internet
connection from time to time. Since the problem was fixed in ashMaiSv by avoiding the use of
vlsp.dll, I would assume that a similar patch to ashWebSv would work and make life easier
for everyone.

DavidR · 2007-02-20T00:48:16.000Z

I’m not saying remove it, but update it, I assume there is a software update function, is that the latest version you are using ?
Otherwise it is something that is likely to continue to happen, less frequently with the work around, but that will almost certainly be replaced by a program update in the future. Unless the work around they gave is included in the update, possibly not, as not everyone uses vlsp.dll.

I think you should go back to the other topic and report that although the frequency of crash is reduced it is still happening.

system · 2007-02-20T00:57:05.000Z

I’ve had no crashes of ashMaiSv with the new version they gave me. I’m running
the latest version of the software plus the update. The error I’m reporting
now is that the problem is a little broader than causing ashMaiSv to crash.
It also causes ashWebSv to crash occasionally.

DavidR · 2007-02-20T02:10:29.000Z

Yes, the problem is basically the same, faulting module vlsp.dll, web shield makes a connection and is hooked by vlsp in the same way as ashmaisv.exe was.

Hopefully this new activity in the topic will be noticed by one of the Alwil team, it may prompt them to do the same with a work around for the ashwebsv.exe.

system · 2007-03-13T19:57:04.000Z

I found a solution to this problem without removing the Venturi application:

http://forums.ceruleanstudios.com/showthread.php?threadid=56383:

Old 22 May 2004, 07:42 AM
There is a known issue with Venturi Wireless (the source of VLSP.DLL) and Trillian. Basically, removing the “transparency” option from Venturi solves the problem.

It can be done from Add/Remove Programs without uninstalling Venturi entirely, or it can be done by double clicking on C:\Program Files\Venturi2\SPI\Uninstall Transparency, which is just a link to “C:\Program Files\Venturi2\SPI\inst_vlsp.exe /u”.

I did this and now I don’t get crashes from vlsp.dll (which were occurring also for other applications besides avast).

DavidR · 2007-03-13T22:13:23.000Z

Thanks sticking with it and for taking the time to give us the feed back.

Announcements