System and System Interrupts- high cpu utilization

Haven't found any fix yet, but i´m hoping that Apple will help us with this issue soon.

I´m still thinking, that this is the best laptop on the marked, but this problem is simply annoying 😟

completely agree

Same problem here, also with an older Intel driver.

I use 3496 because this is the last driver which can use the MST mode on the Dell 4K 24" Display, so I can use it with 60 Hz on the MacBook Pro 13" Retina Mid-2013. The older drivers have this collage-swap-bug, the newer drivers don't support MST well. Just tried the actual 3960, but it showes only 1 of the 2 virtual monitors of the Dell.

And yes, could be that the problem started with Yosemite update.

This is my first Apple experience, and from what I see in the last months, I could stay with Lenovo, Dell & Co ;-)

Also having same issue since upgrading to Yosemite. Currently on latest release. Issue happened on my Windows 7 Ultimate install and Windows 8.1 install both before and after installing bootcamp drivers and software to windows.

Putting windows to sleep and waking it back up is working as a temporary fix.

Filled out a consumer feedback bug report through apple.

MacBook Air mid 2013. i7, 8gb, 128gb.

I'm affected too. %25 CPU usage while idling.
OSX Yosemite 10.10.1 / Windows 8.1 Pro x64 Bootcamp 5.1
Macbook Air Mid-2013, i5, 8GB, 256GB

I have submitted a bug report on https://bugreport.apple.com/ and they recently closed mine due to a duplicate report. The original bug report ID is 18822589 but I cannot see any other bug reports excepts the ones I have submitted. Can someone with a Developer account check #18822589 and let us know the progress?

This is honestly a joke, how has Apple not fixed this yet...

The tip to enable fast boot is an almost perfect workaround but still, I can't use the restart function without the problem re-appearing.

I love the build of this computer, it's perfect.

OS X however, is not. Hence why I run Windows.

If I knew Apple could effectively break the way Windows functions before I bought this rMBP....I honestly would have just purchased a Surface Pro 3.

I agree, this is ********.

Have exactly the same problem with MacBook Pro 13 Late 2013 Retina on Windows 8.1. It seems that all Macs with Intel Haswell cpu and Intel Iris graphics are affected.

Could it be because of outdated Intel MEI firmware version? I just checked mine, it is v9.5.3.1526:

Whereas the latest Intel ME firmware for this chipset is 9.5.41.1904:

Has anyone tried to update Intel ME firmware on a Macbook?

Still haven't found a fix. What could be other causes of this issue?

I have been experiencing the same issue (Interrupts process eating up to 30-40 % of the CPU) on a much older MacBook Pro than yours, since I installed Windows 7 using Bootcamp two days ago.

My machine is a 2010 MacBook Pro 13" with an ancient Core 2 Duo 2.4 GHz, running Yosemite 10.10.1.

I hadn't been using Bootcamp for a long time up to now. The last time that I used Bootcamp was under OS X Lion and I hadn't experienced any sort of problem.

This same issue happens with Linux on the 13" Air as well. The kworker kernel process, which is kind of an equivalent to the System/System Interrupts part in Windows goes for a indefinite spin using 40-45% CPU. The solution people came out with when using Linux was to disable the "gpe66" interrupt using Linux sysfs facility.

I have tried that in Linux and disabling that interrupt doesn't really have any side effects and it fixes the problem. For Windows I don't know if something similar exists - since Apple is being so lazy about this, someone might have to write a Windows driver that disables this interrupt.

It is disappointed that the current symptoms is still not fixed since first report

Just got a new Macbook Pro for Christmas and this is the only issue I have. Here's what I do for now:

1. Added Task Manager to Startup. Then I run a link to "psshutdown" on my desktop to put the PC in sleep after it boots, then wake it immediately. As others have shown, System Interrupt and System go back to normal instead of running at 20-30%.

2. Sometimes when I plug in a HDMI connection I notice these tasks taking 20-30% again, so I do the sleep/wake routine again to fix it. Takes a few seconds, but it's worth it to not lose 30% of my CPU power. I've used the PC for hours, and it's usually only after booting up that I have to do sleep/wake.

Obviously the ACPI or firmware update with Yosemite or something is reading an unexpected value, and Windows relentlessly tries to read the value. After sleep/wake, the value is either reset or readable, and the problem goes away.

Hope they fix it soon! Babysitting this issue is a bit annoying. I have no issues in Yosemite's Activity Monitor, this is only in Windows 8.1, fresh install, updated or not with Windows Update (including the Intel updates).