Antivirus crawling on scheduled scan
Linc
OwnerDetroit Icrontian
This is possibly the screwiest PC problem I've ever encountered. I can't figure out what to look at next, and it has the entire technology department here stumped - from the head network admin down to the student PC technicians.
We use GX260 Dells, Windows XP Pro SP1, and Norton Antivirus.
Norton Antivirus will trigger at 1:00am for its scheduled run. However if someone logs on the next afternoon the scan box will come up and say it has been scanning the system since the previous morning at 1:00am. It does this on ALL our system in the lab I work in, and we've had sporadic reports of it occuring elsewhere (we don't have reliable data outside my lab). Similarly, Folding@Home will hang, possibly because of Norton but maybe for its own reason:
[14:53:33] Writing local files
[14:53:33] Using table 1
[14:53:34] Extra SSE boost OK.
[14:53:34] Writing local files
[14:53:34] Completed 0 out of 5000000 steps (0)
[18:46:44] Writing local files
[18:46:44] Completed 50000 out of 5000000 steps (1)
[17:37:37] Writing local files
[17:37:37] Completed 100000 out of 5000000 steps (2)
[12:44:15] Writing local files
[12:44:35] Completed 150000 out of 5000000 steps (3)
The time gap between frames is atrocious.
What we've thought of:
- Is it Folding@Home? (of course the first question everyone asks
)
-- No. It started happening before F@H was installed and occurs on systems without it.
- Is it the volume of data in student profiles on the machines slowing AV down?
-- No. We removed all the profiles and the amount of info on the disks is relatively small.
- Is Antivirus broken?
-- No. If you stop the scan and start a new one, it only takes 20 minutes to complete.
- Was something fubared in the operating system?
-- No. We created a new image for the machines from scratch and reimaged the entire lab and the problem persists.
- Something in Windows XP?
-- No. It happens on our server running Win2K also.
- Is the system going to sleep?
-- No. The hard drive is set to never turn off and only the monitor ever goes into powersave.
I'm really running out of ideas here fellas. Anyone have any ideas?
We use GX260 Dells, Windows XP Pro SP1, and Norton Antivirus.
Norton Antivirus will trigger at 1:00am for its scheduled run. However if someone logs on the next afternoon the scan box will come up and say it has been scanning the system since the previous morning at 1:00am. It does this on ALL our system in the lab I work in, and we've had sporadic reports of it occuring elsewhere (we don't have reliable data outside my lab). Similarly, Folding@Home will hang, possibly because of Norton but maybe for its own reason:
[14:53:33] Writing local files
[14:53:33] Using table 1
[14:53:34] Extra SSE boost OK.
[14:53:34] Writing local files
[14:53:34] Completed 0 out of 5000000 steps (0)
[18:46:44] Writing local files
[18:46:44] Completed 50000 out of 5000000 steps (1)
[17:37:37] Writing local files
[17:37:37] Completed 100000 out of 5000000 steps (2)
[12:44:15] Writing local files
[12:44:35] Completed 150000 out of 5000000 steps (3)
The time gap between frames is atrocious.
What we've thought of:
- Is it Folding@Home? (of course the first question everyone asks
)-- No. It started happening before F@H was installed and occurs on systems without it.
- Is it the volume of data in student profiles on the machines slowing AV down?
-- No. We removed all the profiles and the amount of info on the disks is relatively small.
- Is Antivirus broken?
-- No. If you stop the scan and start a new one, it only takes 20 minutes to complete.
- Was something fubared in the operating system?
-- No. We created a new image for the machines from scratch and reimaged the entire lab and the problem persists.
- Something in Windows XP?
-- No. It happens on our server running Win2K also.
- Is the system going to sleep?
-- No. The hard drive is set to never turn off and only the monitor ever goes into powersave.
I'm really running out of ideas here fellas. Anyone have any ideas?
0
Comments
//edit: Remote Desktop triggers it to speed up just like normal logging on. Also, logging off does not stop or slow it back down again. It keeps going at full speed after a login has occured no matter what.
Not really knowing about these things, it sounds like the proc. itself is throttleing back when not in use. (shrug) it's a thought.