http://forums.tomcoyote.org/index.php?show…t=0&#entry17825
He says while he's idle there is a 60-40 cpu usage split between system idle process and
'System'. I don't know what is causing it and I hate to leave him hanging here. What is the 'system' process anyways?
In my task manager I have "System" under image name column using 48k 0% cpu
tried ending the process, not specified that it couldn't be ended, but doesn't end process
In my task manager,
Image Name = System
User Name = SYSTEM
CPU = 00
Mem Usage = 236k
I used to have this cpu spikes between 2 and 60%, after trying different things, it went away when reinstalled the USB printer. One of those unexplainable cures.
Various things (can) have system privileges on different machines. One of those things (on 2k, and perhaps other os's) is Indexing. I would like to have input about other instances of high CPU use and associated tasks, to get some glimmer of a general fix for such hangs.
I am interested in how indexing affects page file access, in NTFS based systems especially, with varying amounts of ram. If ram is low, does that increase CPU use dramatically during Indexing? Can the problem be solved by disabling indexing service?
There are various network services that might be improperly running automatically, as well. I need input. I have a wisp of understanding, but lack data and confirmation. I *think* that high CPU use may often be cured by disabling unnecessary services.
Any gurus, cohorts, or guinea pigs in this quest please raise your hand.
Indexing will cause this problem If I could get a little mor information about his or her system .. Page files will also cause this trouble as well as a messed up hdd when was the last time they defraged there drive..
http://www.blackviper.com/ used to be a decent website to obtain Windows Services information with excellent information on all of the System Processes (for both SP1 and SP2), but at the time of this post I am unable to get there!
Perhaps Viper is redesigning his pages to include the newer SP2 information, which has a radical impact on System Services on many PCs, yet (seemingly) on a "pure" Intel (my choice), the SP2 has done nothing except increase my performance, stability and security to new 'highs'.
If you think that it is a problem with the Page File, go to http://www-xp-smoker.com/ and download the trial version, then simply familiarise yourself with setting up the Trial version (because it WILL completely clean out the Paging File System upon a reboot once installed) …that's one way of eliminating the "question" of it being in the Paging File complex.
This doesn't appear to be a Software related issue, however it most certainly is pointing to a memory module error (especially if the machine is 'loaded' with Kingston DDR 'chips'). It also could be a failing CPU or perhaps the CPU needs to be 'released' from it's ZIF socket (slightly), then "snapped" back into place. Same thing might apply for the Memory Modules (remove/reinstall) to get a good 'contact' at all points! Or maybe the bugger just needs to be blown out with some Canned Air?
*Last Choice: If a Window's Reload/Repair ("over the top") doesn't correct the problem, then it is most likely the hardware and not a "bug" in the works. There just aren't that many 'nasties' out there that can drain resources while putting a load on the CPU without being resident in memory, and in that event they will most certainly be detectable "on sight" in an HJT (and I see nothing in the displayed HJT that remotely points to such a beast). If it were resident in memory (or hiding in the Boot Sector), getting rid of it may involve nothing less than a complete wipeout and reload.
I pray this helps …or if nothing else I'll either get in trouble for opening my mouth (fingers?), or this will never be read!
The Reverend
(cadet)-Day One
I pray this helps …or if nothing else I'll either get in trouble for opening my mouth (fingers?), or this will never be read!
The Reverend
(cadet)-Day One
Bob
