Seems like about 8 times out of 10 when I close Sonar I get the message "SONARPDR.EXE has stopped working".  Anyone else get this?  I haven't been crashing at all.... or much, anyway.  And it really doesn't seem to affect much except that when I relaunch Sonar it doesn't remember my recent projects....

Please check your  windows event viewer .
 
Please find the Sonar crash (usual a red exclamation mark item under Administrative Events). Right click the red icon, Copy -> Copy Details as text and paste here. Make sure you get the Sonar crash (should be pretty obvious when you see it).

Wow well there's a lot of crashes in there......
 
Does this actual mean something to you?  There are a bunch others but this is the last one that just happened I know for certain happened on closing Sonar. 
 
Yes my computer's name is "Booger".
 
Log Name:      Application
Source:        Application Error
Date:          2/11/2014 5:06:29 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Booger
Description:
Faulting application name: SONARPDR.exe, version: 20.0.4.278, time stamp: 0x52abb061
Faulting module name: SONARPDR.exe, version: 20.0.4.278, time stamp: 0x52abb061
Exception code: 0xc0000005
Fault offset: 0x00000000000c5ee0
Faulting process id: 0x2850
Faulting application start time: 0x01cf274407960946
Faulting application path: C:\Program Files\Cakewalk\SONAR X3 Producer\SONARPDR.exe
Faulting module path: C:\Program Files\Cakewalk\SONAR X3 Producer\SONARPDR.exe
Report Id: e6c0eedb-9381-11e3-8489-002590e54cf1
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-12T01:06:29.000000000Z" />
    <EventRecordID>3476</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Booger</Computer>
    <Security />
  </System>
  <EventData>
    <Data>SONARPDR.exe</Data>
    <Data>20.0.4.278</Data>
    <Data>52abb061</Data>
    <Data>SONARPDR.exe</Data>
    <Data>20.0.4.278</Data>
    <Data>52abb061</Data>
    <Data>c0000005</Data>
    <Data>00000000000c5ee0</Data>
    <Data>2850</Data>
    <Data>01cf274407960946</Data>
    <Data>C:\Program Files\Cakewalk\SONAR X3 Producer\SONARPDR.exe</Data>
    <Data>C:\Program Files\Cakewalk\SONAR X3 Producer\SONARPDR.exe</Data>
    <Data>e6c0eedb-9381-11e3-8489-002590e54cf1</Data>
  </EventData>
</Event>
 

No smoking gun unfortunately, are all the error messages identical in the description?
Otherwise next step is to run windows update, update to the latest drivers for your sound interface, firmware and plugins etc.
 
Thanks..

Hi Booger, I mean Matt,
 
Looks like access violation - Your probably best to install windows debugging tools on your PC and in the windbg session attach to dmp file and run the command "k" to dump the stack that caused the exception - it will have a bit more info there as to what is happening...  Warning Installing, setting up and using windbg is a little advanced. It downloadable from http://msdn.microsoft.com/en-au/windows/hardware/hh852365.aspx scroll midway down and you'll see the download link.  Once installed you need to setup the symbol path, It is as simple to use the Symbol Server as it is to use the appropriate syntax in your symbol path. Typically, the syntax takes the following format:
 
_NT_SYMBOL_PATH=SRV*C:\temp\Symbols*http://msdl.microsoft.com/download/symbols
 
 - when you set that up you simply open crash dump file from the file menu and run "k" command or "analyse -v" or both...
 
There is adplus that can be used too, you attach it to your sonar process and it captures exceptions like this and run all the neat little debugging commands to produce a pretty comprehensive report (I use to love Dr Watson - it was awesome and now its gone!)...
 
Jim

No please don't install debugging tools and symbols on your PC! :)
 
Sorry Jimmy, I know you are a hack but windows debugging is not a good idea right now, please be aware that windows debugging tools may slow down your PC and make the situation worse. It is not advisable to install developer tools in a DAW environment.
 
If it gets to that stage it's probably best to ring up Cake support, they are far better qualified to handle crash dumps and have the source code to compare it with, and not everybody is a developer.
 
At this moment there are other plenty of other options to explore.
 
Cheers..
 
p.s.
 
> Looks like access violation -
 
There's nothing in the error to indicate this. All this error indicates is that Sonar has crashed.

I am wondering if this might be those run-time redistributable routines from Microsoft being out of date.
 
I concur in running Windows Update until all maintenance is up to date, and then seeing what happens with this error condition.
 
I also concur in being cautious in using the debugging tools, unless one is familiar with them.
 
Bob Bone

> I also concur in being cautious in using the debugging tools, unless one is familiar with them.
 
Without the Sonar source code or symbol files this is unlikely to get anywhere to be honest. The symbols files Jimmy is referring to is for the Windows operating system, however we are not debugging windows here.

I kind of agree to disagree...
 
Windows debugging tools is a tool.  Its only used when your using it, it doesn't load into memory or load any special drivers - bit like the latency reporting tool, or loading up internet explorer - when you run it you don't load it with your DAW running...  So the idea is you load the dmp file into windbg and analyse it, it provides a report and you know what to focus on.  Albeit, having the source code is the ultimate, though at least you can see on what driver is failing then you can check version details from that on the driver and see quickly if you are up to date or not. 
 
Regardless though, Matt you should make sure to have your system up to date.  Usually this would help a great deal.

Sorry Jimmy I'm a .Net developer, I actually run a full developer environment with Visual Studio away from my DAW, and you are wrong here... Check you windows services for instance.
 
The dump is best analysed by Cake (BTW Cake dump files get sent to Cake anyway) who has the source code. If we were getting into Windows BSOD's and kernal mode drivers that would be something else but as you know there are other (less bulky) utilities to use here for end consumers in these scenarios. Here we just have an application crash (and we don't even have the symbols).
 
There is nothing whatsoever to indicate this is a driver issue, and if it was I would expect a BSOD. 
 
Cheers...
 
UPDATE
 
To be clear I meant a windows driver issue. It is still possible there could be an issue with the sound interface. However right now it could be anything.