Cpu %
Thread Starter
Join Date: Jun 1999
Location: England
Posts: 105
Likes: 0
Received 0 Likes
on
0 Posts
Cpu %
I am running Windows XP Home with 512 of RAM. My pc has slowed down. When I look at the cpu it is running at 100% is that correct? Should it be running at such a high %. If not what can I do to reduce it.
Thanks in advance
Fueldump
Thanks in advance
Fueldump
Have a look under the menu Processes in Windows Task Manager. This shows you all the processes that are running and how much CPU% they are using. You should be able to spot the culprit(s) there.
100% may be correct, it depends on which applications you have running. Have a look through the process list and close the programs using the most CPU% to see if they are causing the slow down. Sometimes the name on the list is a bit cryptic, but a quick search on Google usually reveals the source.
You can also use the process list to see how much memory is being used by the various processes, which could also be the reason for your slow down.
(You can access Task Manager via CTRL-ALT-DEL.)
100% may be correct, it depends on which applications you have running. Have a look through the process list and close the programs using the most CPU% to see if they are causing the slow down. Sometimes the name on the list is a bit cryptic, but a quick search on Google usually reveals the source.
You can also use the process list to see how much memory is being used by the various processes, which could also be the reason for your slow down.
(You can access Task Manager via CTRL-ALT-DEL.)
The Oracle
Join Date: Aug 2001
Location: Naples, Florida U.S.A.
Posts: 2,902
Likes: 0
Received 0 Likes
on
0 Posts
fueldump,
Also run:
Trend Micro's Housecall
Just to make sure a virus is not causing your CPU to run at 100%.
Take Care,
Richard
Also run:
Trend Micro's Housecall
Just to make sure a virus is not causing your CPU to run at 100%.
Take Care,
Richard
Sub Judice Angel Lovegod
Join Date: Oct 2002
Location: London
Posts: 2,456
Likes: 0
Received 0 Likes
on
0 Posts
There are a number of things that make the CPU run at 100%. Virus scanning is a favourite, but there is also something(...brain wrack..brain wrack...no I'll have to get back to you) which runs as a result of SQLServer or MSDE being misconfigured on a PC which is also running either Outlook or Outlook Express. Not very helpful, I know, but might help you look in the right area.
I suggest that you try switching off services that you don't need, one by one.
W
I suggest that you try switching off services that you don't need, one by one.
W
Join Date: Jul 2003
Location: Scotland
Posts: 151
Likes: 0
Received 0 Likes
on
0 Posts
I had a similar problem recently and it was the nachi 'virus' which was causing these problems, if you look in your task manager and it is DLLHOST this may be your prob.
If you are unsure of the process that is killing your processor drop a line in here and I am sure you will get a quick answer.
If you are unsure of the process that is killing your processor drop a line in here and I am sure you will get a quick answer.
Join Date: Sep 2002
Location: Chichester, UK
Posts: 1,650
Likes: 0
Received 0 Likes
on
0 Posts
I had a problem with a thread in the XP/Home System process using 100% CPU... triggered by Microsoft's recent DAO critical update
It's a rare but known issue. Should be fixed in SP2. Until then I've reinstalled XP/Home, added SP1 and all the other critical updates apart from DAO, so far so good (but I wish Windows Update would stop trying to get me to install an XP killer...)
More common with a System runaway is a dodgy driver, and it's easy to diagnose what is causing this. If it isn't System it could be legit (running Seti@Home, for example), a bug (Norton Internet Security used to run away on my XP/Pro box and use 100% CPU - killing the process fixed that) or something not so good
It's a rare but known issue. Should be fixed in SP2. Until then I've reinstalled XP/Home, added SP1 and all the other critical updates apart from DAO, so far so good (but I wish Windows Update would stop trying to get me to install an XP killer...)
More common with a System runaway is a dodgy driver, and it's easy to diagnose what is causing this. If it isn't System it could be legit (running Seti@Home, for example), a bug (Norton Internet Security used to run away on my XP/Pro box and use 100% CPU - killing the process fixed that) or something not so good