avast crashed xp pro but...

[penult]

hello. i have two machines. one with a amd800 with xp pro. I am migrating to a p2.4c machine with a asus p4p800 with hyperthreading. I have encountered 2 fatal errors that cause xp pro to stop.  Both were that avast was trying to release a resource that it did not own. ON the amd800 machine all is well. Anyone else having this error?  The file was aswmon2.sys .  :'(

[Vlk]

penult, sorry, this is a confirmed bug in the current version of avast. There is a fix availabale, though. All you need to do is update aswmon2.sys - for instructions and download links, please see my post here: http://www.avast.com/forum/index.php?board=2;action=display;threadid=694;start=msg5444#msg5444 .

Again, we apologize. Of course, the fix will be included in the next program update as well.

Hope this helps,
Vlk

[penult]

Thank you for the help and advice.  I renamed the old file and pasted the new file to the system/driver folder. As I do always with Windows,  I said the little computer prayer, "Oh God, please let this work."

[Vlk]

And....?

[penult]

It's been several hours since he change and ...  

I saw no rhyme or reason when the error would occur.  In the morning or in the afternoon, I would discover a blue screen  or it would occur while using the machine.  The error would not happen at regular intervals.  I have to wait and see.  

 

 

[Vlk]

Good. Fingers crossed...

[penult]

  i returned this afternoon and checked on my system. I tried to open Avast to check on the date of the definitions.  When I went to start/programs and clicked on Avast to open the interface, nothing happened. Well, I should say no interface or splash.  I stopped on-access protection and tried to open the interface/splash again. I got a prompt that it could not be opened.  I hit the OK button before thinking to write down the odd message that was presented.  I tried to open OE and Outlook and neither would open. I rebooted and all is well. hmmm.

I promise I will write down the exception when it happens again. It was something about insufficient components were available.  

Sorry. I won't miss it again.

[penult]

awoke to find the error aswmon2.sys error in bae7b740 base at bae7200 with date stamp 3f014b9b.  hmmm what do i do?
greg

[Vlk]

Please send me the (most recent) minidump file that was created in the \windows\minidump folder.

Have you upgraded to av4.1 or still using 4.0.235?

Vlk

[penult]

hello.
i have auto updates running and this is version 4.1home.  i have not determined how to send you the minidump file but i will look for your email address.

By the way, the other day I awoke to find a prompt on my system that Avast needed to reboot my computer. I am not sure why.  I have since this most recent STOP (blue screen) re-replaced the .sys file, just in case.

greg smith

[Vlk]

My email address is

vlk at avast dot com

Thanks,
Vlk

[penult]

you know i cant send you the dmp file as an attachment. what do i do to send you this dmp file.

greg s

[Vlk]

Got the dump, will take a look at it, thanks.

[Vlk]

Hi I checked the dump and my conclusion is that you're still using the old (4.0.235) driver. I don't know how it got there, but it's there.

Please compare the aswmon2.sys versions in \windows\system32\drivers and <avast>\setup\inf. Are they the same? If not, which is newer?

The one located in setup\inf should be the latest (it should be dated today or yesterday, depending on when you ran the update). If they're not the same, copy it to windows\system32\drivers and reboot.

Vlk

[penult]

ok will do, but cant right now. i have lots of typing to do.  Avast virus database updated and it wants to reboot the system. This doesnt happen on the other machine. Avast just updates.