Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Bellzemos on March 11, 2010, 05:20:04 PM
-
Hello! I've already sent you (ftp) some tmp files concerning Avast's shields going off for no reason, but got no reply. Is there any other way I can send them to you to review them and see what's the reason for this problem? Please. :)
-
Igor, Vlk...?
-
What was the exact filename you uploaded?
03/11/2010 04:25 AM 65,536 Mini031010-01.dmp
for machine OS: Windows 2000 Kernel Version 2195 (Service Pack 4) UP Free x86 compatible
if so, I guess we'll need a kernelmode dump... :-\
also please download http://public.avast.com/~kurtin/gflags.exe and enable "pool tagging" (see pic: http://public.avast.com/~kurtin/gflags.png) and reboot your machine.
Thanks.
-
hmmmm, probably it's not your minidump (you're using XP according to your signature) -- so when did you upload it? 03/07/10? can't see it there...
-
The file name is "Bellzemos-log.rar" and I've uploaded it on 24th of February.
-
I have looked at the dumps. They are, unfortunately, "heap corruption" type of problems, which are technically impossible to properly analyse from such dumps.
However, if the problem is reproducible on your system, we may try to set up a "trap".
Download the gflags utility from pk's post, and use it like this (from the command line):
gflags -p /enable AvastSvc.exe /full
Then reboot the computer, and watch for the problem to occur again.
Thanks
Vlk
-
I don't know what is "heap corruption", but nevermind. :)
When I use the gflags utility and reboot, I have to wait for the shileds to go down again and then? Will the next dump be readable or which file do I have to send you?
-
Yes, the new dump should contain more information that should lead us to the cause of the problem (hopefully).
Thanks
Vlk
-
OK, I'll do that tomorrow and then send you the dump. Thank you!
-
I did as you said: I downloaded "gflags.exe" to my C: drive (root) and enabled "pool taging".
Then I typed in as you said but with no sucess - here's what's happened:
(http://www.shrani.si/f/F/13i/22gT8jkk/jeba.jpg)
-
Perhaps you need disable the avast self-defence module first, avast Settings, Troubleshooting, try that if you didn't already do that.
-
David is right, apologies for not saying that earlier. Self defense will need to be disabled before you can use gflags on AvastSvc.exe.
Thanks
Vlk
-
Perhaps you need disable the avast self-defence module first, avast Settings, Troubleshooting, try that if you didn't already do that.
No, I didn't do that. I will try again later and post the situation here. Thank you.
-
OK, I did as you said and here's what happened:
(http://www.shrani.si/f/1G/om/1H5VU1UF/flufo.jpg)
I don't have time to sit down and wait for the shields to go down again (that's my brother's PC, I'm still using 4.8 on mine), but "gflags.exe" will check for the problems even after a 2nd or 3rd boot of the PC, right? So, when I see some files in the LOG folder (maybe tomorrow) I'll post them to you.
-
Hm, since I disabled Avast's self-defense there were no problems anymore as it seems. Should I enable it or should I wait a little more?
-
Yes you should enable the self-defence module, it was just disabled as that was needed to be able to run the gflags command.
-
If I eneble self-defense, will gflags be still able to save a log when/if an error occurs?
-
It is just the set the markers/parameters within the existing logging settings, this I believe would require that a file has to be modified (gflags -p /enable AvastSvc.exe /full) and that was what the self-defence was blocking. Or rather it was blocking the change of an avast registry key.
That is my best guess and by no means infallible.
-
So I should immediatelly turn on the self-defense, right? Thank you!
-
I believe so, after all it is a part of your defence in protecting avast against attack.
-
It seems that after the 5.0.462 update everything finaly works fine. My little brother says he's not experiencing anymore shield-disabling problems. What about you, other users who had this kind of problems, are you still experiencing them from time to time or not at all?
-
Anyone, please?
-
Not at all (fortunately).
-
That's good to read. :) I think I will upgrade from v4.8 to v5 shortly...
-
Newest version of Avast! 5.0 on my Vista Home Premium 32 Bit machine still has this problem. I remember that all versions 5.0.x I tried had this problem.
It looks like that :
-I uninstall Avast 4.8
- reebot,
- install Avast 5.0.x
- configure password for Avast, so unprivileged users cand modify settings (leaving all checkboxes at default state at password tab)
- everything works perfectly,
- than after one or two reebots (after a day or two) when computer starts avast informs that all shields are down.
- I try to enalble them by :
- using context menu by RMB clicking on Avast icon at tray,
- using shields management screen
- using START->Administration tools->Services and trying to start Avast main service
but with no success - avast tells me that there is some error, so shields can't be reenabled; service starts and in one moment stops.
I noticed that Avast is downloading and installing updates properly (at least by these one or two days).
My system specs (this is computer for my kid):
ABIT KV7 (mainboard)
AMD Sempron 2800+ (Socket A CPU)
Kingston 1,5 GB DDR (RAM)
ATI Radeon 9250 (GPU)
Windows Vista 32 Bit Home Premium.
EDIT :
oh, and one more thing - I'm using Pro version... version 4.8 of Avast works perfectly on this machine
-
I have had this issue for over six months but today I think I not only have a solution but also an explanation for what is happening.
This worked for me on Vista:
- Control Panel> Programs and Features
- Click on Avast icon
- Click on Uninstall/Repair
- Click on Repair
- Start Avast from the system tray or elsewhere
- Click on Fix Now
I think what might be happening is that a program update at startup gets interrupted leaving the program in an inconsistent state. This leaves the Avast service unable to run and it terminates.
Why the update gets interrupted is another question...
In my experience you have to use the control panel Programs and Features as all other uninstallers can't get around the Avast self protection.
-
Also still having this issue. Every reboot, shields are down captain....hit the FIX NOW, everything is fine after, and runs perfect. Never had any issues until recently about a week ago.
Running XP Pro
Avast 5.0.545
Tried all the easy fixes, of repairs and what not? So, I'm still having issues.
Any help would be appreciated.
-
After sharing what I thought was the solution I also had a further problem last night and this time my procedure didn't work. However, when I started this morning and Avast was still not running, I went through my procedure again, and this time IT WORKED.
Did I do anything different? I'm not sure but here is what I did this morning.
1. Start control panel Programs and Feature (in XP use Add/Remove Programs). Click on the Avast icon and uninstall (in Vista, click on the Uninstall link).
2. The uninstall process offers a number of options. Click on Repair.
3. After the repair has completed, click on Update.
4. Start Avast and click on Fix.
I emphasize that it is Windows Programs and Features (Add/Remove Programs) that should be used, not any alternatives. (I use Revo Uninstaller normally but have not had any success with it on this Avast problem.)
One thing to note is that while this procedure did not work last night, it did this morning. Reboot? It may be that a reboot is required.
Hope this helps.