No. The various "shield" options are enabled, which scan files before they're opened, but AFAIK there is no file scan taking place whne nothing's happening.
Hello MorningGlow… Welcome to WhatTheTech…
Avast, by default, installs a "screensaver" process that runs while the computer is idle. The process of the "screensaver" is to scan for viruses as well as build the virus recovery database that assists Avast in cleaning files if it finds them infected.
There is a chance that this activity that you are seeing is a result of Avast. However, it should not be constant. It will be occasional, but by no means constant.
While Avast may play a part in the activity taking place on your computer, there are other possibilities and further tools available to diagnose what is really taking place.
First of all, how much RAM does your computer have? While this wouldn't entirely explain why the system is so active when it is "idle," it may account for more disk thrashing than necessary. When your system doesn't have enough RAM it will use the hard drive to provide more memory to the system. If you have less than 512MB of RAM you will have a lot more thrashing than if you had 1GB or more. 1GB would be optimal, and 2GB would be best for most purposes.
If the activity is always happening, even when the system has not been idle for a long time (such as before the screensaver even kicks in) then it would be an easy matter to download and run
Filemon and generate a log of what disk activity is taking place. This utility will tell you every read/write to the file system. To the untrained eye it may look very confusing. However, if you feel that you have captured some useful information during one of these "active while idle" moments you can always save the log and attach it here for us to analyze. Filemon can generate a ton of information very quickly. It is important that you attempt to run Filemon when you are not performing any other activities on the computer, but the hard drive has remained active, and then only run it for a minute or so.
If this definitely happens "all the time," then you can also use
msconfig (start -> run -> type 'msconfig') to temporarily disable all non-microsoft processes and startup items. It may provide you with a process of elimination for determining what is accessing the hard drive so much. In other words, you can turn groups of items back on until the problem occurs again and then keep eliminating what is doing it.
Good luck and post back here with whatever information you find.