Ryan Munnis [Cakewalk]

Studious
Yeah, the classic "white-out" crash. I've waiting long periods, but it never recovers.  Check your Event viewer > Application after the crash to see if it gives any more detail. The error is usually something like: Apphang. Sonar has stopped communicating with Windows. Unfortunately this is a generic error, and tech support probably cannot assist, other than telling you to completely uninstall/reinstall Sonar.

I wouldn't have bothered putting this together if that was how we handled such issues: http://cakewalk.com/Suppo.../2007013262#CreateDump

We should encourage people to work with tech support, not act like tech support can't help. That mentality doesn't really help customers work nor Cakewalk create better products.

Soens, if you can capture a .dmp file and get it over to us we can take a look and see if there are any indicators of what might be hanging SONAR. I will admit these issues are a lot trickier to troubleshoot... but I don't personally tell people to just uninstall/reinstall like that.

BTW, when your interface drivers disappear like that because the program didn't shut down properly, one way of recovering them is disabling/re-enabling them from the device manager. It's still a pain but can save you from having to completely reboot.

True, I encourage folks to use tech support, unless they want to rely solely on fellow users for support.  
 
I was given no instruction to take a .dmp when I dealt with support regarding my white-screen/apphangs.  You should make this a part of support training, so everybody is working with the same tools.

Hi, Dave. You missed my point. Windows handles data from keyboards differently than it does from pointing devices like a mouse. People forget that although you generally don't have to think about keyboard and mouse drivers anymore they are indeed hardware and require the OS to interpret what is being inputted via "drivers" (if they can even be called drivers at this point but I'm assuming it's still technically a driver). So either Sonar reads the commands differently or Windows as the go between is receiving/sending the commands differently or a combination of both.
 
The Ctrl + S problem may not actually be real but if it is that is where things are likely mucking up.
 
/not a computer tech
 
Oh and considering that I have indeed had bindings fail to work while the point and click options were fine leads me to believe there is indeed a difference. It could be that because of graphical changes to to Sonar's UI how it receives those commands through the menus is more up to date whereas keyboard commands such as Ctrl + S that would have remained consistent throughout the years are using older code/protocols/whatever the heck is going on there.
 
Cheers.

My most common white screen crash trigger is SHIFT-L to enable looping during playback. My Sonar does NOT like that. 

Grem
I have used Ctrl+s to save so many times it's almost like breathiong to me. I hardly think about it. And I've never got a crash from it. Now I do it when Sonar is stopped. Nothing going. May have something to do with it.
 
@Steve
As for as loosing/"breaking the link" of my sound card. I have had something similar do that on my machine with the Realtec sound card in it using ASIO4All. And I will have to quit Sonar and start it back up after waiting like Chuckie  does for a few minutes till it all settles down to be able to get Sonar to recognize my audio drivers again. But this is not associated with the WSOD. So Steve, I now understand what you meant by "Breaking the link"!  

If you have an M-Audio2496, why are you using the Realtek and ASIO4ALL? Makes no sense to me at all. 

i've been getting a lot of these crashes lately, but everytime the event viewer says it's Massive.dll causing the crash.  now i know i have a problem with Massive, and i am supposed to call Native Instruments about it tomorrow night, but i don't remember which of all my projects have Massive in it, so whenever i try to open a project that has Massive in it, Sonar crashes; that would make it seem that Sonar crashes all the time, because i use Massive a lot. i can also make Massive crash whenever i try to open up one of my Maschine projects that has Massive in it, or a Kore sound that has Massive in it. it's definitely not Sonar's fault, even though i can crash Sonar whenever i want to now

Ryan Munnis [Cakewalk]
Soens, if you can capture a .dmp file and get it over to us we can take a look and see if there are any indicators of what might be hanging SONAR. I will admit these issues are a lot trickier to troubleshoot... but I don't personally tell people to just uninstall/reinstall like that.

Thanks Ryan, I will try, tho this has only happened once so far and there was no 'send a report' window.
 
Fortunately I did not have to reboot either. I simply reopened Sonar and went back to work.

99 times out of 100 when I get a whitescreen of Sonar death its a plugin. It happens more often when using 32bit plugs on the 64bit version but not exclusively so. Usually I go hunting for the naughty plugin thats causing the problem and deal with that directly. Its not usually Sonar on my system that is the root cause. Troubleshooting can take a lot of time while I try and eliminate variations and home in on the combination of circumstances that causes it with a particular plugin.