As a longtime Sonar user, I've gotten used to the occasional random crash so I habitually save my work...no big deal.
 
However, one element about the crashes does really irk me, SONAR seems to hang on to my audio drivers after a crash for 5-10 minutes. It sits in the taskbar and I am unable to end the process or really do anything sound related until it finally decides to release them. It seems now after owning a few different interfaces that the problem lies with USB audio interfaces. I used to have an EMU1212m PCI card &  a VS-100 and would only experience the problem when using the ASIO Vs-100 driver. That was especially frustrating as often even a reboot would not fix the problem entirely.
 
However, with windows 10, I had to sell my EMU 1212m and so I picked up a Focusrite 2i2...and now after my first crash using it, it's doing the same thing! I've tried unplugging the devices after a crash. I've also tried a bunch of different USB ports. I actually have a dedicated PCI usb card so there aren't any potential IRQ conflicts. I'm just not sure what to do, but it's especially frustrating if I'm in the middle of a recording session and I have to tell everyone to take 5 when it crashes. I've seen a few posts here and there about other users having this problem but I never came across a concrete solution...have the bakers ever addressed this or is there something else I can try?

I think you'd be better off trying to determine what's causing your crashes in the first place.
 
What's your full system spec and what plugins do you regularly use?
 
What sort of operations are you performing immediately prior to a crash?

AMD X4 640 3.0GHZ
12GB Ram
Windows 10
Focusrite Scarlett 2i2
Axiom 61 Keyboard
Mackie MCU Control
 
The project has a whopping 7 tracks. 4 audio, Addictive Drums2, Kontakt 5, & Dimension Pro.
 
Its crashed twice now, both after pressing stop when recording a softsynth, once in Kontakt  & once in Dim Pro.

I have the same issue and have over several previous versions
I also have at least one or more crashes per day with windows 10 and a few less with Windows 7
This can be caused by something as simple as editing a voice over with a track of music
To woring with 50 tracks ...very annoying

I can deal with crashes if I can recover quickly and just restart the program, but Sonar won't let go without a complete reboot
I hAve tried logging off as opposed to rebooting , which works for a few minutes but more times than not ends up locking up the computer totally
Then I have to plug and unplug my Zoom R24 to be recognized and back to work
Many times it's a 10 minute ordeal
I've been using Sonar for about 15 years and have t h ought about switching DAWS but hate to start over
With all the attention being placed on streamlining work flow it seems like this should be a priority
10 minutes is a lot when you are in the middle of a project
I've contacted support about this but never heard back
I just kept hoping it _would be better in the next version
Thanks for listening!

Lenovo i7
16 gig ram
SONAR PLATIUM PRODUCER
Kontakt Ultimate latest version
All Sonar plugs
M Audio C 400 for midi in out only

I have had similar problems in a very specific instance. If I use melodyne it informs me to up my buffers to 1024. EVERY time I try to do this I get hung up to the point that I must quit the app in task manager and restart windows.That is the ONLY way I have ever been able to continue. (I am using Komplete Audio6). I have gone to the point of writing my work around routine and slapping it next to my monitor. WARNING: when using melodyne, create region FX, save and close, adjust buffers, restart...blah blah. Ultimately, this "3 left turns to make a right" approach saves me more time than swearing at my computer, cursing the digital audio and computer gods, etc. Is it right? NO! Is it fixable? probably. If I try to open a support ticket, will I get it resolved, or will Sonar support say, "consult the manufacturer" and NI support will respond " consult your daw support"?If I had a nickel for everytime I've done that back and forth dance I would have ,well, alot of nickels. Hence, the note on my monitor.Sorry if this rant doesn't help, I just feel your pain.

I used to have both issues of drivers not being released after a crash and Melodyne's constant messages with the buffer. I don't know whether the buffer thing was related to the audio interface I was then using - Roland Quad Core - but the driver release issue was. I used to have to power down the unit and wait - sometimes for several minutes - until it was released...really annoying and contacting Roland - whilst providing support - didn't solve the issue and they weren't about to create new drivers to assist in fixing it. The current driver for the unit is close to 2 years old now. 
This all changed when I purchased a RME UTX audio interface. I no longer get the buffer thing with Melodyne and in the event of a crash - rare - drivers are released immediately. So it would appear that Sonar works better re these issues with different sound cards? It would seem though that a specific fix for the interface used with Sonar is required and that I guess means both manufactures talking to each other to assist end users solve the issue.

I have a question, Fabio. Is your interface USB?

So it seems I'm not alone...I'm curious though, the Focusrite Sapphires are commonplace in home studios...has anyone out there experienced a crash and NOT had to wait 5-10 minutes to restart SONAR? 

If Sonar crashes on me I open Propellerhead's Reason and then close it. Sonar will have released the driver and will boot up again. I'm pretty sure it doesn't have to be Reason so some other DAW will probably have the same effect.
In the old days I'd rip the USB cable out of my interface but now I have a firewire one it warns of death and dismemberment if the cable is ripped out so I don't do that!

People who never have these problems are very lucky. Every version of Sonar, every interface and every PC I've used have had crashes and locked drivers.

Grum.

orangesporanges
I have had similar problems in a very specific instance. If I use melodyne it informs me to up my buffers to 1024. EVERY time I try to do this I get hung up to the point that I must quit the app in task manager and restart windows.That is the ONLY way I have ever been able to continue. (I am using Komplete Audio6). I have gone to the point of writing my work around routine and slapping it next to my monitor. WARNING: when using melodyne, create region FX, save and close, adjust buffers, restart...blah blah. Ultimately, this "3 left turns to make a right" approach saves me more time than swearing at my computer, cursing the digital audio and computer gods, etc. Is it right? NO! Is it fixable? probably. If I try to open a support ticket, will I get it resolved, or will Sonar support say, "consult the manufacturer" and NI support will respond " consult your daw support"?If I had a nickel for everytime I've done that back and forth dance I would have ,well, alot of nickels. Hence, the note on my monitor.Sorry if this rant doesn't help, I just feel your pain.

Ignore the buffer message and just use Melodyne at the settings you started with.

Grum.