Problem with Kernel Task - El Capitan

Since I have upgraded my MacBook Pro to the new OS, when it is unplugged, the Mac slow down and the Cpu usage is from 120 % to 300 % ( the process is Kernel Task).. What can I do?

Thanks a lot

MacBook Pro (13-inch Early 2011), OS X El Capitan (10.11)

Posted on Oct 1, 2015 2:02 PM

Reply
94 replies

Nov 19, 2015 5:18 PM in response to Will87501

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.

Nov 25, 2015 7:39 AM in response to Will87501

As an IT pro to another, let me run this by you: I was onsite, and after driving >5 hours I swapped out my battery (my AC converter died) on my MBP late 2011 15", and tried to boot into my Win 7 bootcamp partition. It booted, but the screen was black. I used a Thunderbolt/HDMI converter and connected it to the TV where I was working (70" Samsung), everything looked beautiful. Checked hardware monitor and my laptop display isn't listed. I reseated all the connections, put the other battery back in, still black screen. Reset SMC, PRAM, still black. Tried a trick I found with google where I put the monitor to sleep, forced a reboot, still black. I let the battery bleed down until it hibernated, plugged in, still black. I'm about to swap it for another screen that I have with a broken bezel just to see if it's the actual screen, but I was hoping you may be able to shed some light on this.


Sorry we didn't resolve your issue.

Nov 25, 2015 8:49 AM in response to Badgermonkey

Hey Badger,
No worries about the issue I had. I really appreciate all your help. I ended up just taking it to an apple service place since it was still covered by apple care. Despite the fact I've voided the warranty in at least 10 different hardware-related ways, it looks like they will be replacing the motherboard for nothing more than a 30 dollar service fee!


Anyway, as for you issue:
A 2011 MBP should be able to boot regardless of the battery, as long as it's plugged in to power. I guess I'm not certain, but I vaguely remember booting a 2010 MBP with the battery completely removed. Although the black screens may have initially been caused by a power/battery issue, I'm not inclined to assume that they're ongoing occurrence is power related.


Can you hear the hard drive kick on at all when you boot? I assume yes. But does it shut off when you get black screens? I'm not suggesting that the power cable to the HD is failing, but in my experience, older MBP's usually make little "writing/reading" noises if their actually doing something. Try paying attention to the HD sounds before and after the black screen and let me know if you notice a difference. We need to find out if the problem is related to important internal hardware, or just some faulty cheap internal display cable.


If the drive is operating regularly and you're still getting black screens, then your internal display cable or GPU is probably going bad. If it's the display cable, you're in luck obviously. But if it's the GPU... that *****! Mid-10 to 2011 MBP's have a known GPU issue. In fact they were "recalled" without customer notification. Or.. "owner notification", w/e. You essentially had to have already had the problem and sought help in order to get a free replacement (whether you had apple care or not). If you're able to boot into safe mode or from a disk you may be able to find crash reports. If you see a "GPU Panic" report anywhere, you're screwed. And by screwed I mean, even if you do get the macbook to boot naturally with its own drive, files, and respective OS partitions, you'll never be able to run photoshop, imovie, or Left4dead2 (😝) ever again for more than a matter of minutes, and you will have to run GFX card status to disable your discrete graphics and force your integrated card at all times.


When you hold option at boot, what happens? You're able to select which partition to boot from? Do you have a backup? The first things I do when I come across weird situations like this are:


1. Get another MBP, take the HDD out, plug it into the MBP that's having issues, try to boot.
2. Take the HDD out of the Macbook Pro that's having the issue and try to boot from the drive with another MBP. You can also use an iMac or mac desktop. In fact, you should be able to use really any mac computer. You can also boot from your drive externally if you have a dock.
2. Remove one of the sticks of ram and try to boot normally.
3. Put the stick you removed back in, remove the other stick, and try to boot normally.
4. Run Apple Hardware Diagnostics via disk or flash drive.
5. Unplug all easily-unpluggable motherboard, hard drive, display, power, sensor, and optical drive cables from the inside of the MBP and plug them back in, then try to boot normally.
6. Does your model have a CD drive? If you have a sata to microsata converter you can try booting from the drive via your optical drive's sata, rather than your Macintosh HD sata.


I know you probably don't think the issue is related to the hard drive, but if you can manage to boot safely from the drive on another unit, you will have definitely narrowed down the cause of the problem.


Let me know if any of this helps!

Nov 25, 2015 10:01 AM in response to Will87501

It boots fine, I can even play iTunes (because I can login and use the media keys with no screen). As I said, when it first happened I connected it to an external display (70" Samsung) and everything was beautiful - Bioshock Infinite looked great, but ran like crap because 4K / ATI6750 w/512MB 8(. I got one of those 2011 MBP's cheap with a faulty nVidia GPU (shame too, it's a 1GB card) and was able to boot it a few times. I tried to lock out the discrete card but didn't have any luck, even with GFX app. Now it's spare parts, and I did swap out the screen a few months ago after I broke the bezel on mine, and it's where the spare battery came from.

So yeah, it boots normally, but the computer isn't seeing the screen at all. It probably is the cable but I've tried with the screen at all angles and nothing, it just stays black like it's not even connected. Weird, since I didn't even touch the cable when I swapped the batteries, and it worked perfectly moments before.


O yeah, I also replaced the drive with a 1TB hybrid drive, replaced the Superdrive with the old 750GB as a Time Machine backup drive (not concerned with backing up the 250GB bootcamp partition - all my saved games are in the Steamcloud, and that's all I do with that other than the occasional bit of work/MS Office which I immediately email to whoever is still forcing me to use Office), and upgraded to 16GB DDR 1333 ($75, thanks newegg!).

Dec 1, 2015 9:06 AM in response to RonSwordsman

For me, the issue was logic-board related and required a replacement. My model (14,1) also did not show up in the list.
If you have any other working apple computers laying round, try swapping the hard drives. Put the working mac's hard drive in the mac that's having the kernal task problem. It should boot fine. You can even put a macbook or macbook pro's drive in an iMac and it will boot as if your iMac were your macbook. Anyway, if the kernal problem still happens when booting from an OS on a totally different drive, then the problem is surely motherboard related.

Dec 2, 2015 6:18 PM in response to Linc Davis

This is not a hardware issue, it is purely a firmware issue related to Yosemite and El Capitan. If you have already attempted to reinstall your operating system, next step would be to make a Genius Bar appointment Apple and have restore computer back to factory settings. Issue will be resolved. You can attempt to restore from backup, but i've noticed that the issue returns after, so the for sure fix will be to restore back to factory settings in an apple store and setup the unit as new, then you can "Enter Time Machine" and manually restore data.

Dec 10, 2015 11:07 PM in response to Linc Davis

This was on a SkyLake iMac 5K. Resetting the NVRAM solved the problem.


What made me optimistic it would work is that the NVRAM Apple KB article mentioned speaker volume might be one of the parameters that would have to be re-configured after NVRAM reset. My external speakers (connected via USB) had been randomly cutting out; power-cycling them fixed the problem, but was clearly not its cause.


Kernal_task went from top CPU process, consuming 20-70%, down to ~1%.


Thanks again!

Jan 5, 2016 10:50 AM in response to pacca.info

Dear Everyone that can't find your specifice device in the kext - We're trying to remove a corrupt/something preferences type file from your machine so that it will resort to a default setting. You don't really need the ones for any other device, so just remove the entire kext.


The worst thing for me now is an OS upgrade immediately hoses my kernel task so an upgrade while it's using 1000% processor takes 24-72 hours.

Jan 18, 2016 9:11 AM in response to Badgermonkey

As someone who is essentially only a software user, making changes in Terminal scares me a little. So, this is probably a stupid question, but if I delete this plist, the computer will just replace it with one that is not corrupt? If I choose to delete the ACPI_SMC_PlatformPlugin.kext, this will also be replaced with one that is not corrupt?


Sorry if these questions are basic, but that is my level of understanding on these things.

Jan 18, 2016 9:23 PM in response to Brian Rizer

making changes in Terminal scares me a little

It should scare you a lot. This wretched thread is full of dangerous, irresponsible fake advice.

this is probably a stupid question, but if I delete this plist, the computer will just replace it with one that is not corrupt?

It's not a stupd question. It's exactly the question you should ask. The answer is no. You'll have a corrupt installation that can only be fixed by reinstalling the OS. You should never delete or modify system components for any reason.

If I choose to delete the ACPI_SMC_PlatformPlugin.kext, this will also be replaced with one that is not corrupt?

Same answer.


I suggest that you ignore everything you've read in this thread and instead start your own with a full description of the problem. You'll have as much chance as anyone else of getting a useful response. You have none here.

Jan 27, 2016 9:21 AM in response to Linc Davis

It is scary only in as far as the only acceptable solution to a logic board having a malfunctioning sensor (or camera, or whatever) requires replacing the logic board (a service apple will happily charge you ~$750 for), or buying a new computer. A comparison to this would be a car manufacturer crippling your car if the seat warmer malfunctions, forcing you to only be able to ride in first gear until you fix it. The manufacturer states that the only thing you can do is pay ~70% of the cost of your car to replace all the electronics within it, or buy a new car.
The solution posted by Badgermonkey to override the malfunctioning kernel_task process has been around for years and I have not seen any reports of people having their computers damaged by it. Even if it does, your logic board is already considered scrap by Apple anyway, so who cares.
As long as your temperatures are fine and you peg your fan speed to your cpu sensor (which you can with some free software called "Fan Control for Mac". I have mine start to increase fan speed at 50C and run at max speed at 85C) so it's not running at 100% speed all the time you should be OK.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Problem with Kernel Task - El Capitan

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.