I’m having trouble with avast v4.6. When I shutdown WinXP the ashserv crashes and bring up error about it couldn’t write to a praticular address in ram press ok to terminate the program. This problem occurs often when I use bittorent for long period of time. Now this doesn’t prevent XP from completely shutting down. What should I do?
My spec:
AMD athlon XP 2000+
Biostar N7CD 400 mobo
nvidia nforce2 chipset
2x 128 (256) kingston ram
Windows XP home with SP2
Western digital 30GB hdd
well I did search for this problem and found an exact match but it was related to a previous version of avast (4.5 in particular ) I am using the current version of avast and i never had this problem with the previous version.
thanks for the encourage technical. I know that the avast team is really busy so wait them to respond. This problem is a minor annoyance so I am not paniciing yet.
Upthatwey, the whole discussion here is about intermittent crashes on system SHUTDOWN (quite benign). Is your problem different? Is ashServ.exe crashing while your working on your machine?
Yes, while working. I run mailwasher and feel that it crashes (occasionally) whilst mailwasher is checking for email. Possibly also causing the system lockups.
This is a fresh install of XP Pro, Avast 4.6 and everything else.
I also have the shutdown problem. Not everytime though, but it does happen.
Hi…
This exact problem happens for me as well, but interestingly enough when i reboot i find that avast is still starting up but it is switched off…
I have to restart manually through administrative tools/services as the Avs4 control service has been disabled in startup & sometimes Avast anti-virus too.
I have virtually the same specs working on winxp sp2 , it is a minor annoyance that is easily sorted by restart & the error shutdown message doesnt seem to effect shutdown too much, has it got something to do with the auto-update not shutting down..?
(still a great piece of software tho ;) )
I too am having the crashing problem intermittently but the SLOW SLOW shutdown is really annoying. The problem started with with the last three or four beta updates (I DO NOT EXACTLY REMEBER THE NUMBER)which PROBLEM I had posted earlier.
Before that everything was JUST FINE ???
Guys, look in the \data\log folder for files named unpXXXX (XXXX is a random number). Are there any such files? If so, please send them to my email address.
Please, go to folder \windows\minidump and send the newest (recent) .mdmp files to Vlk’s email (vlk@avast.com) for further analysis.
Better if you can compress (zip) them and add some information about the BSOD and the link for this thread.