Obviously, you can't kill kernel_task in Activity Monitor.
The kernel is using excessive processor cycles. Below are some possible causes for the condition. Some may not apply to you.
FileVault
Please open the Security & Privacy pane in System Preferences and select the FileVault tab. If there's an indication that encryption or decryption is in progress, wait (maybe several hours) for it to finish and see whether there's an improvement.
Throttling
When it gets high temperature readings from the hardware, or low voltage readings from the battery of a MacBook, the kernel may try to compensate by interrupting the processor(s) to slow them down and reduce power consumption. This condition can be due to:
☞ a buildup of dust on the logic board
☞ high ambient temperature
☞ a worn-out or faulty battery in a portable
☞ the malfunction of a cooling fan, a temperature sensor, a voltage sensor, or some other internal component
Note that if the problem is caused by a sensor, there may be no actual overheating or undervoltage.
If the computer is portable, test with and without the AC adapter connected. If kernel_task hogs the processor only on AC power, charging is causing the machine to heat up. That behavior may be normal for some models, but it may also be an indication of a hardware fault.
Apple Diagnostics or the Apple Hardware Test, though not very reliable, is sometimes able to detect a fault. For more thorough hardware testing, make a "Genius" appointment at an Apple Store, or go to another authorized service provider.
If nothing is wrong with the hardware, then whatever you can do to improve cooling may help.
Installed software
User-installed software that includes a device driver or other kernel code may thrash the kernel. That category includes virtualization software, such as Parallels and VMware, as well as most commercial "anti-virus" products. Some system-monitoring applications, such as "iStat," can also contribute to the problem. You can test for this possibility by completely disabling or removing the software according to the developer's instructions, or starting in safe mode. Note, however, that disabling a system modification without removing it or testing in safe mode may not be as easy as you think.
If you're not sure what software could be contributing to the problem, please hold down the option key and select
System Information...
from the Apple menu. The System Information window will open. Select
Software ▹ Extensions
from the menu on the left. After a delay of a minute or so, a list of all installed kernel extensions should appear in the upper right pane of the window.
In the extension list, click the heading of the column Obtained from twice to sort it by source, with Apple at the bottom. At or near the top, you may see some third-party extensions. Select one, and information about it, including Location, will appear in the lower right pane of the window. What do you see?
Corrupt NVRAM or SMC data
Sometimes the problem is cleared up by resetting the NVRAM or the SMC.
External display
Connecting an external display to some MacBook Pro models while the lid is open may cause this problem. If applicable, use the external display in clamshell mode.
Other peripherals
Disconnect all wired peripherals except those needed to start up, and remove all third-party expansion cards (if applicable to your model.) If the problem is resolved, reconnect the devices one at a time until you identify the culprit.
