Lost a bit of work after Audio Engine crash

This happened today, and was full-recoverable. I figured I'd see if there's anything I can do to prevent it, or if it's a known issue. I was playing back a project, decided to change an aux send. As soon as I chose it, I got the Audio Engine dropout dialog. I wasn't able to click "close" or do anything with Sonar. I couldn't close the window or exit the program in any way. Strangely enough, it didn't say "Not Responding" as it usually does when it crashes (in the program title space at the top). So I CTRL+ALT+DEL, and closed it. When started back up, I lost probably 10 min of work. It was like my project had went back in time. I'm the type of guy to CTRL+S after every other small change, so I know I saved it after doing many of the things I had to redo. Finally, unable to send a problem report because it didn't officially "crash". Anywho, is this common at all?

I have a 64bit Windows 7 OS, but I use X1 32-bit because I found that it behaved better on my machine with my plugins. I always look to see if X1 has a 'hidden' or 'secondary' dialog by looking at the pinned tab on the taskbar. Often when there is another dialog open, a tiny sliver will show next to the main Sonar tab. I'm sure everyone has seen it. You see it when you open Help. This time that didn't show. Also, I right-clicked the tab and selected "Close this window" and that did nothing but cause the tab to blink orange. Good ol' ctrl+alt+del was my only option. I was able to use other things, but Sonar literally froze.

As I said in my initial post, I instinctively hit ctrl+s (save) every other minor tweak. I change an envelope, I save. I do that in my day job on a mac (command+s), in Sonar, in any software that has that shortcut I do it. So it's not like my work wasn't saved and I was being lazy. In short, I save a LOT. I probably would get punched in the chin if my computer had arms because it has to repetitively save. There are so many new variables for me to really pin down anything. I have a newer PC, new OS, new Sonar version, and new type of hard-drive. Speaking of which, perhaps it's because of my new SSD hard-drive? Do contents get written directly to it's disk... or is there some sort of cache/buffering happening where the saved information does not get permanently written to disc until I close Sonar or enough data has been piled up to store? I ask because I've had crashes with Melodyne that do this exact "time-warp" work-loss. So if I'm heavily working with Melodyne, I will close my session and re-open to make sure it's saved. This is the type of thing that makes me nervous because what happens if a client records a great section or song, and then Sonar dies and they lose their data?