Sonar crashes at lot for me.  At least once per day.  That would not be bad if I could restart it.  However, as long as SONARDPR is running in Task Manager, Sonar will not start normally.
 
If I could end that process in Task Manager, I could restart Sonar.  When I select it and choose End Process, nothing happens (in most cases).
 
Is there a way to end this so I can restart Sonar without a total PC reboot?  The reboot is what takes 75% of the time.

This is usually a sign of the audio driver failing to respond, I think. Does switching off your audio device let you end the SONARPDR.EXE process?

A few months ago I had some odd crashes in SPLAT, and I noticed that there was a sonar app process that I closed but didn't totally close the all the processes for it... I scrolled down in background processes and there was a sonar-related process still going on, i forgot the name of it.  Closing that process freed up that existing thread and I could restart sonar without rebooting.

Konradh you are having no luck these days! I had that issue and it was my USB device driver not get released. I would kill the process in task manager and then power cycle your audio capture device and Sonar should launch again.
 

Rather than a total cold boot your best option is to "Log off / Log on using Windows.
This takes a few seconds Vs. a reboot which(if you have an HDD) can take a few minutes.
 
I used to have this problem a lot until I switched Audio interfaces and updated to the newest drivers.
Since I did this, I haven't seen this problem at all, then again I don't experiences crashes (like once in the past year) and I use Sonar 6-8 hours a day Monday thru Friday.
 

Maarkr
I scrolled down in background processes and there was a sonar-related process still going on, i forgot the name of it.

You may be thinking of the BitBridge server. It is launched automatically when 32bit plug-ins are added to a 64bit instance of SONAR. AFAIK, it is the only other process created by SONAR other than the SONAR exe. It has been know to hang on occasion. Most likely related to the 32bit plug-in(s) hosted by BitBridge rather than the BitBridge server itself.
 
Waiting on a reply from the audio driver and BitBridge server are two things that may prevent SONAR from shutting down properly.

Here is what I have done.  I have made a VBS script that stops and starts Sonar Platinum.  Note: Only do this if Splat will not shut down normally.  The script contains the forwarding VBS command.  Note: this is on Windows 10 64bit but should work on Windows 7 as well.  Note, if you run this while Sonar Platinum is visibly open (IE you can see the GUI) , it will still close and restart.

Dim oShell : Set oShell = CreateObject("WScript.Shell")
oShell.Run "taskkill /im SONARPLT.exe /F", , True

oShell.exec "C:\Program Files\Cakewalk\SONAR Platinum\SONARPLT.exe"

How do you utilize the script? Do you put it in note pad and then change the extension?

Konrad,
are you using ASIO or WDM?   I've had a few problems recently and I also wondered whether or not it was related to my audio interface driver...

konradh
Sonar crashes at lot for me.  At least once per day.  That would not be bad if I could restart it.  However, as long as SONARDPR is running in Task Manager, Sonar will not start normally.
 
If I could end that process in Task Manager, I could restart Sonar.  When I select it and choose End Process, nothing happens (in most cases).
 
Is there a way to end this so I can restart Sonar without a total PC reboot?  The reboot is what takes 75% of the time.

That's the Roland audio driver not behaving - bad news is that there is probably no fix this.
 
I had this issue a lot when using the VS-700R. Sonar would get stuck and over the years I have never been successful in killing the process so that the audio driver would come back - meaning in those case where I managed to kill the stuck Sonar process, Sonar would start again but missing all my ASIO input/output channel, thus still requiring a reboot.
 
I'm meanwhile using other interfaces with better drivers and kill Sonar as I like (although I rarely have to, unless I do something stupid) and the audio driver is not affected.