CPU kernel_task Usage Rendering MacBook Pro Unresponsive

Question

For about a month I’ve been having issues with my office setup when docking/undocking my 15-inch 2012 MacBook Pro. As soon as I launch a couple of applications (Adobe Muse, Photoshop, Parallels, etc.) kernel_task begins eating up all the CPU threads, rendering the MBP unresponsive and nearly inoperable. I have been using my dasiy chain setup for over a year w/out issue prior to a month ago.
Steps I’ve taken to resolve the problem:
Resetting PRAM
Resetting SMC
Disconnecting Peripherals
Results from the steps seem to work for a little while, then the problem returns.  The one caveat to that is – the kerenal_task ramps up CPU even when all peripherals are disconnected.  I’ve been cautious of contacting Apple Support for assistance, as I’ve been unable to replicate the issue on demand. kernel_task just happens, and happens right in the middle of me doing something important.  This makes me believe my hardware has become faulty or I’ve recently installed some software that is affecting the functionality of the MBP.  Which isn’t a huge deal, I just want to resolve/pinpoint my issue so I can address it.
In researching the problem I’ve found the following threads that I believe are similar to what I’m experiencing.  Posts by Linc Davis have been extremely helpful, I just can’t seem to put a finger on my specific problem:
https://discussions.apple.com/message/22529264#22529264
https://discussions.apple.com/thread/4817768?start=0&tstart=0
Any and all suggestions/assistance would be greatly appreciated.
Note: Set up – MBP > Thunderbolt Display > Seagate GoFlex Desk Thunderbolt Adapter w/ HD attached > 2005 20” Cinema Display.

Answer 1

Preface:
I had iStat Menus installed and it seems this was the root cause of the kernel_task issues I was experiencing.
After taking the Thunderbolt display and MacBook Pro to the "Geniuses" to verify that the issue(s) were not being caused by my hardware, it boiled down to pinpointing a software inconsistency.  A post made by Linc Davis helped me start the digging.  He mentioned in one of his post that:
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.
I tried uninstalling the software to see if that would solve my problem.  Unfortunately it didn’t; therefore, I went about making a full Time Machine backup, a system clone using Carbon Copy Cloner, and reformatting and reinstalling OS X.  This may not be the ideal fix for some of you, but fortunately I maintain many backups.
For me, that solved my problem!  The kernel_task hasn’t shown up for over a month and everything is running extremely smooth.
Note: This is really not desirable for the majority of you, as it is highly time consuming and may not be practical for you, but it is definitely a surefire way to solve this problem.  I didn’t restore from any of my backups, I only made backups for a “just in case” instance.  I decided to do a fresh install and set up my system from scratch.  I maintain all my software DMGs and serial numbers on a separate HD which made this a smooth way for me to go about restoring my workflow.