System Interrupts taking up 10%+ of idle CPU Processing Power

lowlanding

Reputable
Sep 2, 2014
4
0
4,520
I recently took out my HDD from my notebook and replaced it with a Samsung 840 Evo SSD. The hardware removal and installation went incredibly smoothly. Upon installing Windows 7 Home Premium (64-bit), I updated all of my drivers and went through the tedious task of Windows updates. With everything up to date and working, the computer ran well. I was happy with the performance of the SSD but noticed the fans slightly louder than normal.

I looked in to the resource monitor and noticed that "System Interrupts" is taking up ~10% of my CPU power. I have quite a powerful CPU, so the 10% is quite a bit. This is causing me to only get about 4 hours of battery life where before I got 7-8 hours depending on what I was doing.

I've done hours and hours of googling and trial-and-error, but nothing I can find is helping my cause. I've checked my other Windows machines and they do not even list "System Interrupts" under Resource Monitor.

I'm incredibly confused as to how I can fix this. I've tried reinstalling Windows (clean install). Even before installing drivers and other programs, the Resource Monitor still lists "System Interrupts" (as seen in attached screenshot).

g1gm2qc.png


My Computer's specs:
-PC: Samsung Series 7 Chronos - http://www.samsung.com/ca/support/model/NP700Z5C-S01CA
-OS: Windows 7 Home Premium (64-bit)
-CPU: Intel(R) Core(TM) i7-3615 (hyperthreaded)
-GPU: Nvidea GeForce GT 640M
-RAM: 8GB
-SSD: Samsung 840 Evo 250GB

I go back to school tomorrow and desperately need this laptop running properly, ANY HELP IS GREATLY APPRECIATED!
 
Solution
I FINALLY FIGURED IT OUT. After about 4 hours of trying to figure out the problem, I needed to install my bluetooth driver.

When setting up the computer, I tried not to install bloatware and things I wouldn't use, so I didn't touch bluetooth. I have no idea why bluetooth caused this but that fixed it for me.

lowlanding

Reputable
Sep 2, 2014
4
0
4,520


Windows 7 does this by default. I double checked and yes, it is off.
 

lowlanding

Reputable
Sep 2, 2014
4
0
4,520
I FINALLY FIGURED IT OUT. After about 4 hours of trying to figure out the problem, I needed to install my bluetooth driver.

When setting up the computer, I tried not to install bloatware and things I wouldn't use, so I didn't touch bluetooth. I have no idea why bluetooth caused this but that fixed it for me.
 
Solution