Audioicon

bitflipper
When was the last time you looked at the Windows Event Log, much less ran a crash dump analysis?
My guess is never, because it would mean nothing to you.

And by the way, I do not used Consumer Windows OS. I run Sonar on Windows Server 2012 R2 64.
See my other post on this.

 
 
I have heard some good things about running DAW's on server editions but I don't think I would try to problem solve on one. Sonar has never supported Windows server.

chuckebaby

Audioicon

bitflipper
When was the last time you looked at the Windows Event Log, much less ran a crash dump analysis?
My guess is never, because it would mean nothing to you.

And by the way, I do not used Consumer Windows OS. I run Sonar on Windows Server 2012 R2 64.
See my other post on this.

 
 
I have heard some good things about running DAW's on server editions but I don't think I would try to problem solve on one. Sonar has never supported Windows server.

I wasn't recommending Windows Server as a solution but rather as my choice for systems.
In addition to Sonar, I run everything else on Servers.

I have been using Windows Server and it works flawlessly with very little to no issues. I also have OZone 8 running on the Same Server Instance with SoundForge and CD Architect. 

Audioicon

bitflipper
When was the last time you looked at the Windows Event Log, much less ran a crash dump analysis?
My guess is never, because it would mean nothing to you.

And by the way, I do not used Consumer Windows OS. I run Sonar on Windows Server 2012 R2 64.
See my other post on this.

Hi. I don't remember if I read it on this forum or another, but it seems (some people strongly mean that) Windows Server (in general) are not the best to run a DAW on. I am by no means pc savvy, and have no knowledge of why, but thought I'd mention seeing it.
I will look and see if I can find the thread, and post it here.
All the best.

Zargg

Audioicon

bitflipper
When was the last time you looked at the Windows Event Log, much less ran a crash dump analysis?
My guess is never, because it would mean nothing to you.

And by the way, I do not used Consumer Windows OS. I run Sonar on Windows Server 2012 R2 64.
See my other post on this.

Hi. I don't remember if I read it on this forum or another, but it seems (some people strongly mean that) Windows Server (in general) are not the best to run a DAW on. I am by no means pc savvy, and have no knowledge of why, but thought I'd mention seeing it.
I will look and see if I can find the thread, and post it here.
All the best.

There are always valid arguments on both sides.
I have all of my production software on another Server:
PhotoShop, Dreamweaver, the entire Adobe Suite and Video editing and I have never had issues.

Importantly, the server runs and stay out of my way, it is enterprise systems and you are not going to have the issues you have on Consumer Windows but this setup is not for everyone.

Like this: "Windows have install updates and must shutdown." :)
 

I thought I was answering the OP. 
As my expertise here is non existent, I'll move on.. 
 

There should be no problem whatsoever running SONAR on Windows Server 2012, with the possible exception of a few unnecessary background processes. 
 
I happen to share Audioicon's point of view: there are definitely things a developer can do to make software more robust. My own software is mission-critical, meaning a showstopper bug can literally shut down a business and cost people real money. When it takes an error, it offers explanations in plain English (or French), automatically reports the error to me via email, and maintains extensive logs for post-mortem troubleshooting. Users don't call a middle man for help, they call me, the guy who wrote the software, and I answer the phone 24x7. 
 
But - and this is a big But - I also charge a lot of money for my products and services. It is unrealistic to expect that level of bulletproofing in a $500 consumer package.

Also, Audioicon, I want to extend an apology for assuming you don't know how to read a crash dump. 
 

bitflipper
Also, Audioicon, I want to extend an apology for assuming you don't know how to read a crash dump. 

No need to apologize, but I accept. I think in many ways you are correct, not everyone will understand Crash Dumps and Event logs.

I was thinking this may benefit Cakewalk in the long run if errors were easier to understand, this way users can post issues with less ambiguity. 

Someone saying "Sonar Crashes." Well, that could mean a million reasons and most may crashes may have nothing to do with Sonar but because errors are not easily interpreted for the user, Sonar gets the beating.

Again, I wasn't offended but thanks!

AI

OK, are you guys finished?

Getting back to the OP -
I just want to chime in as another who experiences the crash on exit.

It sure would be wonderful to get to the bottom of it.

I've verified all the latest drivers, verified the system memory, swapped USB ports/devices, swapped
internal cards around, altered the BIOS settings per other threads, and still the crashing continues...

No finger-pointing here, as it is most likely a faulty driver or VST plugin.

It'd just be nice to find and eraticate it so I have a stable system again...

I consistently get such error , when I save a CWP to a Bundle file. I get an error at the very end when Sonar exits; just prior to confirming that it went well. I do however get a CWB file which can be opened and modified. I always wondered if this error has any consequences.