/ Sign-up
Your question

McAfee CPU Utilization ISSUES!!!

  • McAfee
  • CPUs
  • Apps
Last response: in Apps General Discussion
December 26, 2005 9:59:28 PM

So, I just got a new ATi Radeon X850 Pro GPU. I was having problems installing it when I noticed that my virusscan with background scanning initiated was using anywhere from 20-90% of my CPU AND was constantly accessing my HDD, making it more difficult to use the PC. Well, I have managed to reboot several times, and each time I have disabled McAfee's background scanning, and now everything isi installed and fine. Can anyone help me enable it with out having these issues? I plan to do a virusscan now and I will report back later. Thanks

More about : mcafee cpu utilization issues

December 27, 2005 6:44:16 PM

So, I have done a Microsoft Antispyware scan and found nothing. I have tried to do a full Virus scan, but when McAfee scans certain zip files, it takes too long (i.e. 20 min and still hasn't even passed the file it has been scanning) so I have been unable to do a full scan. But, is it normal for McShield to utilize the CPU (up to 98% when I was installing Catalyst drivers!!!) when I am accessing files, docs, etc?
December 28, 2005 4:35:03 PM

McAfee had a version that went bad like that. They have a small patch out on their website that fixes this. It was about 6-8 months ago when this came out though.
Related resources
Can't find your answer ? Ask !
December 28, 2005 9:58:35 PM

Really? Well I'll go and check it out. Thanks a lot.
December 29, 2005 6:22:35 PM

What verison are you using btw?

There is no need for mcafee to scan files that haven't been accessed or modified.. which tends to cause problems when you're running programs and the like.
December 29, 2005 6:33:45 PM

Right now I am using Virus Scan Professional 2005 version 9. I ran the virtual technician at the McAfee website, which later updated my Security Center. But, when I still run taskmanager, McShield usage still jumps up (just opening 'My Computer' makes McShield use 22% of CPU). I'm guessing this is normal then? It was just really odd when I was installing Catalyst drivers..........