Performance Issue on cakewalk bandlab version

I downloaded and installed cakewalk by bandlab today,and I found all of my sonar platinum project will cause cpu useage 100%.and I switched to sonar to open these project,every thing seems fine.
The project created by cakewalk by bandlab also cause this problem.
 
I am sure it's not the vst problem because this machine just running vienna ensemble pro.All the vst's and software instrument are running on my server unit.This is just a sequencer.I tried to remove all the vst's and just leave the midi and one track audio data,won't solve the problem.
 

JoseC.
Ummm...I just had time to play a couple of projects this morning, and I was getting audio dropouts that they were not happening before. I then opened them Sonar Platinum and I was getting the same, too. After closing Sonar I realized that I had left Bandlab assistant open. I had no time to check if I had found the culprit. I'll investigate further tomorrow as soon as I have time.

Yes, you are not the only one.but   I shut the Bandlab assistant,the  audio still dropouts.100% cpu useage 

azslow3
"Stop audio engine". Still the same?
Check for MIDI looping (disable all MIDI outputs in preferences, check for Echo/Auto echo on tracks)

i'm sure it's not the midi looping thing.this will happen every 5-10 second,100% cpu usage ,and audio engine drop.even I set the audio buffer to 2048 samples.
I've also tested a total empty project,with only one audio track or one instrument track,same issue.
but with the same project this won't happen in sonar.can't figure out why.

azslow3
Stop audio engine. Wait for a while. If you get significant CPU activity, it is not from CbB..
If you use Control Surfaces, remove them from preferences. As I wrote before, also remove any MIDI Outputs (and just in case... Inputs) from preferences.
 
Check VST settings. If you have auto scanning enabled, CbB can scan for VSTs. Depending from your installation, that can take long time. Set it to Manual.

Stop audio engine，cpu usage will return to normal.vst scanning was set to manual. still get this problem.