system idle process

Simple... It's a virus in your system... Either Blaster or Gaobot...

Goto nai.com and download their stinger tool... it's free.. run it...
or goto trend micros online and do a free virus scan.

Not possible. This has been an ongoing issue with Every W2K Pro system I have worked on.
Nevermind the fact that our Intranet is C.L.E.A.N
Anyone else??

I asked myself the same question awhile ago. The system idle process is responsible for "accounting for processor time when the system isn't processing other threads" I'm confused as to how it may be hanging up the system though, it shouldn't. You cannot stop the process, but to see if it's working correctly try opening the task manager, and while the task manager is open, opening a program (like Internet Explorer) and the System Idle Process should drop to about 6% or so then jump back up when it's done opening the application. Hope this helps.

How could there possibly be the same virus on ALL the W2K Pro/Server PC's I've worked on within a 3000 Km Radius???
They are not linked in ANY way, This issue has been in existence since 2K Pro first came on the market, It is NOT a virus.
Would you profess that McAfee's virus tool Stinger (updated Feb 23/04) is ineffective in finding or fixing the Blaster or Gaobot viruses they claim to detect/protect from????
Nice try
Again, Anyone else??

Thanks Halo,
I'm aware of what it's supposed to do, However, the problem i'm having is it is tying up CPU at a rate of 98-99% for unacceptable lengths of time.
I suppose I shouldn't say it's hanging the system as it does recover on it's own (eventually)
But, this is a critial system and this "lag" time we're experiencing is simply unacceptable

get the tool off the web called procexp.exe

it will give you a detailed explaination of every process and what it is linking to / using.

the gaobot worm infects other pcs on a network instantly. affecting the svchost.exe file. check your task manager... do you have svchos1.exe running?

but run that procexp.exe program (like 300kb's) and report what it finds...

Thanks for the info and the program. It works well, although the System Idle Process is not attached to anything at all. It runs at 98 - 100% and there is no way around it until it lets go. This process is only supposed to be in use when the system is IDLE. And it is not the case in this situation.
Again, thanks for your assistance everyone...looks like this one goes unsolved for alittle longer :(

This question was closed by the author