Next time it hangs - try firing up Task Manager and seeing if you have something called BitBridge running.  If so, it means that one or more 32-bit plugins are running in Sonar, and this is a potential thing that can cause issues.
 
What I mean is that sometimes some 32-bit plugins just wig out when being 'bridged' to be able to be loaded and used in a 64-bit Sonar project.  A frequently seen symptom of that is to see BitBridge running when Sonar is hanging.
 
I WOULD like to see you run a test, where you launch Sonar, and then hold the Shift key when you open the project that seems to frequently hang Sonar.  This will tell Sonar to open this project in its 'Safe Mode', and it gives you the opportunity to pick and choose which plugins get loaded for this iteration of loading the project.  It will ask you for each plugin, if you want to allow Sonar to load it or not.  I would like you to NOT let Sonar load ANY plugins, and then I would like you to exit Sonar (no saving, just a regular exit), and then post back on whether or not Sonar hangs or crashes.
 
If Sonar does not crash or hang after the above, it would point to there being some kind of issue with one or more of the plugins associated with that project, and it then gives us something we can work through until we identify specifically which one(s) are causing the problems.
 
If Sonar STILL hangs/crashes, that is also revealing, as it means we need to look to some other cause for the problems.
 
By the way, if your latency is as high as it is - and you are recording, rather than mixing, I think you will want to revisit the settings for our ASIO Buffer Size (assuming you are running with ASIO drivers).
 
So please run the above test and post back, and when I get back from running my 84-year old mom to the doc, I will jump back in to tr to help.  Others will likely be assisting as well.  :)
 
Bob Bone
 

In case it was not done after upgrading make sure to follow these instructions http://www.cakewalk.com/S...ommended-for-Upgraders

dbmm
That's whats so frustrating. Seems like I spend half my time diagnosing problems instead of creating music. Sometimes the crash occurs during save, sometimes I can save and when I exit it crashes. One thing that seems consistent is that Sonar or something in Sonar is hanging on to the drivers, because they are unavailable after the crash until I unplug the interface and force the process that's hanging on to the drivers to give up.

First of all...I hear you. Years of reviewing audio software has given me the "pleasure" of experiencing all kinds of anomalous behaviors involving various pieces of hardware and software from multiple manufacturers. One of the many reasons I've stuck with SONAR is because in my experience once you get it working, it stays working. Windows is not the best environment in the world for high-performance applications...great for spreadsheets, though 
 
Did you check for updated drivers from Roland? They made a big difference in my system. Also please check out the link to the tip in my previous post. No guarantees, but I used to have to set the latency high to avoid the problem you mention. Disabling that one driver let me reduce latency dramatically and still avoid crashes.

Just had another crash during save. Haven't had enough time to go through the plugins one by one yet. One thing puzzles me though. Once I've had a crash, if I reinstall the latest Sonar patch (E) it heals my system for awhile and I can save again. The problem is over time, it varies, the crashes come back. Install patch, it works again. Rinse and repeat.

Downloading updating. Will be out of town for a few days, will have to resume when I get back.

Test tones, azimuth, cotton buds and alcohol. And striping time code... Yey.... But please don't make me do it again...

This probably isn't the same thing, but I have a thread open about an older project that autosaves every few seconds up to one minute - even though my auto save was set to every 10 minutes and 30 changes.   Basically, autosave in this one instance, actually happens so much that it locks the project - screen goes white, have to kill the project.  Again - this probably isn't the same thing, but it might be worth looking at.  
 
Best Regards,
 
L 

brconflict

CakeAlexS
Test tones, azimuth, cotton buds and alcohol. And striping time code... Yey.... But please don't make me do it again...

One other advantage to tape: If you like your mix, you can very quickly apply any changes to ALL the songs on tape by simply playing them all through the mixer at once.

I think that would be true only if all instruments are assigned to the same tracks in all songs, otherwise you have to repatch. You could do the same thing in a DAW if all instruments are assigned to the same tracks in all songs by loading all songs sequentially into a single project.

Anderton

brconflict

CakeAlexS
Test tones, azimuth, cotton buds and alcohol. And striping time code... Yey.... But please don't make me do it again...

One other advantage to tape: If you like your mix, you can very quickly apply any changes to ALL the songs on tape by simply playing them all through the mixer at once.

I think that would be true only if all instruments are assigned to the same tracks in all songs, otherwise you have to repatch. You could do the same thing in a DAW if all instruments are assigned to the same tracks in all songs by loading all songs sequentially into a single project.

In many situations this might just be the case. I checked my PM's and you should have seen a screencast I made regarding PSG's. It's a bit long-winded, but if I had a really good way to detail how this could work, I think it would be quite useful, and in fact, complimentary to something.
 
To address the problem of mis-matched tracks between these Projects. That could be solved by either inserting blank tracks manually (the trashy way), the PSG could automatically insert a PSG dummy tracks for proper track-numbering, or simply this collection may not work well with PSG's. Some don't. I find that, in a single album, especially in Rock or Punk, the drums, for example don't ever change, or, if I add something to one project, not appearing in other projects, I can either remove that different project from the PSG, or simply move those extra tracks to the highest track #'s possible.
 
However, many times, we might edit a buss fader or EQ setting, which may totally be duplicated across all Projects, for example.
 
btw, the screencast isn't clear on a couple of aspects: You can sync as little or as much as you want between projects, and any one of the open projects can be Master of the current changes, so long as that's the one you click the PSG button in. There are many different situations people find themselves in, but if your workflow would adapt to this thinking, the PSG might be a real time-saver.

just remember when saving to let things chill for a second.
while we do live in the 20th century it seems like saving while the transport is rolling should be a reasonable thing.
but I wouldn't suggest it. like I said, wait for a second before saving, it could be while your saving something is trying to update, a preset, a plug in, a driver and thus when you try and save it gives you the whitey.
 
good luck.

What are the plugins causing issues?

FWIW I've been told that majority of Cakewalk's tech support calls involve third-party plug-ins.

I am not sure if I caught all of the context of this thread, so not sure if the crash is more on exit or save. A hang on exit can easily be caused by taking resources away from SONAR that it is using. SONAR does adapt to this but can take a moment to do so (Windows is the "middle-man" for this, and SONAR is dependent on Win7 to tell it what is available). When exiting always save/exit SONAR before removing a MIDI controller or audio interface (reverse is true for bringing SONAR online).
 
The reloading the E patch being a temporary fix sounds odd; there has to be a very repeatable recipe causing this issue (plugins, drivers, work flow, and the like). Win7 can also be invasive in taking control of an audio interface unless forced not to (making it unavailable to SONAR). I am not familiar with your interface, so not sure if it plays well in the sandbox with others "sharing" it.

Well many plugins work and others don't so I would draw some obvious conclusions from this. On the other hand bitbridge might not work well with certain plugins (either blame the chicken or the egg). It would also be very easy to taint all scenarios under the same brush.

Also note it's unlikely cakewalk gets full access to the third party code (it's not their job to debug other people's code either).

If the OP has a dense project (lots of tracks/EFX):
I'd first make a copy of that project... for test purposes.
 
Now, load that copied project in Safe Mode (to strip out all plugins).
Try running this project (sans EFX/processing) for a good while.
Loop it, start/stop transport many times...
If this project runs completely stable for extended periods (over multiple sessions), you now the issue is plugins.
If the machine still crashes, it's time to test the system's RAM.
A bad stick of RAM can cause major stability issues...