One thing I noticed when dropouts occur at the same place every time is that there's new clips starting up during the song, and I have a sudden increase in plug-in CPU consumption because 4 or 5 CPU-intensive plug-ins are being "kicked-in". In this case, I simply freeze the track, so that it will go ahead and calculate all plug-in processing for complex tracks (especially those with lots of Lanes). That helps me reduce or eliminate the expected drop-outs.

fHumble fHingaz Hi all,  I'm having some problems with Sonar X2a and was wondering if anyone might be able to help
 
The first, most annoying one is that when I close some of my projects without saving (which I often do if I want to just check something I did in a mix & leave it untouched), it freezes.  I have to close Sonar down completely.  Then it refuses to open again until I shut my computer down & restart.

 
I also sometimes experience the freeze/crash when closing projects.  I don't reboot, I just kill the sonar process (and sometimes the dreaded bitbridge process) and I can again open Sonar.  I've also been experiencing other Sonar crashes and the intructions from tech support was to do a full uninstall/re-install.  Will be doing this later .
 
P.S. Be sure to check the Windows Event log (Application section) to get details on your crashes.  It may help you find the root issue, and it's useful info to give to tech support, if you choose to contact them

stevec

fHumble fHingaz
No, Sonar X2 will not re-open after it has crashed (until I re-start the computer) - the soundcard however, still works with other DAWs that I have installed on my computer (eg. Sonar X1, Reaper, Mixcraft 6) immediately after Sonar X2 has crashed without the need to restart.  
 
 

I think Bibs meant that SONAR may be still running in the background; i.e., in Task Manager.  If so, that would prevent it from loading up using the shortcut.  Apparently MAudio drivers have a tendency to lock the SONAR executable under certain conditions, even if other apps are able to access the drivers after the fact.
 

Correct
 
I can confirm this first hand.

+1.
 
Used to get this alot when I had crashes with my M-Audio keyboard plugged in.
 
little tip for you: try 'logging off' and 'logging back on' in windows, much faster than rebooting

Ok, thanks for the help everyone! - you've given me a lot to check out.

little tip for you: try 'logging off' and 'logging back on' in windows, much faster than rebooting
 
 
Thanks - This worked really well!

+1 on audio drivers not being released as something to check out for this symptom - I've had this as well historically, but with a different audio interface.  Once a new version of their driver came out, the issue was resolved completely.