Downloaded .396 on XP3 and no more BSOD’s. On a reboot for another software shields stop sometime. Is there a Delay in hitting the “Fix” button and the shields becoming active. I tried it once without it working, then I saw that Gaming Mode and set that. (I like that feature) then in a few seconds the shields come up??? Definetly more stabile than .377 And it resolved the PowerDVD issues as far as I can tell. Much Better!!!
I think I may be having the same problem.
Twice now I have had to start the shields manually with the fix button. My system also had the date drop back to March of 2001.
There also a problem with Avast 5 loading first. It shows itself not loading until after other items.
So far I’ve had none of these issues with 5.0.396. I have noticed on my XP SP3 box that it managed to change my power settings for me. My monitor was set to power down after 20 minutes. For some reason this was changed to Never during the install of Avast 5 or the uninstall of Avast 4.8. I wondered why my screensaver was always running.
sounds like a new bug on XP (according to several reports)… as to the interference with power options, that’s hardly possible 
Hello amk…
Open avast! and go into settings>troubleshooting. You will see a box marked load avast! services only after loading other system services. See if this box has been checked. If it has, try removing the check mark, click ok. Reboot your pc and see what happens. This may or may not help you.
I had one BSOD last night (not caused by Avast but by HP). Booting up though, the shields do not come on line. Had to “FIX” again. You’d think on a reboot the shields should come up without having to be fiddled with. Still a lot more stable that any earlier version.
I upgraded my XP Pro system to 1.5GB RAM and it is a lot more stable and faster as well.
I found out that my system uses dual channel RAM and in order that it performs at its best the same RAM size has to be installed in the second slot.
In total I now have:
Slot 1 512MB PC2700 (166MHZ)
Slot 2 256MB PC2700 (166MHZ)
Slot 3 512MB PC2700 (200MHZ)
Slot 4 256MB PC2700 (200MHZ)
For a little over $50 it will make this system last a while longer for me.
Yokenny, what is that for, who’s having any RAM issue here ??? did I miss something ? you can always argue that the lack of RAM can cause issues, even bsods, but why now and why here ? was a full description of your memory configuration needed at all here? no offense man, I’m just asking…
If anyone else has a clue how this is related to this thread thanks for letting me know
It was a Tidbit of information, I guess. Lost my shields again, this time without BSOD. Would not “fix” on Avast screen. Got an error going to windows uninstall and trying to Repair the program. Finally got them up by going to Change in unInstall. Can’t figure what is dropping them out. And do you all notice that when shields drop the maintainance screen doesn’t know what versions it is holding on program or virus definitions.
Twice now my system has crashed unexpectedly when no one was on it. This is never happened until I installed avast5. When the computer reboots, it says it is recovering from a major error. Then, avast has a red X over the systray icon, and the program isn’t running. I click on Fix and nothing happens.
Last time it happened I went to Control Panel -->Add Remove Programs–>Avast5 and selected “Fix Install” and it solved the problem. This time it doesn’t work.
I am running XP SP3.
Do you have auto-updates of VPS turned on? If so, at what time interval?
The default is 240 minutes.
If using auto-updates of VPS it’s possible that the crash occurred during
or right after an update. If the problem persists, try setting updates to
notify only. Then initiate a manual request for updates at your discretion.
Or leave it at auto-updates but set the time interval to a very high value
(e.g. - 1440 minutes). Then do a manual update when you want, so you can
see if any problems occur immediately following.
Note that changing the time interval for updates doesn’t appear to take effect
until the next time avast! is started (e.g. - after a reboot).