Ever since Splat , My first core is way higher than all the others.  I have contacted support , and we have done core parking which dose not seem to work, 
 I have done a bunch of other things as directed and its still the same.  I am also wondering if it could be a plugin , Could a plugin cause uneven cores even if its not loaded in the project? I do notice Rounds from NI is a resource hog, I can only have about 3 instances before I hit the red on core 1 .
 Even without rounds loaded the first core is higher than the rest. Could this be a setting or bug in the software?  I really like to find the culprit. With Splat Im actually running into a brick wall . Its seems like I need more Ram a bigger CPU. And I never did before, I believe my spec are more than adequate.  Perhaps I should have someone connect remotely to see if they can tweak my system. Any suggestions would be great Help. Thanks Again John

Yeah, my first core is always higher than the rest. Core parking helps a little, but for me, it's been that way from X1, X3, and Splat. There's a logical reason for it (that I can't remember right now). Scook explained it very well one time, maybe he'll explain it again for us.

IIRC the first core handles all the maintenance and management of the other cores as well as its own load. 

Hi, may be you can explain what tweaks you have done so far.
dan
 

My first core is also higher than the rest. Always wondered about it, but never gotten around to checking why.

me too.  It is the limiting factor so far in heavy loads.
 

The first core is also "Windows workhorse" since every machine has a Core 0 regardless of CPU type. Additionally (and what you may be seeing), some plugs are scripted to also use this core (possibly for the same reasoning), and SONAR can do nothing about this since it is only a host. One offender I have seen mentioned regularly is Ozone 5, but there are others.
 
Unfortunately there is no "ready reference" for what plugs do this (among other things), and the best way to learn these is via trial and error. Basically save the project with a new name, then begin deleting plugs while monitoring CPU overhead (via Window's Resource Monitor) is preferred.
 
However, if you are not noticing performance degradation from what you are seeing, the simple fact that you can see it may be your nemesis (out of sight, out of mind thing). Many similar threads have gone down the path of "But I can SEE it, therefore it must be resolved."
 
If you do get into situations where degradation occurs is where renaming/deleting plugins will come in handy (or bumping up audio buffers to lower CPU strain).

I have done Core parking, as per instructions with no changes, I adjusted my buffer , I made sure speed step was disabled in the bios. I've done a bunch of other tweaks as per jose's thread. and its still very unbalanced , i can load up a new project and I can see my first core peaking over the zero line while there's zero activity on 2,3,and 4 .
 when I get back home I'm going to load up x3 with a new project and see if I have the same results..