Sonar X3 not closing properly

Hi, folks.  
Been using CW since forever, but for the past few weeks, Sonar X3 does not close down properly.  When I close it, it closes then says that SonarPRD.exe is not responding.  The it offers the usal options to 1) Check for a solution and close the program, 2) Close the program, or 3) Wait for the Program to respond.  Then it generates this information:
Description:
A problem caused this program to stop interacting with Windows.
Problem signature:
Problem Event Name: AppHangB1
Application Name: SONARPDR.exe
Application Version: 20.0.5.352
Application Timestamp: 5320c501
Hang Signature: d8bf
Hang Type: 0
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Hang Signature 1: d8bff7159c77c0884acc72f3682aa0f8
Additional Hang Signature 2: f71c
Additional Hang Signature 3: f71c961e84fd34a4191a88587c91762c
Additional Hang Signature 4: d8bf
Additional Hang Signature 5: d8bff7159c77c0884acc72f3682aa0f8
Additional Hang Signature 6: f71c
Additional Hang Signature 7: f71c961e84fd34a4191a88587c91762c
 
It also does not save the last project in the drop down menu list of recent projects.  Any ideas?  Otherwise, it seems to work OK.  I just have to make sure that I save the file and then be able to locate it to open it back up.

Sonar has at times been stopped from properly closing by a connected MIDI device that doesn't let go when Sonar closes. Easiest way is to check the Task Manager to see if Sonar is still running and look for some device esp a midi device which as I said can often be a culprit.

OS?
My old win 7 system had this and was fixed when I went to Win 8 (and 8.1).
 
Mine was on a Delta 1010 card on Win 7 Ultimate 64 bit....having said that I was so annoyed by the lack of driver updates for the Delta 1010 I bought a MOTU Audio express and Win 8 at the same time, this resolved for me.
 
Now my Delta 1010 is my windows sound and my Motu a dedicated Sonar/Pro Tools card.

If there are any loaded 32-bit plugins, sometimes BitBridge can hang things up.
 
You would see it in Task Manager.  Some folks do seem to get it sorted out by cycling the audio interface, as noted above.
 
Also, with regard to Win 7 and/or Win 8 and 8.1 - the biggest thing to make sure of is that our audio interface drivers will work properly in the OS version you load, (whether that is 7, 8, or 8.1).
 
I ran on Windows 8 for quite a while, then just last night finally got around to upgrading to 8.1.1 - whatever the latest version is.  I did that only after making sure my interface drivers would work OK, and they work just fine.
 
So, just do your homework on that.
 
Windows 8 actually works very well, but lots of folks completely lose it, with regard to the tiles and the start button and all that, but it is no biggie, and you will get the hang of it in no time, plus you can get a lot of the familiar look and feel back quite simply.
 
Bob Bone
 

Funny this topic, as I very very rarely have these sort of issues, But I just had this exact same thing happen to me early this morning. And oddly enough the same thing with the last project was not in the drop down menu??? I found that very odd. When I opened it by browsing it was fine. The thing is I had saved it a half dozen times as I worked on it, then I exported a mix and tried to close Sonar. Sometimes at this point some projects ask you to save even though you did before export. Is this related? 
 
But the comment about the midi device is what I think happened as my stupid Yamaha drums fell asleep and disconnected. Sonar told me. So that might have been it.. The other problem was my mouse battery died and it was behaving crazy as it breathed it's last breath, so I thought?? oh well. But that is odd we both got the identical weirdness.
 

This used to happen to me all the time. The way I solved it was to shut down Sonar X3 in this order. Instead of just pressing the "X" in the upper-right corner, go to File->Close first. Then wait a few seconds (you'll see the borders of X3 change color slightly indicating it's not doing any work) and then exit out of X3 entirely, either by going to Menu->Exit or just pressing the "X" icon. 

If you are already doing this and still getting this error, then I don't have any advice :P

Oh I didn't catch that, we do both have Focusrite and Mix Control. And as another point, I don't often open mix control. You don't need to unless you are adjusting monitor mixes or the input line/instrument toggles. And this was a time where I had it open and over on my second monitor. Could just be you need to close mix control and all would be good.
I don't see the point of re installing the drivers if they are the correct ones. I just checked and mine are up to date still. All that might do is force a re set to the factory default which you can do from the menu. Try that instead.  

johnnyV
I don't see the point of re installing the drivers if they are the correct ones. I just checked and mine are up to date still. All that might do is force a re set to the factory default which you can do from the menu. Try that instead.  

Sorry but you are mistaken, otherwise I would not have recommended it and I would not have stated "whether on latest or not".

I've had issues at least twice where cleanly reinstalling + reset fixed the issue. The problem is that upgrading from earlier mix control versions sometimes corrupts settings, not only at the hardware end but at the software end as well, and a clean install+full reset sorts it out. I've also recommended it to others in the past and this has fixed their issue, I've also have been in contact with Focusrite about it a while back. So what I state is tried and tested (and seems to be known about from Focusrite).

I strongly recommend carrying out the procedure I stated in the previous post in full to see if it helps. Full reset inc hardware.

Nowadays when I upgrade mix control I always perform a clean reinstall+reset as I don't trust the product to upgrade itself correctly.

Thankyou..

But this makes absolutely no sense to my pea sized brain, I do believe your right in the case of software that seems to be not working, But my version of mix control seems to work perfectly fine and for about 8 months now every day I use it without issues. And it is the only version I have ever used since day one. 
 
I just completely re did my system and when I did I had the latest version of mix control so that's what gets installed. It is  1.8   which I just checked and it is still the most up to date version. 
 
So why  would  re installing something that is working perfectly fine change anything? Software should not be that flaky. Sure if it was not working right because of a possible glitch in the download. But even that seems far fetched as most corrupted download will throw errors when installing, There's code to check these things built into the installer, right?  
 
I will agree that sometimes a complete fresh install of everything is sometimes faster than endless troubleshooting and registry hacks.. that's for sure. But in my case I just installed it a few weeks ago. It could help the OP however. 
 
I have no clue why the same thing happened to both of us, and nobody else here does either, It's either a coincidence that we both have Focusrite interfaces and some combination of whacking on buttons and stuff before closing Sonar caused a random glitch. I cannot re create it, I tried. So it's was just one of those daily weirdness you will always experience when working with these new fangled computer systems.. I'm hoping my new build will lessen the daily weirdness by a factor of 9.