-
All replies
-
Helpful answers
-
Jan 28, 2015 1:29 AM in response to michalfrommartinby Zhyrnov,Updated from 10.10.1 to 10.10.2 final release, problem is resolved. EFI updated from B11 to B14 for my Late 2013 rMBP 13.
-
Jan 28, 2015 1:42 AM in response to Zhyrnovby michalfrommartin,OK. Problem resolved. Installed OS X 10.10.1 to internal SSD, updated to 10.10.2 and EFI updated to B18 from B16. High CPU usage is gone. Thanks Apple.
-
Feb 9, 2015 7:37 AM in response to kondratkby ambravoc,On Windows 7, Try this:
1. Go to Device manager. Right Click on Computer - Properties - Device Manager (listen in displayed on the left panel)
2. Select and Unfold "Display adapters".
3. Right Click on "Intel Iris.....XXXX" - Properties
4. A window with Properties appear. Select Driver Tab and "Roll Back Driver".
Thanks.
-
Feb 9, 2015 10:01 AM in response to sg][by a4840639,My MacBook 11.2 is on 10.10.2, and its firmware is B14.
The problem persists for me.
I also have lots of other problems on Boot Camp as well. For instance, the card reader will mysteriously vanish after a long sleep.
-
Feb 9, 2015 11:22 AM in response to a4840639by Reverse_Parn,Hmm, I have a similar model, 11.1. My Sys Info shows:
Boot ROM Version: MBP111.0138.B13
System Version: OS X 10.10.2 (14C94b)
The problem in Bootcamp with high CPU utilization was fixed for me during beta testing, but it looks like the release is out now: About the OS X Yosemite v10.10.2 Update - Apple Support
I'm downloading it now...
-
Feb 9, 2015 1:55 PM in response to kondratkby ambravoc,Fixed in Windows 7. Mode sleep and then wake up.
worked
Thanks.
-
Feb 10, 2015 5:01 PM in response to kondratkby saulthu,For what it's worth, I had a similar problem of high system interrupts in Windows 8.1 in bootcamp, happens regardless of OSX version. In my case it only happens after plugging in the thunderbolt-to-dvi connector for external monitor, on my MBP retina late 2013. The fix that worked for me was to install the latest graphics drivers from Intel for Haswell CPU, from https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=23162
-
Mar 8, 2015 7:38 AM in response to kondratkby vagaerg,Thank you very much, luckily the sleep/resume workaround is ok for me!
However, my EFI is not updated, I can see that most of you say that with B14 the issue is now, I have B11 and can confirm with this update it is still present. I haven't been able to update from 10.10 because I initially had 10.10, took it to the Apple store where they replaced the SSD and got it back with 10.10.2 but no EFI update. If I check for updates it says no updates found
What can I do? My main usage of the Macbook is Windows (it has always been) and I cannot be thinking of sleeping/resuming every single time.
Thank youMy MBP is a rMBP 13" i5 / 8GB / 128GB SSD Mid-2014
Boot rom: MBP111.0138.B11
-
Mar 8, 2015 1:26 PM in response to vagaergby vagaerg,Ok, found how to solve this. I downloaded the 10.10.2 update even though I had already installed it, and installed it manually (dmg file from apple website). This time it did update de EFI, everything works great now
-
Mar 17, 2015 1:18 PM in response to a4840639by areeb,I have the same problems as a4840649. I have a nifty card which disappears when bootcamp (Windows 8.1) goes to sleep. Also I still struggle with the system and system interrupts cpu usage despite being on B14 (hovers around 20 to 25% during idle).
Thankfully I don't use Bootcamp very often and the sleep workaround still sorts out the high cpu usage issue.
-
Mar 17, 2015 5:44 PM in response to areebby TheJohno,I have the same issue as everyone here. I'm running Windows 7 Professional 64-bit on my MacBook Pro 15" (Late 2013) model with Intel Iris Pro 5200 graphics. I am fully updated to the latest version of Yosemite (10.10.2) and there are currently no other updates for the system. I am also running on Boot ROM Version: MBP112.0138.B14 as others have noted. As soon as I boot into Windows 7 my CPU is at a constant minimum of 12% utilization and one of the cores (or threads?) is showing as being fully maxed in Task Manager. The only solution that works for me is to put Windows 7 to sleep then wake it back up.
I have verified that it is either the Intel graphics driver or something closely related to the driver. After uninstalling the graphics driver, the CPU acts normally. But as soon as I install the graphics driver (either the Apple provided one and the latest one from Intel) the CPU jumps back up to high utilization.
I'm not sure where else to go with this, Intel says to talk to Apple but Apple doesn't seem to have any kind of fix. Putting my PC to sleep isn't ideal for me and has been causing all kinds of weird problems. Sometimes, upon waking, various background processes will have stopped working at the PC won't function as normal. For example, often the Bootcamp software will stop working and I am unable to change the brightness of the display or keys. On some occasions, Windows will just completely crash and my MacBook will reboot.
I use both OS X and Windows frequently so this issue is cumbersome for me. I have never had so many issues with an OS until I bought this MacBook. Hopefully there is a fix soon.
-
Mar 20, 2015 4:22 AM in response to kondratkby deanb01,Yep, just noticed this a couple of days ago on my 2013 15.4" MacBook Pro. CPU running at around 20% in Windows 7. At first I thought it was an errant process but appears to be Kernel System Interrupts. Only appears to have happened since I updated OSX recently.
The laptop gets hot to the touch around the magsafe socket / Esc -> F4 keys if I don't do this.
The hibernate / close lid / awake fix works for me every time. Waiting for permanent fix as I also flip frequently between Windows 7 and OSX through the working day.
-
Mar 26, 2015 11:36 AM in response to kondratkby janjaapMBP,I have a MacBook Pro 15.4"(mid-2014) and i also encounter high CPU usage around 12% from system and system interupts in Windows 8.1. After closing the lid it's fixed. Intel driver and driver from Apple doesnt fix it unfortunately.
I hope someone comes with a permanent solution!
-
Mar 30, 2015 8:53 PM in response to cawhitworthby sonicartist,Hello,
I am also seeing this with my 2012 mac mini 2.6gHz running Mountain Lion. For many reasons I can not update to Yosemite. Have the recent updates solved the issues you were having? Has anyone running Mountain Lion solved this issue? I'm wondering if there is a way to update the firmware directly. This is such a mess.
-
Apr 8, 2015 1:15 PM in response to deanb01by deanb01,Still not fixed in update 10.10.3. Just saying.
