Idle - CPU Usage?

[Perixx]

I've always checked my CPU usage and when I idle, it way always 0% and maybe 1%. All of a sudden, ever since last night, I idle at like 10% CPU. I've restored my computer to an earlier good backup, I have ran anti-malware and viruses and they've came clean. What is this and why did this happen all of a sudden?

[ForsakenLive]

Even a windows update service can be doing this, so don't worry too much. However:

 

What are your specs?

Use the task manager to see what processes are being run (take a screenshot if you want to).

Use the run application (press Windows Key + R simultaneously) and type 'msconfig'. Enter the services tab, then check the box that says 'hide all windows services'; this will show you a list of all the non-windows related services being run in the background when you boot. Take a screenshot of that as well.

[Perixx]

I'm using a Lenovo y410p.

i7 4700MQ

GT 755m 

8GB RAM 

[Perixx]

Even a windows update service can be doing this, so don't worry too much. However:

 

What are your specs?

Use the task manager to see what processes are being run (take a screenshot if you want to).

Use the run application (press Windows Key + R simultaneously) and type 'msconfig'. Enter the services tab, then check the box that says 'hide all windows services'; this will show you a list of all the non-windows related services being run in the background when you boot. Take a screenshot of that as well.

 Specs are above

[ForsakenLive]

-snip-

 

I asked for the specs to see if the motherboard was using any sort of controller that could impact CPU load (for example Killer NICs). But the board in the notebook shouldn't be of any concern.

 

The application that is generating this load is 'system interrupts'.

System interrupts is an state in which the CPU is waiting for some sort of input, be it from a device, or even another application. Something as silly as a plugged USB drive that is doing nothing can be constantly alarming the system that input needs to happen.

These interrupts are something extremely common, and happen all the time in a computer. Even by touching the trackpad, pressing keys or even moving the mouse causes them. The more processes and services you are running simultaneously can potentially increase the amount of times the system expects you (or other software) to do something, causing these extra efforts to check if there is anything else to do.

Usually the OS does the handling of how much important is a I/O interrupt, so you should be fine during high loads (apps running in the background shouldn't let this load happen if there is something with higher priority). Basically, don't worry much.

 

To reduce the amount of times this is happening, and to have a more agile and quicker to boot system, I suggest you start removing stuff from the startup.

First, take a look at the 'startup' tab in the task manager, start disabling stuff that pops up every time you turn on the PC. Leave the antivirus if any (I couldn't see it on the list, so you are probably running the integrated windows defender, which is fine).

You have services coming out on boot massively, so start unchecking some boxes there! Don't get too worried about what you should/shouldn't touch, as most of the stuff on the list is not critical, and it's own processes are most likely to launch the service when executed. Pretty much allow all the Intel and Nvidia stuff to do their thing (don't mind them), leave the steam service on as it gets pretty mad at you when you uncheck it (no kidding). Also allow services from specific hardware you are using, as well as the software you actually want running all the time (like displayfusion). Everything else (including Google's stuff) seems like it can go away. If you found some program having a function that is not working, check that box back. As I said before, these are not critical stuff, so don't get concerned about them.

[itachipirate]

Maybe try looking through task scheduler? I'm not sure if scheduled tasks are classified under that process

[Perixx]

I asked for the specs to see if the motherboard was using any sort of controller that could impact CPU load (for example Killer NICs). But the board in the notebook shouldn't be of any concern.

 

The application that is generating this load is 'system interrupts'.

System interrupts is an state in which the CPU is waiting for some sort of input, be it from a device, or even another application. Something as silly as a plugged USB drive that is doing nothing can be constantly alarming the system that input needs to happen.

These interrupts are something extremely common, and happen all the time in a computer. Even by touching the trackpad, pressing keys or even moving the mouse causes them. The more processes and services you are running simultaneously can potentially increase the amount of times the system expects you (or other software) to do something, causing these extra efforts to check if there is anything else to do.

Usually the OS does the handling of how much important is a I/O interrupt, so you should be fine during high loads (apps running in the background shouldn't let this load happen if there is something with higher priority). Basically, don't worry much.

 

To reduce the amount of times this is happening, and to have a more agile and quicker to boot system, I suggest you start removing stuff from the startup.

First, take a look at the 'startup' tab in the task manager, start disabling stuff that pops up every time you turn on the PC. Leave the antivirus if any (I couldn't see it on the list, so you are probably running the integrated windows defender, which is fine).

You have services coming out on boot massively, so start unchecking some boxes there! Don't get too worried about what you should/shouldn't touch, as most of the stuff on the list is not critical, and it's own processes are most likely to launch the service when executed. Pretty much allow all the Intel and Nvidia stuff to do their thing (don't mind them), leave the steam service on as it gets pretty mad at you when you uncheck it (no kidding). Also allow services from specific hardware you are using, as well as the software you actually want running all the time (like displayfusion). Everything else (including Google's stuff) seems like it can go away. If you found some program having a function that is not working, check that box back. As I said before, these are not critical stuff, so don't get concerned about them.

I figured out that this interrupt is being cause from one of my external displays. I have two, running off my laptop, while the laptop's display's is off. Both displays are the same, except, one if running vga and the other is using HDMI (from laptop) to DVI (the montior). If I unplug this display, this idling is normal and the interrupts disappear. Why is my second display causing this if it is the same? I used to run dual displays and never had this problem with different monitors. Would it be because I'm using an HDMI to DVI cable?

[ForsakenLive]

I figured out that this interrupt is being cause from one of my external displays. I have two, running off my laptop, while the laptop's display's is off. Both displays are the same, except, one if running vga and the other is using HDMI (from laptop) to DVI (the montior). If I unplug this display, this idling is normal and the interrupts disappear. Why is my second display causing this if it is the same? I used to run dual displays and never had this problem with different monitors. Would it be because I'm using an HDMI to DVI cable?

 

It's pretty cool that you found out what was causing the interrupts so quickly! To scan exactly what thing/app is exactly causing them is a tremendous hassle.

Now, to the monitor thing. Which model is it? Does it feature any sort of USB ports, audio ports or something in particular besides the default DVI port?

Remember that HDMI does take care of audio as well, so you should try this:

-Open the sound tab (you can right click the speaker icon on the bottom tray), then disable the HDMI sound.

-Go to Device manager and see on the display and the sound-related categories, what's there. If there is some HDMI sound option enabled, try turning it off (disable).

-Reboot the system and check again if the monitor leaves this undesired load on idle times.

[Perixx]

It's pretty cool that you found out what was causing the interrupts so quickly! To scan exactly what thing/app is exactly causing them is a tremendous hassle.

Now, to the monitor thing. Which model is it? Does it feature any sort of USB ports, audio ports or something in particular besides the default DVI port?

Remember that HDMI does take care of audio as well, so you should try this:

-Open the sound tab (you can right click the speaker icon on the bottom tray), then disable the HDMI sound.

-Go to Device manager and see on the display and the sound-related categories, what's there. If there is some HDMI sound option enabled, try turning it off (disable).

-Reboot the system and check again if the monitor leaves this undesired load on idle times.

HDMI sound is already disabled. What's odd is, if I hibernate my computer, once I turn it back on and relieve it from hibernation, the cpu stress is gone. But, if I restart/shut down my computer and reboot it back up, it is there again until I hibernate my computer. Considering I am using a cheap HDMI to DVI cable, could the cable be the problem? Any other thoughts or ideas?

[ForsakenLive]

HDMI sound is already disabled. What's odd is, if I hibernate my computer, once I turn it back on and relieve it from hibernation, the cpu stress is gone. But, if I restart/shut down my computer and reboot it back up, it is there again until I hibernate my computer. Considering I am using a cheap HDMI to DVI cable, could the cable be the problem? Any other thoughts or ideas?

I don't think the cable is the issue. It looks like there is some piece of software derping somewhere.

 

Can you try telling the display driver to replicate all the screens (I think it's called mirror mode or something like that). So we can be sure there is no 'overthinking' being done by the display software, or nvidia's control panel. Try to get it to boot on mirror/screen-replicating by default, to see if part of the extended desktop feature is not being handled by the driver all that properly.