Hey Guys:
I'm suddenly getting a huge number of crashes (three or four an hour at times).  Nothing in particular seems to cause it.  It happens when I open a project, if I try to add a track, change the setting on a VSTi, or any number of other things.  Usually I'm asked if I want to file a fault report, but then Fault Reporter won't work.  Generally I get the following message:
Exception Code C0000005
Address 00000000005B9A35 followed by a slew of zeros (too many to count) then 65:000065
 
Any thoughts?
Thanks!

Have a look in C:\Users\USER\AppData\Local\CrashDumps
 
The Bakers might be able to use a dump from there if present.  AppData is hidden by default, so you may need to choose the option to show hidden items
 
 

Thanks!!  Will do.

This has happened to me all day.  It seems to be related to play 5 (for me anyways).

eph221
This has happened to me all day.  It seems to be related to play 5 (for me anyways).

Eph, that interesting, because in one particular project that is hugely crash prone I'm using Play 5.

I've also had issues with Sonar crashing on me over the last couple of days -- and this is after many months of solid performance. It happened three times in an hour, this evening, and it is very frustrating. Of those three times, two of them involved Play 5 (the first crash happened when I had only Sonivox's Big Bang loaded up, the last two crashes involved Big Bang and Play 5 loaded up). All the crashed sessions also had the new Exponential Audio Nimbus reverb demo loaded up, as well. I've been playing around with it, this evening...
 
In my case, Sonar just freezes up, and simply stays unresponsive. I have to force close the program, and afterwards there is no error message or dump file -- at least, as far as I can tell. Sonar basically just decides to hang.
 
I've gone back to using Reaper, this evening, in order to get some stuff done. 
 
 
 
 

Have a look in the Windows event log. Go to Windows Logs -> Application. In the Actions pane, click "Filter current log" and check "Error" under Event level. Press CTL-F for the Find dialog and type "SONAR". In the details, look for "failing module name". That'll (usually) identify the culprit if it's a plugin.

Thanks!!  Will do. 

In my case, two of the three crashes are classified as system hangs, and so a faulty module is not listed. The third crash incident was a full application error for SONARPLT.exe, and the faulty module was: ntdll.dll
 
...which I believe is a Windows system file. Judging from a brief Google search, ntdll.dll is implicated in a lot of crashes, but they could be caused by just about anything.