Historical Sonar/CBB Crash Knowledge Base

I have had my own share of Sonar Crashes, some I can tolerate but others just make the software appear worthless at times, especially given the damage this can cause.

I like to think I have the most robust system: RME Fireface UFX Plus (Best Drivers) running on an extreme minimalist configuration but still sometimes I get crashes. Then I have to stop being a musician and play IT guy.

With my rant (frustration out of the way), I am wondering if there is an interest or if anyone has ever compiled a list of crashes and solutions. I have been seeing several post with helpful information but these are all over the place.

I am sure this information is passed on to the team but is it available as part of the knowledge base in the near future.
As part of the new CBB is this something that can be created as these problems are posted and solved, especially given there is no Phone support?

I am referring to critical errors that can cripple an entire session, how are these solved and should we have a knowledgebase as part of the growth and need to make CBB a more solid and attractive platform?

This could be all errors but I am thinking to begin with more critical stuff.

Is this an area of interest?

slartabartfast
There is a limited official knowledge base for SONAR et. al.
https://www.cakewalk.com/Support/Knowledge-Base
 
I am not clear if it is being maintained for CBB. This forum is probably the most complete accessible  troubleshooting system. It suffers from poor organization and searchability, incomplete descriptions of systems problems and solutions and is apparently facing extinction at some time in the future. Your best bet is to search for a problem with Google [problem descriptor] site: forum.cakewalk.com and if that fails, post as complete a description of your problem as software support would expect here and wait for scook.

I am referring more to specific issues nothing close to what that link provides. Something professionals can refer to. For example: Each time a user reports a persistent crash, I see people requesting crash dump, then the issue is solved and nothing is really documented.

Example: The following Hardware, when used XYZ will cause Sonar to crash. Again, I am just showing an example but this will be based on crashes reported by users.

The fact that after decades we still have sporadic crashes, even on robust systems does not help any system.

What happens Scook is out of town?

So is what you are looking for is something like the Microsoft Knowledge Base? 
https://technet.microsoft.com/en-gb/ms772425.aspx
This kind of thing has never existed for Cakewalk products, and Microsoft has been making it harder for the average user to find and use over time, apparently preferring to hijack problem requests to pages that tell you how to buy or use their products.
 
Or maybe you are looking for a problem reporter. There was a built in trouble reporter in later versions of SONAR that purportedly sent a memory dump and problem report to Cakewalk, but my understanding is that has not been carried over to Bandlab. 
 
If you are just looking for access to technical support for your particular problem then you can contact support, but it sounds as if you are asking about a more complete and accessible self-help system. I have personally found this very forum to be useful at times, if tedious to search and interpret.
 
 

slartabartfast
So is what you are looking for is something like the Microsoft Knowledge Base? 
https://technet.microsoft.com/en-gb/ms772425.aspx
This kind of thing has never existed for Cakewalk products, and Microsoft has been making it harder for the average user to find and use over time, apparently preferring to hijack problem requests to pages that tell you how to buy or use their products.
 
Or maybe you are looking for a problem reporter. There was a built in trouble reporter in later versions of SONAR that purportedly sent a memory dump and problem report to Cakewalk, but my understanding is that has not been carried over to Bandlab. 
 
If you are just looking for access to technical support for your particular problem then you can contact support, but it sounds as if you are asking about a more complete and accessible self-help system. I have personally found this very forum to be useful at times, if tedious to search and interpret.

Yes, but I am not looking to solve a problem at the moment. 
What I meant to ask or to convey is: If there is nothing, is this something Bandlab is interesting in making or keep track of and making it available to users?

For example: It could be something as simple as a page which shows what are factors most likely to cause a crash.
It could be anything from hardware to something else. What I am getting at is all of those Crash reports and solutions being in a single Knowledge base.

Thanks, you explained it better than I did.