Good posts everyone. 
 
I would also add housekeeping issues such as making sure your disks are defragged and not bumping into the ceilings.  The ceiling issue is not as bad as it once was, due to the size of HDD's, but it needs to be looked after.  I started with an IBM AT with a HUGE disk (at that time) of 20 Megabytes.  Hey that was twice the size of the original IBM which had 10 Megabytes.  Having the disks defragged, however, can save a lot of headaches.

Disk fragmentation is far less of a problem now than it was during XP days, unless the disks are approaching capacity.

Updated graphics driver, disabled low latency mode and was able to save without a crash. But when I went to X out of the program after the save.....it crashed.
 

is it the same in both asio and wdm driver modes?

The crash log from that would be useful,  (not so much for us, but for tech support), but that sounds like a plugin not closing correctly/at all when Sonar is trying to close.
 
When you say "crash" do you mean it is white screening with 'not responding' or blue screening the whole computer?

Yep both modes. No blue screen, just white screen of death in the sonar window then a pop up window "SONARPDER.EXE has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
 

dbmm
Yep both modes. No blue screen, just white screen of death in the sonar window then a pop up window "SONARPDER.EXE has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

That generally means the program is waiting for something to happen which is preventing it from closing. Either a file/record lock problem is preventing it from closing files, or audio driver instances are not closing because something is keeping them open when Sonar is trying to close them.
 
I've seen it here several times  (sonar.exe doesn't close) but I can't find the solution with a quick search.   It is here somewhere....

does the crash only happen in conjunction with saving? or anytime you exit?

Since you say you have repeated crashes, I wanted to point out that after that white screen crash, I have to reboot the whole PC, not just Sonar, to get things working.
 
Also, someone remind me: can't you shift-click the Sonar icon to start it in a mode where it asks you about every plug-in/soft-synth?  Usually, you can start it without one or more plug-ins to isolate which one is the problem.
 
Extremely time-consuming if you have a lot of plug-ins, I know, but it is one way to find the one that is messing things up for you.  It looks like you don't have too many soft synths, so that helps.  I, unfortunately, have gone nuts on soft synths.

All good suggestions, it will take some time to diagnose which is causing the hang up. 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.