Windows 7 Processes and Files

CarlTR6 said:

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.

That is what I found in my research as well.

WHS, you say there is more to this process? It seems to me that it is pretty clear cut. It is not hogging the resources of your system, it is providing them with something to do while they have nothing else. This should not trigger a high fan speed. That may be an issue with the BIOS or just a read error.

~Lordbob

I will keep digging; but I am going to have to get some books on the architecture of Windows Seven. Most all of the references I can find are to XP with few to 2000 and Vista.

I guess I am not sure what you meant then...

~Lordbob

I think he may be referring to this:

"In Windows 2000 and later the threads in the System Idle Process are also used to implement CPU power saving. The exact power saving scheme depends on the operating system version and on the hardware and firmware capabilities of the system in question. For instance, on x86 processors under Windows 2000, the idle thread will run a loop of HLT instructions, which causes the CPU to turn off many internal components and wait until an interrupt request arrives. Later versions of Windows implement more complex CPU power saving methods. On these systems the idle thread will call routines in the Hardware Abstraction Layer to reduce CPU clock speed or to implement other power-saving mechanisms."

This is why I need to delve into Windows Seven architecture.

Just wondering... How did me asking what would happen if I killed the proccess (Access is denied by the way, even in Admin safe mode), turn into all of this?

cclloyd9785 said:

Just wondering... How did me asking what would happen if I killed the proccess (Access is denied by the way, even in Admin safe mode), turn into all of this?

LOL, it is called learning. From your original post, we learned that the process cannot be killed, that it is not using resources, and that it actually enhances the use of the CPU.

NEXT PROCESS!

If I kill wininit.exe, I know it will cause a BSoD, but will it harm the system after it boots back up?

whs said:

Guys, don't break your heads over it. I only meant that there is a lot to be found regarding windows7 processes. Here is a lead, but you have to dig deeper.

Now that is heavy! That will require some concentrated reading for me.