SONAR X3d seems to be working fine but crashes on close

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....

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>
 

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

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 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.

I think the maintenance getting up to date would be the logical place to start, as if it is those run-time redistributable Microsoft routines, that would be a quick fix, and in any case should be done.
 
Bob Bone
 

Exactly, and #4.
And we are still looking for errors in the event viewer.
We would need to get dependency viewer utilty out later to see if it is a library issue assuming the issue persists.
Cheers.

Jimmy another day, Windows debugging threads are a whole other thing, and besides it's time for bed.... I'm not saying you aren't trying to be helpful but installing developers debugging utilities on consumer PC's is whole different ballgame. That would be a last resort type thing and really it's best left to developers. We don't have the symbols or debug edition of Sonar and there's probably a better a way of fixing this issue. It's a bit of a sledgehammer to crack a nut. Cheers..

The age of the machine may not be an indication of the age of the software installed on it. If the builders are available and support their machines, maybe give them a call and ask them about the errors and warnings you are seeing in the event viewer. Might also be worth a call to Cakewalk tech support. When I got a new machine (now a year old ) I routinely checked the event viewer early on so I could establish a baseline for what to expect. It rarely has errors or warnings and I can account for all of them without any special diagnostic tools.

Hope it works out! I recently had to do a total OS re-install, too.

Yup - I am following both threads.  I am looking for a response in that thread to some questions I posed.
 
Bob Bone
 

BTW if you are that far behind in windows update you may need to run it several times, and don't forget about the optional updates as well.... Thanks.

Closing projects before exitting is also safer to ensure saves take until your issue is better defined.

CakeAlexS
BTW if you are that far behind in windows update you may need to run it several times, and don't forget about the optional updates as well.... Thanks.

+1 to this recommendation. Many windows updates need to be done sequentially, so it can only install "so far" before a reboot is required and the next "set" can be done (run Windows Update as many times as needed till no more "important" updates are listed).
 
Edit: I just checked my Win7 and I have 253 updates... so you may still be a bit shy on numbers

Please list your computer specs, so we can help figure out what is going on with your system, 
 
Bob Bone