Erik
What are your anti-virus and anti-spyware arrangements?
Task Manager is useful but you could look at another freeware utility
Process Explorer, which provides similar information but adds that
little bit extra towards seeing what the running processes represent.
For further information about Process Explorer see here:
http://www.sysinternals.com/ntw2k/fr.../procexp.shtml
To ascertain which service is causing the problem select the
image name producing the high CPU usage, right click,
select Properties, Services. Note there are the full names and some
explanation of what each service does.
You will find further information on Services here:
http://www.theeldergeek.com/services_guide.htm
To trace the particular Service involved you need to turn off each
service in turn and then restore it noting what effect it has on CPU
usage. However, you need to take care and watch what other Services are
dependent on that service. When you click on the Dependencies tab allow
it a little time to display the information.
Hope this helps.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
"Erik" <(E-Mail Removed)> wrote in message
news:B395D2DC-A17B-4E1F-9767-(E-Mail Removed)...
> Can anyone give me some suggestions on how to relieve the problem I have
> with
> my laptop's (Windows XP Pro) CPU frequently spiking to 100%. Once the CPU
> hits 100% all programs/applications run painfully slow or freeze and the
> spike remains unless I manually kill all processes using the most memory
> via
> the Task Manager. I don't see any trends with the CPU spiking. It spikes
> even if I just have a typical Web page open (i.e.: msnbc.com) and nothing
> else. This problem just seemed to happen all of a sudden for no apparent
> reason and has been an issue for several weeks now. I didn't install
> anything that caused this (to my knowledge).
>
> Additional info:
>
> - I have all the latest XP and Office updates installed (via
> windowsupdate.com and officeupdate.com).
>
> - I've done "Error-checking" and "Defraged", but the problem still
> persists.
>
> Please help. Thank you.
>