Cpu stuck @ 100%

robert1117 said:

Screenshots now (2 pages) from Process Explorer. Thank you, gentlemen.

Click on the start orb and type msconfig in the search box. Click on msconfig.exe, Select Diagnostic startup click Apply then click OK. Restart with the prompt and see if the issue is still there.

Apologies for the delay. Holiday season, etc, etc...

My failure to keep a detailed log of my repair efforts clouds the picture of exactly which step(s) finally tamed my overactive CPU; however the general indicators/culprits remain clear. Without question, the success is completely as a result of suggestions presented within this thread.

If my CPU was human, one might have suggested Ritalin. However, it appears the strongest indicator(s) of success point to Outlook and the massive number of startup processes.

While boot time was never a huge factor (actually my "racing" CPU gave the impression it couldn't wait to get into the game), and I've used machines where, while waiting for a full boot up, you could go make and eat a sandwich...at your friend's house across town. Then the ‘welcome’ screen would appear, like clockwork, while reading the last paragraph of an un-translated copy of War & Peace.

In this case, disabling add-ons in Outlook is the most likely remedy. Observing Outlook’s activity in Process Explorer, you could see a steady increase in resources. It would begin by consuming approximately 250MB and ramp up to nearly 0.5GB. Now Outlook is holding steady in the 90MB range. One curious change: UAC now asks for permission to open the program. I did not notice its absence until its appearance.

There is one phenomena that seems to defy explanation; at least to me. When all meters indicated CPU usage pegged off the scale, it would require killing several heavy hitter processes, including Outlook, to bring demand down to even 90%. This would seem to push the scale back toward the elimination of extraneous startups.

Perhaps the largest lesson learned here, excluding the fix itself, is the need to develop the patience to detail the recovery process so those that follow might possibly be spared from having to reinvent the wheel. Fortunately, they may only have to look at the posts contained here.

Clearly the answer(s) to my predicament lies within this thread, and for that I am indebted to each and every one of you.

Thank you.

I'm unsure how to "unattach the net" (or I'm unfamiliar with the term), however, as requested, here is a Process Explorer screen shot following the fix:

I'm still chuckling at my ignorance. What else could "competely unattach the net" mean? pfffftttt. I suppose sounding stupid helps keep a person humble. I am a living, breathing example of the quote in your "signature". I'm just hoping my five minutes is up soon. It is comforting to know that there is assistance
available for the feeble minded. Otherwise, I'd be SOL. Now, if everyone's eyes have quit rolling...

This screenshot is after...ahem, unattaching the net, which in my case meant simply pulling the wireless USB adapter (sheesh):