System and System Interrupts- high cpu utilization

Strange!

Actually I am using the Apple Thunderbolt GbE adapter with Windows 8.1 fast startup enabled and it works without any problem with my 13" Macbook Pro Retina mid 2014 :-)

Which Macbook do you have?

Does the Apple Thunderbolt GbE adapter work if you disable Windows 8.1 fast startup?

I have 13" MacBook Pro Retina Late 2013 with Windows 8.1. Adapter works fine if fast startup disabled.

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

MacBook Pro 13" Retina mid 2014

@zChip

Sorry, you are right. I also have the same problem with the Apple Thunderbolt GBit adapter not working when I restart Windows 8.1

When I shutdown or hybernate Windows 8.1 the Apple Thgunderbolt GBit adapter keeps working.

Apple tells you that their MACS can run Windows.. Like f*** yeah... But apparently they never tell you that they can't run it well and smoothly. Piece of junk software that they never bother to fix before releasing. I regretted buying a Mac. Nuff said.

I get the frustration.. in past you'd want to hunt down the latest drivers to reduce dpc latency etc but these days it's been pretty smooth sailing.... this is prob the most serious thing to happen recently and even this isn't that huge given there's at least a work around.

~Steph

Having the same problem. Running Windows 7 Pro 64-bit (BOOTCAMP) on a 2013 Macbook Air 13' (Yosemite with latest update). ~30 CPU from System Interrupts all the time. Temporary solution (sleep/wake) works for me and CPU utilization goes down to nominal values (e.g. 0-2%).

Dear Apple,

Please address this major software glitch as fast as possible.

Thanks.

Apple be like, yeah you bought a Mac? Good for you, now I've got your cash b**ches. What you gonna do bout it?

Lesson learnt the hard way, I'm NEVER EVER gonna buy a mac. EVER!

I agree with the recent posts here. This is getting ridiculous. I bought a $2,000+ MacBook Pro a few months ago knowing I'd mostly be using Windows. It is not acceptable to break Windows compatibility with the launch of Yosemite and then be completely silent on the issue and when it will be fixed.

Has anyone tried the 10.10.2 pre-release? I'd try it but from what I'm reading there's a lot of stuff broken on the Mac side so it's probably not a good idea. And I can't find a real changelog that tells what's actually fixed in the release so who knows.

It's not ridiculous, everyone make mistakes. It so happens that apple made one and now they need to fix it. Everyone just calm down. Obviously they didn't do it on purpose and now they know about it they want to come up with a fix, test it, then deploy it.

Be patient... updating a bios across a range of devices is tricky and they would want to test it.

As a software engineer, I'm going to stick with my opinion that it's ridiculous. They pushed Yosemite with total disregard for Boot Camp users.

Also, numerous people here reported this bug to Apple and the response everyone got was "marked as duplicate." As an engineer, I can tell you that absolutely does not guarantee they are working on a fix. Hence why more communication is needed from Apple.

Lastly, if Apple can't properly support Boot Camp, they should stop advertising it as a feature. I would've gladly gave my money to a PC manufacturer had I been aware of this issue that has now been around for months.

Same issue here. Nothing new to add, just hoping Apple will take notice.

I have the same problem, but I also have a question. When Apple releases an update to fix this problem, will I have to be running Yosemite? At the moment I am still running Mavericks, but will I still receive the firmware updates when they are released?

Same Problem here since upgrade to OSX 10.10.

This is wat Intel says https://communities.intel.com/thread/56126

So the say we should contact Apple for this Issue.

So could Apple please check what the problem is???

I too have this same problem on MB Air with windows 7 on bootcamp. Is there any permanent fix yet?