Please run the removal utility specific for old AVG so to delete any remnants.
You haven’t been reading: I’ve done the SP3 update. This didn’t really help much – my computer remains slow. If I turn off Avast, my computer behaves normally.
It is possible that my computer is the only computer in the world having trouble with the latest version of Avast. But I doubt it. I suspect this version has a bug in it that is masked by faster processors and larger memory of newer systems.
We can’t say if avast has a bug “just” for the behaviour seen in your system.
For example, if some remnant of previous security tools is still causing some conflict with your current avast, then who is really causing this? Is it avast, or the remnants? In such case, disabling avast’s shields you see the same effect, but avast may not be the culprit.
Some other situations similar to that one are possible. Don’t get me wrong; it is still possible that avast has a bug. The point is that we need to find out where exactly the real culprit is located, instead of just showing some general consequences.
The removal utilities for older security tools that were already uninstalled was already suggested. A clean up of all your previous versions of avast was also suggested. If you want to report about these steps, we will try to continue with you narrowing down the source of problem.
After two weeks of fussing with this computer, I’ve found the problem:
Windows somehow got switched into PIO mode. I was able to find a script to fix the registry here: http://winhlp.com/tools/resetdma.vbs
I don’t know if Avast caused this – perhaps it is merely a coincidence that Avast shut itself down (and prompted me to update) on the same day Windows decided it was time to go into PIO mode.
I like Avast (right now I have AVG installed) but I’ll wait for a new version to come out before trying it again.
Avast has nothing to do with the mode of your storage ports; not in the BIOS nor in your OS. At most, avast was indirectly (and unintentionally) showing you the problem, but was not the source of it.
JFYI, before reinstalling avast (whenever you do), uninstall any other security tool and run the respective removal utility (http://singularlabs.com/uninstallers/security-software/) under Windows Safe Mode. This will reduce conflicts between security tools.
Windows will go into PIO mode automatically after a certain number of disc access events it reads as errors (I believe the number is six). This seems to happen with bad CDs/DVDs especially.
I don’t see how Avast could have been responsible for this either – I’d assumed it was, because the problems started after the update.
I still think it’s strange that 1) Avast turned itself off and 2) the sound icon disappeared from the taskbar – at the same time Windows switched to PIO mode.
If nothing else, I’ve spent the last few days cleaning up my computer, it’s running as fast as it did when it was brand new (four years ago).
The DMA mode could be deactivated (changed to PIO mode), but that is not for filesystem problems. You should review your cable connections to your storage ports. You could even try the HDD manufacturer’s tool for hardware checking.
The clicking and the sound icon is probably because the PIO mode. It may have been using the same resources that the sound card was trying to use. When your storage works in DMA mode, the conflict (with resources) stops, and the clicking too.
BTW, HDD physical problems can have “clicking” sounds too, but they are clearly different from sounds coming from the OS (or the sound card). They clearly come from the HDD itself.
Please read:
DMA reverts to PIO
http://winhlp.com/node/10