Why does my Kernal_Task run so high when I first start up the computer

Question

Okay...I recently found out that my macbook pro 13in late 2011, main problem is my Kernal_Task......I notice it started happening this past Saturday. Everytime I put it to sleep, my CPU kernal_task runs high of 204-396% which is not normal. Then my fans kick on afterward.....it does the same thing when I properly shut down the computer and start it back up again, with nothing running or open. I did the Disk Utilty of Repair Disk Premissions, and still it is an on going issue with the kernal_task. And before all this happened, I never had a problem of putting my macbook to sleep at night, and wake it up the next day. Sometimes, I don't shutdown until 3 or 4 weeks at time....but now, since my kernal_task is acting up, I was told I now have to shut it down when I am not using it, like a PC machine. Can anyone here give me suggestions to sovle the kernal_task problem, of having it go back to normal use at 2-5% of CPU use, instead of 204-396% of CPU use....I am hitting a wall and want to find out if I have to reinstall OS X Lion or not...
Thanks...

Answer 1

The kernel is using excessive processor cycles. Below is a partial list of causes for this condition.
Throttling
When it gets high temperature readings from the hardware, or a low-voltage reading from the battery, 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 or sensor
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 battery power, the fault is in the battery or the logic board.
The Apple Hardware Test or Apple Diagnostics, though not very reliable, is sometimes able to detect a bad fan or sensor.
Installed software
User-installed software that includes a device driver or other kernel code may thrash the kernel. 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 booting in safe mode. Note, however, that disabling a system modification without removing it or booting in safe mode may not be as easy as you think it is.
Corrupt NVRAM or SMC data
Sometimes the problem is cleared up by resetting the NVRAM or the SMC.
Peripherals
Connecting an external display to some MacBook Pro models via Thunderbolt may cause this issue. I don't know of a fix, other than to disconnect the display.
Encryption
Transferring large amounts of data to or from an encrypted disk image or FileVault volume may put an extra load on the kernel. If both the source and the destination are encrypted, the load may be doubled. If you transfer data from an encrypted disk image on an encrypted partition to another such image on another encrypted partition, the load may be quadrupled.
This issue probably doesn't affect late-model Macs with an Intel i-series, recent Xeon, or later processor. Those processors support hardware-accelerated encryption. You can determine what kind of processor you have by selecting About This Mac from the Apple menu in the menu bar.