You could try changing "ThreadSchedulingModel" from default=1 to 2. May help ... or not, but quick and easy to test and set back ...
ThreadSchedulingModel=<0 - 2>This variable goes in the [Wave] section and controls the interaction of the main audio thread and worker threads on multiprocessor systems when the Use Multiprocessing Engine option is enabled. Dependingon the system, a particular model may result in less glitching and better overall performance. The values are as follows:0 = Same as previous versions of SONAR. 1 = (default) Better thread balance. Model is more efficient and can provide cycles for other tasks.2 = Additional worker thread is created. This may result in improvement with Quad processor systems or higher. Not recommended for Dual processor systems.Thanks for the tip. I didn't notice any real difference when changing the settings. Core 0 is still considerably higher than the other 7. Still can't figure out why this does this.