Windows 7 - Windows 7 Processes and Files

I recommend a complete system image if you are going to try it.

Ok, but just saying, when another proccess says it is using high CPU, but not high RAM, the fan goes on high, but when its not, its low.

Occasionally, my fan will be really high for no reason, and when i check task manager, it says systemIdleProccess is at 98-100% of my CPU.

Here you go; check these links:

System Idle Process: Information from Answers.com

Coding Horror: Why Is The System Idle Process Hogging All The Resources?

I applaud you for the initiative. Just 2 comments:

1. if you feel like it and have the time, you should make it into a tutorial. Here it will eventually disappear from the radar screen - even pinned.
2. as you do your research, you will run across links that give more detailed information. The best links I would include (and I am not talking about all those websites that want to sell you some dumb scanning program)

I will give it a try. Thanks for the suggestion.

That could become a lifetime job. Maybe you guys get together and do it together. One piece of information people are always looking for is whether a certain service - or group of services - can be stopped or not. And that answer is not easy because of the interdependency of the services. People are usually being referred to Black Viper, but there it is fuzzy too. A "breakthru" on that question would be a real step forward.

So its just flusing out all the idle threads it used during my systems uptime?

How does one know whether they are idle or not?

WHS,

I have been researching this for the last hour. What I found is that most of the information available dates back to XP days. I found nothing Windows Seven specific at Microsoft - only a general statement about the process. I don't really see a need for a tutorial as there is nothing to tutor. Here are the results of my my research.

From Microsoft - System Idle Process - You cannot end this process from Task Manager. This process is a single thread running on each processor, which has the sole task of accounting for processor time when the system isn't processing other threads. In Task Manager, expect this process to account for the majority of processor time.

I conclude that the system idle process is more of a counter than a process.

The fact is that most computers can never really do nothing. When the computer is on, the CPU is running and it must do something - even if that "something" is waiting for something real to do.

Think of it as the computer just twiddling its virtual thumbs, waiting for something more important to do. The computer's doing something (virtual thumb twiddling), but we wouldn't call that doing anything useful - we call it being idle.

The "System Idle Process" is the software that runs when the computer has absolutely nothing better to do.

Hmm, keep looking. There is a lot more to it. It's going to be a fun project.