Leee
I don't think I can ever recall having a repeatable crashing issue with Sonar.   I read all these posts from people who have problems with Sonar crashing, and I feel a bit bad for them, but also felt fortunate to have a stable working DAW.
Well, that changed with the latest update 2016.12.   It seems whenever I try to export my project into a wav or mp3 file, Sonar will automatically give me the Windows "this program had an unexpected..."  along with the crash report window from Cakewalk.

I tried this on new projects that were written in the latest version, as well as older projects from earlier versions.  They all crash when trying to export them.   I reverted back to 2016.11 and everything is working fine again.

I submitted a bug report.  Just wondering if anyone else has this particular issue?

Very Similar... Today 2016.12 repeatedly crashed on bouncing the entire mix to a track or for that matter, as a test, odd sections of the project I've been tweaking, which is weird since it seemed o.k. up to the 12/22. Failed to catch an unexpected exception, so sounds like basically the same issue to do with rendering the audio... So submitted a bug report and I too reverted back to 2016.11 & bounced o.k. But... Despite having a 4GHz core & 32 GB of ram I found it's best not to do a fast bounce, which I always used to do way back, as it seemed control data doesn't always register properly in the rendered track... Any issues there?? Oh yeah, I always run in admin mode due to prior issues where elevated access was needed, for various reasons, so that's not a work around for this crash... And I agree running this way is not the best practice.

My problem has come back again.  After switching to start Sonar as Administrator, it worked okay for a few days.
And now, without changing anything, Sonar crashes again whenever I try to bouncing a project to a final audio file.
So once again, I had to revert back to 2016.11.

So, I removed the "SOLVED" from the title, it seems we are back to square one.
I am no longer able to use version 2016.12, in normal or admin mode.  It now crashes again every time I try to render a project to a wav or mp3 file (or any file type for that matter).

Yup it's an issue!! Just uploaded and attached 5 more mini dumps to my problem report, that I previously skipped sending, when this started cropping up early this morning... So I sincerely hope our friends in the bakery give the report, hitherto not reviewed, a gander shortly, the more shortly the better as I fear that 2016.12 might have revealed something serious as opposed to introducing it... My feeling is that it's related to the recent W10 12/13 update, at least in my case, and possibly the thread timing issues I spotted in some posts on rogue VSTs.

I had to roll back because of constant crashing while recording a background vocal.

hi,
 
while this may not be the case for you, i had situation sonar crashing during export a month ago.
and it appeared it was because of Aux tracks.
 
i have no idea at what moment they caused the problem, but after i removed them
everything began to work just fine.
 
its quite easy to check - if Aux track doesn't play for some reason - try to delete it and either use bus or new aux track.

Playing is not a problem bouncing is. All my crashes are due to an Access violation - code c0000005, and from what I can tell, and I could be wrong, it's not due to a plugin! It's sporadic but when it occurs it continues to happen even after a machine reboot, which suggest that an incompatible system state exists for the crash time periods, resulting in the violation. Without going to 'dump analysis school' I've no idea which module or component is throwing the exception! So until the support team analyzes the minidumps which they haven't as yet, the cause is undetermined and due to it's sporadic nature there is no work around. My concern is that if it's not identified, in my case under W10 post the recent update, that I could be stuck with 2016.11 and not be able to take advantage the next set of splats rolling updates. So it would be much appreciated if the issue is addressed sooner rather than later and hopefully a resolution is found.
 
Thanking the bakers in advance...

Leee
Yeah, I know, I've been searching and haven't been able to find anyone else having this problem.
I have found a quick and easy work-around though, I just start Sonar in Administrator Mode and it works fine without crashing.  So, that's what I'll do from now on.  I'm guessing it might have something to do with Windows 10, I've noticed a lot of crash issues with Sonar and the latest update of Windows.

I have had this issue as well. Only with one particular track. I also operate Sonar in Admin. For me, it only happened as I tried to render this particular track in real time mode. When I did the speed render it worked fine. Go figure... 

I also tried the suggestion of putting Sonar in Compatibility Mode (Windows 8) as well as running it in Admin mode.
It worked a few times, but whenever exporting/ bouncing down the project to a song file, the cursor would be very jumpy and staggered when moving across the timeline. (normally it's very smooth)
And yesterday, when it got to the end of the song, I got the same type of crash. (Access Violation)

So once again I reverted back to Sonar 2016.11 and all is well again.
I hope the bakers come up with a fix soon!

Leee
So once again I reverted back to Sonar 2016.11 and all is well again.
I hope the bakers come up with a fix soon!

Me too! Leee, did they review your crash report yet??

TEZ

Leee
So once again I reverted back to Sonar 2016.11 and all is well again.
I hope the bakers come up with a fix soon!

Me too! Leee, did they review your crash report yet??

No not yet, and I really wasn't expecting any response.  I'm just hoping they fix the problem, which I'm pretty sure is related to the new Windows 10 update (in combination with Sonar's 2016.12 update).