Q: Problem with Kernel Task - El Capitan

This is what my machine was doing, Kernel Task was using 900%(?) processor with nothing connected to my 2011 MBP.  I first had this issue with Yosemite too, and this fixed it.

Hello there,

I have an iMac12,2 (model identifier) - which I removed according to the instructions.

But didn't do the trick unfortunately.

I have an iMAC 27-inch running El Capitan.

Ever since I have upgraded my memory has been eaten up by kernel_task. Right now it is at 1.25GB

Is there something else I could try?

The iMac12_2.plist file has been removed from that folder --- actually this solution did work for me before I upgraded but NOW

kernel_task is sticking around and my Mac is slooooow...

Thank you in advance for your advice

Chaba

Same here. I'm only able to copy it to another folder. It still remains. Reeeeeeally frustrated!

yeah been having kernal problem since Yosemite too, I have a late 2011 MBPro. I now carry my power adapter with me all the time. Seem silly but that the only way my laptop wont slow down. I was thinking of buying a new macbook pro laptop since this one was getting outdated but I done with apple laptop now. my next buy will for sure be a window book or surface pro.

Follow my instructions on booting into recovery mode and disabling file protection.

Did the solution I posted not work for you?

I have a MacBookPro11,3. Unfortunately this identifier does not exist in the Ressources folder.

The highest number is MacBookPro8_3.

What should I do?

Where can your solution be found?

thanks

Click on Go to original post, read This solved my issue...

I'm working on a 2013 iMac that was brought to my office because the fan is always at its maximum speed. Initially I thought it was just a problem with the fan, but before ordering a new one I noticed that the Kernal Task is Shreking the CPU. I tried your fix for the issue, but terminal replies "command not found". (I'm stuck at step 0). Any help would be greatly appreciated.

http://www.howtogeek.com/230424/how-to-disable-system-integrity-protection-on-a- mac-and-why-you-shouldnt/

Thanks! I'm so close now, but there's one more problem.
My system report says "iMac14,1" which is nowhere to be found in the resources folder of the path you specified. There's a list of very similar ones, such as "iMac12,2" but no iMac14,1

If deleting the file that relates to your machine doesn't hurt anything, I can't see how deleting the rest would either.  Just copy that entire kext to your desktop or somewhere, then delete it from the system folder.

ps  This stopped the kernel task issue, but my fans have been running full blast since the Yosemite update - AHT shows a faulty temp sensor, but I can't find to which one the error code corresponds.

Thanks for getting back to me
     I already tried deleting all of the files. I put them in a folder on my desktop and deleted them from their native location. After restarting, the kernal_task was still at 98% and the fan was still hitting max speed (from about 50 seconds after booting, and maintaining speed indefinitely unless shut down). Keep in mind this is a late 2013 iMac. It's not one of those iMacs where you can just take a suction cup to the glass screen, pull it off, unscrew the casing, and access the hardware right away. You have to take a plastic too to this screen and carefully "scrape" the screen off of the fitting. It also requires a 20 dollar glue kit from apple every time you remove the screen. This iMac is so slim that the "fastest" way to replace the on it RAM is to remove the entire motherboard. However, you can't remove the motherboard without removing the fan, the PSU, and loosening the left speaker. My point is that this is still a new and only lightly used computer. It has a 2.7ghz Intel Core i5, 16 gigs of RAM, Intel Iris Pro graphics, and a 1TB drive with 979 gigs of space free. It was purchased by Outside Magazine for one of its designers and they expected it to work properly for longer than it has.

As mentioned, I did try deleting all of the files. After spending 15-20 minutes staring at the list, hoping I was somehow overlooking the 14,1 file, I ended up taking my chances and just deleting them all. Hardware aside, I have nothing to lose with this iMac. I have already done a clean install on it multiple times with an external optical drive. The fan/kernal issues persist even before upgrading to Yosemite. To make thing even weirder, one of my first attempts to fix the problem involved replacing the HD with the drive from my personal Macbook Pro (which doesn't have this issue). Although the iMac booted up with my username, password, background color, files, and programs, it still had the issue with kernal_task eating up the CPU. Obviously something is causing the kernal task to consume the iMac's CPU, but it's as if the cause is in no way related to the OS, any of the iMac's files, or even the Hard Drive itself. In fact, I'm pretty sure I can even remove the hard drive completely and boot this guy into diagnostics with a disk, and the fan will STILL go nuts. The reason I assume this is because I've booted her up from an external OS installation disk, opened activity monitor in the utilities, and found the Kernal task eating the CPU. Even though the hard drive was not disconnected, it had not been booted from.

As a full time IT-technician, it's my job to fix this iMac for the company I work for. It's not like I'll lose my job if I can't, but I would really appreciate any addition help/options. I'm still new to this job, but this is the only issue I've encountered so far that has left me clueless.

Thanks in Advance,

love you Badgermonkey

-Will

At this point I would take it to an Apple store as it seems to be hardware related (I don't think that it is, but I would love to have Apple address this issue).  Apple's come with a 3 year hardware warranty, as I'm sure you're aware.  The last time I supported Apple products in at IT department, it was pretty standard to take machines with obstinate issues to Apple.  We could handle most issues, but Apple products seem to have some sort of sorcery included in the hardware and software that just isn't documented, or I can't find it.