What happens if system idle process is ended

I opened task manager and saw what process where using the most. You cannot kill the System Idle process. The real question is why would you want to? System Idle is the process that runs when the computer has absolutely nothing better to do in other words it is waiting for some other process to need more CPU resources.

The fact is that most computers can never really do nothing. Think of it as your computer just twiddling its virtual thumbs, waiting for something more important to do. It effectively runs at the lowest possible priority so that if anything, anything at all, comes along for the CPU to work on, it can.

Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How to terminate System Idle Process? Ask Question. Asked 6 years, 4 months ago. Active 1 year, 7 months ago. Viewed 18k times. Without this process constantly keeping your processor occupied with something to do, your system could potentially freeze.

You can think of it as a simple placeholder. Without this process always keeping your processor occupied with something to do, your system could potentially freeze. System Idle Processes are native to Windows NT operating systems, dating back to —they also appear in Unix-like operating systems such as Linux but operate a bit differently.

A System Idle Process is a normal part of your OS that runs a single thread on each CPU core for a multiprocessor system, while systems that use hyperthreading have one idle thread per logical processor. The reason this all works is that the idle threads use a zero priority, which is lower than ordinary threads have, allowing for them to be pushed out of the queue when the OS has legitimate processes to be run.

To understand the number next to the process in Task Manager, you have to think the opposite of what you normally understand it to mean. Browse All iPhone Articles Browse All Mac Articles Do I need one? Browse All Android Articles Browse All Smart Home Articles Customize the Taskbar in Windows Browse All Microsoft Office Articles What Is svchost.

Browse All Privacy and Security Articles Browse All Linux Articles Browse All Buying Guides. Best Portable Monitors. Best Gaming Keyboards. Best Drones. Best 4K TVs. Best iPhone 13 Cases. Best Tech Gifts for Kids Aged Sometimes my machine is running idle and it cannot be interrupted.

That is, the idle process is too busy to notice keystrokes and mouse clicks. I once read something about WinXp automatically moving files about, a kind of optimisation. The point seems to be that users expectations are that the SIP should not take over the machine, but it does, interferring with the usefulness of the computer.

There have been many times for me when a program has appeared to have crashed when in fact the computer is just busy doing the SIP. If the SIP is housekeeping processes and commands to keep the processor occupied during periods when programs are inactive then as soon as a program requires the CPU, the SIP should be suspended. So either the SIP has been badly programmed or it is more than the computer sorting itself out.

Either way this is very frustrating to users and a way to control the SIP would be really welcome. On my computer i found the same thing, but while transferring a massive gb folder from partition to partition. Needless to say it is deadly slow, should,nt the processor consider that an opportunity to maximize the cpu to decrease time? Leo, I understand what you are saying about SIP not interfering by definition, or by design is probably better.

But what Hawkins, Webb, and Milton are saying is true. Whatever the intent, SIP does in fact interfere. What is needed, as Milton says, is user control of this feature. Is it that once it starts, it must finish the SIP first? Is this process only characteristic of Windows? One guy said it was days b-4 he could even get on line. I did a search because I was under the same idea, that the system idle process was killing my ability to work.

I have a feeling that based on the new info here from Leo and the complaints that I was right in my first idea. The slowdows are the result of either system restore files being written, the hard drive trying to clean up swap files and rewriting or closing files, or both depending on when they take place. I think the system backup is growing too large and maybe the way to stop it, is to make sure the computer is running right and turn off the system restore so it dumps the huge files, then restore it so it can start over.

I hate waiting 12 minutes on startup because the hd is wigging and wigging though the processor and system idle show nothing is happening.

Having read most of the comments above, I get what system idle is all about and have never had an issue with it, until now. What is it doing? Does it effect the temperature of the processor?

The svchost. My computer is slow to to launch any program and Internet Explorer and email is most difficult to launch. This seems to be a matter of communication.