aswUpdSv.exe - application error / Windows XP Pro / Avast Home edition

I wonder if anyone can help with a strange problem of mine.

When I go to shutdown Windows XP Pro after playing Call Of Duty multiplayer (I can’t comment on single player as I don’t play it) after around an hour or so I get the following error box popping up during the blue ‘shutting down’ screen:

aswUpdSv.exe - Application error

The instruction at “0x77e79575” referenced memory at “0x0000003c”. The memory could not be “read”.

Click on ok to terminate the program.
Click on CANCEL to debug the program.

Without any further user intervention by me the comp continues to shut down normally, after a few seconds.
This has only started occurring after I completed a fresh install of Windows XP Pro updating it to Service Pack 2.
Is there any chance of an incompatibility between Windows XP Service Pack 2 / Avast Home Edition and / or Call of Duty?

I have only seen this error after playing Call of Duty otherwise Avast performs flawlessly with Win XP Pro and Service pack 2 and I have recommended Avast to many of my friends.

My comp specs are:

Windows XP Pro Service pack 2 plus all the latest update, AMD Barton XP2500, 512Mb DDR Ram, Avast Home Edition.

The usual Google searches have come up with very little information.

Many thanks in advance. ;D

Just one question? is that game a 16 program?
Welcome to the forum.
Take a look HERE and see if this answers your question.
Please post back here to let us know. Thanks

Hi Bob,

Thanks for the reply. The thread you directed me to appears to be programs having difficulty installing with SP2 and making registry changes to Avast.
As the problem i’m having is completely different to the ones outlined in the thread i’m reluctant to try the fixes. :stuck_out_tongue:

I don’t think Call of Duty is a 16 program as it only came out last year but it is known to be notoriously hard on computer systems. Prior to this problem I had Windows XP Pro with SP1 and all the latest patches and Call of Duty would randomly restart my comp after about an hours gaming. I’ve seen other gamers reporting this behaviour also.

I’m a little confused as to why it would cause a conflict with Avast though and specifically, the aswUpdSv.exe file. What does this file do anyway?

Any more ideas anyone?

aswUpdSv.exe (note the UPD) is the part of Avast that checks for vps and program updates. It is not a definate fix, but disabling the automatic updates in Avast when you gonna play will likely prevent the error from showing. Don’t forget to enable it again after playing and perhaps do a manual check for new releases directly after playing.

Cheers Eddy, I’ll give that a go and post the results after a few test runs of stopping the automatic updates before playing CoD online.

;D

Remember that the automatic updates checks every 4 hours by default. While testing you may want to shorten this period in avast.ini. Otherwise you would have to play for at least 4 hours to see if the error comes or not :smiley:

The slower value for update period (of Home version) is two hours (120 minutes).
Details on ‘Settings’ in my signature :wink:

Sorry about that, Guess I didn’t have my glasses on this morning.

Well. An interesting one this is!

After a few test runs i’ve come to this conclusion.

Mearly turning off automatic updates before the game is played and turning them back on after the game is exited still causes the error message to be displayed when shutting down or rebooting the computer, however.

When turning off automatic updates before the game is played and leaving it off before shutting down and rebooting the computer causes no error message.

Strange one eh?

I also see the aswUpdSv.exe error when shutting down XP Pro SP2. The error dialog only appears briefly before the computer completes the shut down process and turns off. It does not happen every time I shut down.

I would have never noticed this error if I had not been watching the screen while my computer was shutting down.

I’m not a gamer so it’s probably not related to your game.

Your post was the only one I found when doing a google search. Apparently there are not very many people seeing this error.

I just spotted it on my puter last night when I shut down.

Yes, strange one indeed. I’m glad (in a way) i’m not alone on this one although a Moderator has yet to offer any possible explanation on this thread. I haven’t seen the error message for quite some time now and it appears to have gone away, all on its own accord.

Come on Mods, any ideas?

although a Moderator has yet to offer any possible explanation on this thread.
That is not the task of a moderator. A moderator monitors the threads and make sure the board policy is followed by the posters.

Yeah but they’ve chipped in before on various threads. Just wondering if they had any thoughts. :wink:

What you’re actually looking for SuperTrooper is a reply from some one on the Alwil team.
In this case, the mods also happen to be members of that team. ;D

By the way, I’m running version 4.6.588 if that helps any.

Guys, do you think you could try out the latest beta (as described here: http://forum.avast.com/index.php?topic=10806.0 )?

Chances are it will help to resolve this issue. We’ve made some changes that should generally prevent this problem from happening.