System and System Interrupts- high cpu utilization

The problem relates to the EFI update released with Yosemite.

Event Log: The embedded controller (EC) did not respond within the specified timeout period. This may indicate that there is an error in the EC hardware or firmware or that the BIOS is accessing the EC incorrectly. You should check with your computer manufacturer for an upgraded BIOS. In some situations, this error may cause the computer to function incorrectly.

Thousands of users are experiencing this problem. No need to report a new machine not working.

Temporary workaround:

1. Put the computer to sleep,

2. Wake it up

Thank You.

Solutions/ Suggested solutions/workarounds are welcome.

I got the same issue and apple please fix it immediately.

Has anyone gotten any updates on this? Any word from Apple?

I just filed a bug report, for what it's worth. I encourage everyone else to do the same: https://bugreport.apple.com

Same problem here. Macbook Pro 13' . The solution in this thread, that is, to sleep and then wake up, certainly works for me.

I'm looking forword to a perfect fix from apple.

from china

I have the same problem also, on a Macbook Air 13" 2013. And like the rest said, it works to sleep and wake up the machine, but really? Should this be necessary? Hope a fix will come.

Exactly the same for me. I searched for half an hour, and this produce the same results under Windows 10 Preview. Closing the lid fix it. Not very classy for such high computers.

same Problem here, hope we can get an update soon...😢

Yup, I am having the same issue on a Late 2013 Macbook Air running Windows 7.

The sleep/wake workaround solves it temporarily, but a fix would certainly be nice..

Have the same problem with same work around results.

Filed a bug report if it helps others to also file I filed the report here:

https://bugreport.apple.com/

And this was my report

Summary:

After updating to Yosemite and receiving an EFI update the CPU graph now reports a consistent 30% usage in Windows 7 x64, the laptop then warms up and fans go on.

This continues until I close then lid and let the MBA sleep.When I open the lid and it resumes the CPU then idles at a normal 1%.

The problem is detailed in this thread as experienced by many others. https://discussions.apple.com/thread/6598184?start=45&tstart=0

A clean install make now difference once the efi update has occurred.

Steps to Reproduce:

Update to yosemite

Boot into Windows (it does not seem to matter whch version of the intel gpu drivers you have installed).

Observer the task manger cpu graphs... they read 30%ish for CPU 1 and 2

Close the lid on the notebook and let it sleep or hibernate (whichever action is set in power management).

Open the lib and tap a key for it to resume.

Observe the task manager cpu graph now reads 1% when idling

Expected Results:

The graph normally reads 1 % when idling and system does not consume much power.

Actual Results:

The system consistently idles at 30%

Version:

Yosemite 10.10

Win 7 x64

Stock bootcamp gpu and windows drivers

Notes:

The sleep/wake work around works 100% of the time.

Tried clean install of both yosemite and windows

Tried different Intel GPU Win7 drivers including stock windows and stock bootcamp

Configuration:

Does not occur pre-Yosemite EFI update (tested with another MBA 2014)

Does occur post Yosemite EFI update.

:

I suggest anyone reading this thread and experiencing the same issue with same work around success file something similar....

~Steph

Same Problem here on a Mid-2014 MBP Retina 13" 2.6 256GB/16GB.

The CPU is constantly being used 60% by "System Interrupts".

Windows 8.1.

I have the same issue on my 2013 13" MacBook Air. This one has the i7 and 8 GB Mem with the 250GB ssd (the stupid one, not the good one). I've been using OSX 10.10 with Windows 8 since OSX was in its first public beta, but I don't remember having this issue until fairly recent... (last month or so).

Putting the computer to Sleep and waking it back up seems to fix the High CPU usage.

Thanks guys! I look forward to an actual fix.

~Reuben

Have submitted a bug report, I urge everyone in this thread to do the same.

I've lready received a response for further clarification, let's make this a high priority for Apple.

I'm gonna file a report rightaway.