CPU Usage

  • Thread starter Thread starter Brodie
  • Start date Start date
B

Brodie

In my task manager under processes I notice that under the CPU usage most of
the proceses are either at 0 or 2, but the process "system idle process" is
running at 95. Is this normal.
 
Brodie:
System Idle Process is roughly equivalent to the CPU twiddling its thumbs
while waiting for something to do. In other words, 95% System Idle Process
indicates 5% CPU usage. This is normal. Don't worry about it.
 
Completely normal.

Think about what your computer is doing when System Idle Process is that
high.

Tom Swift
 
-----Original Message-----
Brodie:
System Idle Process is roughly equivalent to the CPU twiddling its thumbs
while waiting for something to do. In other words, 95% System Idle Process
indicates 5% CPU usage. This is normal. Don't worry about it.
--
randwulf57

the CPU usage most
of process "system idle process"
is


.
While we're on CPU cycles - according to my Task
Click to expand...
manager, winlogon.exe uses from 2 to 30+% for a couple of
minutes at a time. I've done a lot of searching and
don't think it's the virus-caused Winlogin.exe - I ran a
complete NAV scan with no virus result, ran a SPYbot scan
with no results, ran an Adware scan with only an Alexa
and Comet Cursors results - deleted these and am still
getting the winlogon.exe cycle overuse. Plus, what shows
in my Task manager is "winlogon.exe" not WinLogin.exe.
I've got XP Home and NAV. ANy ideas?
 
dayo:
A quick Google shows two possibilities...
1. Real-time antivirus scanning. I found many references to disabling
real-time antivirus scanning, which seemed to solve the problem. (I am not
recommending you permanently disable your antivirus program. However, it may
be worth a try to temporarily disable it to see if the problem clears up.)
2. A porn dialer winlogon.exe which would be located in the Windows folder.
(I know you have done a spyware scan, but have a look for this file anyway.
Couldn't hurt. Also run msconfig and see if there is a reference to it in
the startup items.)
Of course, there may be other possible causes for this behaviour. Perhaps
someone else has an idea or two to share.
 
Back
Top