Ashserv.exe - application error {fixed}

[DavidR]

This is very strange and the first case I have seen on the forums where the usual culprit another AV once removed resolves the issue. For it to also effect other AVs I'm really baffled as to what it could be.

Whilst I have had no issue with outpost pro, that really is the only common denominator other than your OS. Are you using the anti-spyware plug-in in OP Pro, if so I would suggest you disable it and see if that makes any difference.

Before you posted the windows event log entry for this, if you can go to the latest one and see if clicking the for more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp link and see if it does produce more and perhaps more helpful information.

[Nogard]

This is very strange and the first case I have seen on the forums where the usual culprit another AV once removed resolves the issue. For it to also effect other AVs I'm really baffled as to what it could be.

Whilst I have had no issue with outpost pro, that really is the only common denominator other than your OS. Are you using the anti-spyware plug-in in OP Pro, if so I would suggest you disable it and see if that makes any difference.

Before you posted the windows event log entry for this, if you can go to the latest one and see if clicking the for more information, see Help and Support Center at go.microsoft.com/fwlink/events.asp link and see if it does produce more and perhaps more helpful information.

I turned off the anti spyware program for outpost and still have the error. I clicked on the link in the event veiwer and got this:
 
 
Details
Product: Windows Operating System
ID: 7034
Source: Service Control Manager
Version: 5.2
Symbolic Name: EVENT_SERVICE_CRASH_NO_ACTION
Message: The %1 service terminated unexpectedly. It has done this %2 time(s).
   
Explanation
The specified service could not continue. This service is configured to report the number of failures and, after a specific number of failures are reported, the Service Control Manager will perform the recovery action configured for the specified service.
 
   
User Action
For information that can help you identify possible causes for this error, view the WIN32_EXIT_CODE error that SCM encountered. To view the error, at the command prompt, type
sc query service name
 
 
 
I did what it said to do but I get an error saying " the specified services does not exist as a service."

[Vlk]

Nogard,

usually, when a program (or a system service) crashes, a "minidump" file is generated. This file contains detailed information about what actually took place, and can help us analyze the problem. To that end, it would be really useful to get your minidump files corresponding to these crashes.

Unlike in case of "blue screens" (whole system crashes), application-level crashes are not saved (i.e. are deleted as soon as the program terminates). Now, it remains to find out how to capture the dumps we're interested in. Unfortunately, this is not too easy because the procedure depends on your configuration.

What usually works is to run a program called drwtsn32.exe (integral part of Windows). Configure the paths where dump files should be saved (or leave the default locations). Next, simulate the problem (i.e. start the service and let it crash). This should cause a dump file to be generated in the path configured in DrWtsn32. If that's the case, just ZIP the dump and upload it to our ftp server (as described here): http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=18

Once the dump's ready, or you have problems generating it, please get back to us.

Thanks
Vlk

[Nogard]

Nogard,

usually, when a program (or a system service) crashes, a "minidump" file is generated. This file contains detailed information about what actually took place, and can help us analyze the problem. To that end, it would be really useful to get your minidump files corresponding to these crashes.

Unlike in case of "blue screens" (whole system crashes), application-level crashes are not saved (i.e. are deleted as soon as the program terminates). Now, it remains to find out how to capture the dumps we're interested in. Unfortunately, this is not too easy because the procedure depends on your configuration.

What usually works is to run a program called drwtsn32.exe (integral part of Windows). Configure the paths where dump files should be saved (or leave the default locations). Next, simulate the problem (i.e. start the service and let it crash). This should cause a dump file to be generated in the path configured in DrWtsn32. If that's the case, just ZIP the dump and upload it to our ftp server (as described here): http://support.avast.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=18

Once the dump's ready, or you have problems generating it, please get back to us.

Thanks
Vlk

Do you want the log file or the user.dmp?

[Vlk]

user.dmp.

[Nogard]

OK I zipped it but where do I send it to? I can't upload it to the awill ftp site. There is none

[igor]

There is - ftp://ftp.avast.com/incoming
There are no read/listing rights there, so you won't see anything in that folder (not even the file you upload), but we'll get it. I suggest to rename the ZIP file to a unique name before uploading it (random, or something containing your nick, or something like that).

[Nogard]

Thanks, I did it.

[Nogard]

I'm going to try to re-install Avast again one more time. It don't work, I'm done with it.

I fixed the problem. It was OutPost Firewall that was causing all the problems. Anyone know how to install outpost without having this problem? 

[DavidR]

Well you didn't say what it is in Outpost that is the problem so I haven't any idea how to bypass the problem. I'm not suffering the same issues with outpost pro 4.0.1025.7828 (700).

I assume by fixed you mean you have uninstalled outpost.

I would suggest downloading the latest version of outpost and with avast already installed then install the latest version.

[Nogard]

Well you didn't say what it is in Outpost that is the problem so I haven't any idea how to bypass the problem. I'm not suffering the same issues with outpost pro 4.0.1025.7828 (700).

I assume by fixed you mean you have uninstalled outpost.

I would suggest downloading the latest version of outpost and with avast already installed then install the latest version.

OH, I just uninstalled Outpost Firewall and and it worked. So I just reinstalled Outpost firewall and it works fine. I'm not sure what was blocking it.

[DavidR]

Often there is no apparent reason why but a clean reinstall often sorts out many of these unknown issues.