This is the very reason I went to Reaper a couple of years ago.  Just when I start trusting Sonar and trying to do serious work with it - Poof!  Closing now, bye-bye to your last takes and comping!
 
Guys - this is frustrating.  I gave fault reporter permission to run.  Does it go to the bakers automatically, or do I need to send something?
 
 

when the problem reporter comes up, it issues a trouble ticket and gives you the number of that trouble ticket.  you should be able to contact tech support regarding that ticket number and get information on where it is in the system.
 
trouble tickets do not automatically go to the ones who create/write/change the code.  it goes to tech support to verify or get further info and does not get elevated to the actual bakers unless it is a verifiable problem.
 
often, I have found, that when this kind of thing happens it's usually an interaction between sonar and a plugin, or strictly caused by the plugin itself.  what kind of things were you doing when this happened and what plugins were you using?

Thanks
 
I didn't get it a number ... just the opportunity to exit Sonar without saving ...

Almost invariably, whatever you recorded is in your project audio folder. The file will usually incorporate the track name depending on when the freeze occurred, but you can always click through the project audio file in the media browser to find it.
 
Don't know if this applies in your case, but running 32-bit plug-ins in a 64-bit environment is risky. This is why DAWs like Studio One, Pro Tools, Cubase, etc. don't even let you run 32-bit plug-ins (most don't support DirectX, either). While I appreciate that SONAR makes an effort to provide backwards compatibility, using older plug-in formats and bridging technology to fool SONAR into thinking the plugs are compatible can definitely impact stability.
 

The only plugin in the project was a bypassed copy of the tempo delay that came with X3.
 
I was working with the comp tool when it poofed.  I'll bet the $80 I wasted upgrading to X3 that the crash has to do with the comp tool.
 
So, did the fault reporter report anything, or no?  How do I tell?

if if did not ask you if you wanted to report the fault to cakewalk then the fault reporter did not report anything. the fault reporter will pop up a window and ask if you want to report the problem to cakewalk. if you say yes, then a report number is generated and sent to cake support and the number will be shown on your screen and you will get an email with the problem reporter incident number as well.

sound card drivers are also a typical fault of sonar going "poof"

what soundcard are you using and which driver mode?

The reporter did ask and I told it yes.
 
Delta66 ASIO
 
Don't waste a lot of time.  My hardware is rock solid with Reaper.  I'll pick back up with that until I see some maint releases for Sonar.  I'll just make sure not to trust it to quickly next time.

ok, sorry it's happening to you, but I'm sure me and others would be glad to help you track it down if it continues to happen.

rfreeze
The only plugin in the project was a bypassed copy of the tempo delay that came with X3.
 
I was working with the comp tool when it poofed.  I'll bet the $80 I wasted upgrading to X3 that the crash has to do with the comp tool.

Was it the Cakewalk Tempo Delay or the Blue Tubes one? The Cakewalk one is an old DirectX plug-in. In fact it will throw a DirectShow error under some circumstance I don't recall right now, something like bouncing to clip in a mono track because it's a stereo effect. 
 
I'm not trying to minimize your frustration at having something go wrong. I understand what it's like to lose work. However, as mentioned I think the work probably isn't lost, and if you used the Cakewalk Tempo Delay, it's a DirectX plug-ins - which has been a "zombie format" ever since Microsoft lost interest several years ago, and only remains supported in a few hosts primarily for backwards compatibility. You'd be better off with the Blue Tubes if that's not the one you used.
 
You are not the first person to have this kind of problem nor will you be the last, but many times relatively simple solutions are found through the experience of people on this forum.