Just what you suggested above... a couple of things that were constantly searching for upgrades from Microsoft. Alan
Sarcasm, right? As a trader, I don't care about maximum performance, features, or value. All I care about is that it starts up every day and runs reliably. The Techs at Equis said [paraphrasing], "... The code for MS Pro was written for maximum compatibility with Intel..." Maybe they hold stock??? Anyway, it has worked for me!!
Duhhh! Who couldn't tell that? I was just saying that Equis recommended Intel for MS Pro. I have an AMD machine too, and it also works smooth as a gravy sandwich... though it's not my primary trader.
============================================= FREE virus scans! *http://www.pcpitstop.com/antivirus/default.asp *http://housecall.antivirus.com *http://security.symantec.com Good luck! =============================================
Thanks for the sites. When I get this situation resolved, I'll stay on top of things with periodic scans. I did a full PitStop scan, no viruses were found. Alan
I have had the same problem with high CPU usage. As Archangel suggested, it may be an ap running in the backgroung. Upon looking into my problem I found Seti@home was the culprit.
Note that the Pitstop scan is not complete - it only scans for the most recent 200 viruses. The virus I removed from a friend's PC a couple of weeks ago that was eating up all his CPU was a fairly old virus and would have been unlikely to be found by Pitstop. Don't mistake Pitstop as a substitute for a full blown virus scanner like Norton Anti-virus. Good luck.
Archangel, you make a good point. I had to think back(I've been working on this problem for several months), and actually when I first experienced the high cpu usage someone recommended I disable my Norton antivirus(which I did), thinking it might be the cause. I had been running it up to that point. Here is the latest... last night the plan was to do a complete system recovery, and then if the problem still persisted, it would be in IBM's hands. But the recovery stopped midway through the process, and a diagnostic test indicated a defective hard drive. This same test found nothing several months ago. So I should get a new hard drive from IBM on Monday, and then I'll see how it goes. It would be some coincidence if this wasn't the problem, but you never know. As always, thanks for the helpful posts. Alan