It's the only truly irritating thing in the new build, IMO. I don't really care if it's plugins or whatever - please find a way to force Sonar to close all projects, every time. I can't be expected to Task Manager - "End Process"  in front of clients - it makes them nervous, and it's bad bad PR for Cakewalk.
 
Thanks!
L.

Sometimes "end process" doesn't even work, and I have to shut down the computer. I don't know if the problem lies in Windows 7 or Sonar, but it's definitely irritating when it happens.

This is not normal behavior. I can't recall this ever happening to me. In the past when people had this issue it was often due to a hanging driver that wouldn't close or give Sonar the proper handshake to release it. M- Audio was known to have this problem.
 
A driver update may be in order.  

John
This is not normal behavior. I can't recall this ever happening to me. In the past when people had this issue it was often due to a hanging driver that wouldn't close or give Sonar the proper handshake to release it. M- Audio was known to have this problem.
 
A driver update may be in order.  

This has been my experience as well.  Not saying it's the root of the OPs problem, but should be ruled out to clear the path for other troubleshooting

When these issues were solved in the past, the usual culprits were either drivers not releasing, or issues with bridged plug-ins where the bitbridge server didn't close. Not sure if those are things that Cakewalk can address.

You know, I think I realized what my problem might be. I use JBridge for one plugin and one VSTi that I used in some of my older tracks that I revisit from time to time. Every time it happens I see multiple instances of "auxhost" that are also hung up in the task manager. So, big shock, my 32 bit plug and VSTi are most likely the root of the problem. I use only 64bit on all my current stuff, and never have a problem. My advice to the OP: If you have any 32bit plugins or VSTi's in your projects, try to find 64bit substitutes.

BobF

John
This is not normal behavior. I can't recall this ever happening to me. In the past when people had this issue it was often due to a hanging driver that wouldn't close or give Sonar the proper handshake to release it. M- Audio was known to have this problem.
 
A driver update may be in order.  

This has been my experience as well.  Not saying it's the root of the OPs problem, but should be ruled out to clear the path for other troubleshooting

I've had this happen with all versions of Sonar and it still happens with Platinum (definitely nothing 32 bit involved anymore) - I know in my case it originates from the Roland drivers (which aren't going to be updated, but they fit the OS I'm on), which are not interacting too well with some 3rd party software (K5 in my case, which is also a known issue at NI) ...
 
Nevertheless, Cake has to find some way to keep Sonar from crashing/hanging when the audio drivers give up for whatever reason ...
 
BTW, the OP is running what is probably the most stable audio interface driver there is ... which also happens to be what Cake officials are using themselves ... so ???

I had this happening most days when working on various projects with Roland Quad Capture interface. Plt would either crash, freeze, stop working or I lose sound. I'd have to go to Task Manager and time after time, Plt was there hanging. Ending the process it would typically it would take between 5-8 minutes before being released and I'd have to power down the Quad and terminate my midi keyboard as part of this process.
 
Of note, after upgrading to a RME UFX - love this interface BTW - on the rare occasion Plt stops working - and I mean rare - Plt is released almost immediately...praise the lord!

FreeFlyBertl
Nevertheless, Cake has to find some way to keep Sonar from crashing/hanging when the audio drivers give up for whatever reason ...

 
I'm not sure that Sonar can know the drivers have given up if they're hanging. It probably thinks they're still doing their thing. I get the impression that drivers tell SONAR what to do, SONAR doesn't tell the drivers what to do. I could be wrong.
 

BTW, the OP is running what is probably the most stable audio interface driver there is ... which also happens to be what Cake officials are using themselves ... so ???

Could be a 32-bit something somewhere...

Well, this problem has been around for several Sonar versions, under various error messages. I had Win 7 Ultimate and now Win 10, which is luckily more stable, except for that error.

It may well be worth Cakewalk's time to write some sort of a PC/OS debug tutorial then - even if it's not their bug. Where the heck do I even start looking - I make music!

The more you can educate your users, the less trouble you have.
 
Ludwig