I, too, am getting this. However, I can give significantly more details about it than I've seen in other replies here. Screenshots work wonders so I'm posting one (it's 1920x1440, too big to post directly):
View the 1920x1440 screenshot.
By going to "view" then "columns", you can see a lot more system status elements than what Windows Task Manager has by default (I use them for my game design stuff, useful for hunting for otherwise unseen bugs.). Only the "vsmon.exe" process is having this problem.
For the more in-depth details:
A read and a write are performed almost simultaneously every 2 seconds. Each time a read occurs, exactly 5,196,800 bytes are being read (but increases under certain circumstances - see below for details). Each time a write occurs, exactly 7,811,584 bytes are being written (this increases as well, under the same circumstances.
When I check "C:\WINDOWS\Internet Logs", I see that there are 4 files that are always up to date, almost to the second. A fourth file seems to be off by only a few minutes, but occasionally updates every 2 seconds with the rest. These are the following files in question (exact files sizes after the //):
HOME-B4C7A5B812.ldb // 1,351,680 bytes and increasing (see notes below)
BACKUP.RDB // 2,598,400 bytes
IAMDB.RDB // 2,598,400 bytes
ZALog.txt // see notes below
By repeatedly right-clicking on the "ZALog.txt" file and choosing "properties" to bring up the file size, its file size increases by about 500 bytes. In addition, the LDB file increases in file size as well. The other two files are not affected by this behavior.
I'm using Windows XP Pro SP3, fully updated. The ZA version stuff is as follows:
ZA Security Suite version 9.1.507.000
Truevector security engine version 9.1.507.000
Driver version 9.1.503.000
This doesn't affect system performance to any noticeable degree, however, it is noticeable when loading/saving files on the drive that's affected (C for me - nothing happens on my E drive as it only has video and music files stored on it). Of course, those with slower systems (like Pentium 3 or 4) will have a noticeable degradation in performance because of this.
Hopefully this information can be used to pinpoint the cause of the problem.
Edit: ZALog.txt, not ZALog.log