System and System Interrupts- high cpu utilization

Hi there - I can offer another data point to this conversation, highlighting the impact of this issue on battery:

I have a 2014 MacBook Air (256GB 8GB, i5 cpu) on which I have windows 8.1 via bootcamp.

BEFORE YOSEMITE:

I was getting a consistent 10 hours (extrapolated based on the battery drain during the first hour) with moderate usage (surfing, a bit Youtube and Visual Studio). Fantastic, no windows laptop comes close!

AFTER YOSEMITE:

Battery life is noticeably reduced, and based on my extrapolation battery life is reduced to 7 hours. Coming from this stellar performance it feels depressing.

Also the back gets noticeably warmer. System : 7-8%, System Interrupt 2-4%, totaling about 10% of CPU

->After the "lid fix" (this is hilarious - feels like windows back in the days) the temp drops to what I am used to, and System to 0-0.4%, interrupts to 0.1-0.4%

Battery stabilizing... Phew. (will extrapolate again later but seems a lot better already, if not back to before)

Really glad I found this forum. Cant wait for Apple to fix this. I would assume new bootcamp drivers are in order.

Hey Jaws1200,

your method worked for me. I have, as everyone here installed Yosemite as an upgrade onto Mavericks while having Win 8.1 installed using Bootcamp.

My system is a late 2013 13" rMBP with Core i7-4558U and 16GB RAM...

This is not a fix, unfortunately...

If you have a moment please submit a bug report here: https://bugreport.apple.com/

You can use some content from my post on pg. 4 if you like.

~Steph

I submitted a bug report about this on October 28. Finally, just today, Apple marked my bug as a duplicate of 18822589. Does that belong to anyone here who can provide an update? To me this means they have to at least be aware of it now since they are closing the duplicate reports of it. Hopefully that also means a fix is near.

I just received the same... my bug report id was: 18892123

~Steph

so I guess it makes no sense to raise further bug reports then?

My bug report also got closed. Hopes this means that they will look into this and fix it, because it's so freaking annoying.

If anyone has not created a bug report, please do so.

Even though they are marked as duplicates, they increase the impact score of the original bug report.

I cant log into the bugreport page. Is there something I am doing wrong? I am just entering the apple id and password and click ok and nothing happens. I even changed my password. Still the same. Tried from Windows and MacOS

You have to register yourself as a developer before you can submit bug reports:

https://developer.apple.com/register/index.action

Thanks! I did that and successfully filed a report.

This issue still exists in OSX 10.10.1. At least the workaround still works...

Found a permanent fix for the problem which worked great for me on a Macbook Pro Retina 13" Mid 2014 i5 8Gb RAM :-)

(Latest Intel version 3960 GPU driver with Windows 8.1 Enterprise with SP1 and all updates installed per 18.11.2014)

As Admin, go to Power Options -> Choose what the power buttons do -> Change settings that are currently unavailable -> Turn on fast startup (recommended)

However this only fixes it for Windows Shutdown, but not for Restart.

If you choose Restart in the Windows Start Menu the 30% CPU usage with system interrupts and system returns until you either do a shutdown or hibernate.

Hope that helps :-)

Nice work! This is making the workaround a bit more permanent, but still I would like to see a real fix soon. I did acitivate that feature.

Another data point:

I definitely think its with the Intel Drivers

Here is what I did: I installed the Intel Driver Utitlity, which informed me my Intel drivers were outdated:

10.18.10.3960 vs 15.36.7.64.3960 in my case.

So I upgraded to the most recent (expecting no improvement on the issue, but generally newer is better right?) and didnt see an improvement

But that gave me a program in the programs and features section called "Intel Graphics Driver"

I figured what happened if you uninstall that.

After uninstalling that, the driver utility said I am now on 6.3.9600.16384, probably some bare basic minimum driver. The display got very low res. But the System interrupt issue was gone! But that is not sustainable of course. I dont want to look at a low res screen, and Windows also quickly in the background upgraded the drivers back to 10.18.10.3960. (which is I guess what bootcamp thinks is the most recent drivers)

Long story short, drivers have something to do with it, should we not raise a bug with Intel as well?

In this "fix scenario", the external thunderbolt adapter (like a GbE Controller) is not recognized by Windows.