Hello! Looking for help on where to start in tracking down my crashing issues since 22.11. I noticed many threads pointing to CA-2A being part of the issue and I expect the dev team to release a hotfix to whatever is causing the issue related to CA-2A. Thing is I'm having the same issues but I don't have the CA-2A installed.

I'm worried the hotfix wont address my issues specifically. So where do I start with minidumps et cetera? I have sent in fault reports in the rare instances that it pops up. I have a bunch of minidumps.
 
So far my only recourse has been to safe mode my projects and rebuild them synth by synth in a new project. It's a huge buzz kill and time sink. I have unhappy clients which makes me an unhappy camper but I have patience and hope this can resolved soonish.
 
So where do I start?
Thanks for any help.
 

Revert back to oct for now

bitman
Revert back to oct for now

Can anyone speak to this? I've seen mixed messages on the success of rolling back. I've personally attempted rolling back to 22.10 with no success.

I'm kind of cautious about rolling back too far but if 22.09 is working I'll give it a try.

I have 22.09 on my other machine and it's all good, but I didn't roll back. I've seen quite a few other posts where this does not solve the current issues...may be risky.

You might as well try rolling back. You can always go forward again if it doesn't help. I have done it any times in the past wit out ussue.
 
FWIW in the future I find it is good practice to take a disk image of the system drive (I use Acronis True Image) before applying updates. That way you can always return it to it's previous state if needed.

I tried rolling back but the crashing Persist. 
 

"FWIW in the future I find it is good practice to take a disk image of the system drive"
Best advice!
That being said, Win 7 here and no issues with "11" on the Cat or my x86 office rig.
 
T

DeeringAmps
"FWIW in the future I find it is good practice to take a disk image of the system drive"
Best advice!
That being said, Win 7 here and no issues with "11" on the Cat or my x86 office rig.
 
T

Kind of makes you wonder if an automatic update of Window's 10 broke Sonar. This issue is occurring on my Desktop and laptop; both are running Window's 10. 

You are not alone with crashes unrelated to the ca-2a.  I have also sent in crash dumps.  I have only seen this with my laptop using the waspi driver mode on fully updated win10.  I am happy they are making improvements for this type of driver and look forward to a fix.  I understand there are many drivers to be verified and understand it will take time.  I did not update my main daw with the Nov. update and also recommend you roll back for now.

I'm having the same crashing problems since the update. It's happening on both my studio DAW and my portable laptop DAW that i use for remote recording so it's got to be something in the update. I tried rolling back to October and that didn't work so I reinstalled the most recent update. I tried it again and it didn't work...but, for some reason I started up Sonar again (without rebooting the computer) and tried to open the same project and it worked. This also is consistent with the laptop DAW.
 
In summary, on both my laptop DAW and studio DAW, Sonar doesn't crash when it opens. It crashes when it tries to open a project. Like I mentioned above, if I start up Sonar again after the crash and try to open the same project it works. I have never had problems with Cakewalk programs or Sonar so this is unusual and I'm not happy that I have to go through this to get the program running but at least I'm not dead in the water....at the moment