For me, the problems I had only affected SONAR - no other programs were affected, no BSOD, just the "SONARPLT.exe has stopped" message

Bristol_Jonesey
For me, the problems I had only affected SONAR - no other programs were affected, no BSOD, just the "SONARPLT.exe has stopped" message

thanks- I can understand a program having the occasional crash, and the update context seems pretty clear. BSOD's though are much worse again

BSOD's are nearly always down to drivers or hardware, theoretically it should be a lot easier to solve.

Bristol_Jonesey
BSOD's are nearly always down to drivers or hardware, theoretically it should be a lot easier to solve.

thanks - on this occasion no hardware has changed, nor have drivers, and nothing else is giving a problem (eg Reaper  and Sonar), only the Samplitude demo I am testing against Sonar. And as Samplitude is causing the BSOD it looks  like a win for Sonar :)

Gregh1957

Bristol_Jonesey
BSOD's are nearly always down to drivers or hardware, theoretically it should be a lot easier to solve.

thanks - on this occasion no hardware has changed, nor have drivers, and nothing else is giving a problem (eg Reaper  and Sonar), only the Samplitude demo I am testing against Sonar. And as Samplitude is causing the BSOD it looks  like a win for Sonar :)

Hardware can go bad, components fail, I've had more that one RAM chip go South. Also things like a buildup of dust inside your machine can trigger overheating followed by a BSOD.
 
Don't rule out hardware problems just because "nothing's changed".

Bristol_Jonesey

Gregh1957

Bristol_Jonesey
BSOD's are nearly always down to drivers or hardware, theoretically it should be a lot easier to solve.

thanks - on this occasion no hardware has changed, nor have drivers, and nothing else is giving a problem (eg Reaper  and Sonar), only the Samplitude demo I am testing against Sonar. And as Samplitude is causing the BSOD it looks  like a win for Sonar :)

Hardware can go bad, components fail, I've had more that one RAM chip go South. Also things like a buildup of dust inside your machine can trigger overheating followed by a BSOD.
 
Don't rule out hardware problems just because "nothing's changed".

thanks - I've had many a hardware fault in the past, some incredibly difficult to diagnose eg a motherboard that was affected by humidity. But typically they have affected the computer globally rather than a particular piece of software under a specific condition. But you are correct and I will test for a few more days before I am completely convinced it is Samplitude causing the problems.

After last Cakewalk Sonar Platinum update(2016.11) only cakewalk plugins crash my DAW(both Sonar and Ableton). All other plugins work as before. Nicely. I have done a few big projects after that update and no problems at all if i just don't use cakewalk plugins(CA-2A and Rapture Pro for example) Yes, Rapture Pro crash the Ableton also these days. I just try to add Rapture Pro for my new project and that project crash immediately(in Ableton live 9). 

[Update] - The shoe maker's elves must be dabbling in DAWs because everything seems to be working just fine now. No magic steps required before opening and running a project. No crashes or VST Scan hangs. The two changes on this system:
1. Installed 2016.12 Sonar update (since rolling back to previous versions or anything else did not solve the problem.)
2. Updated Win10 (Pro) OS Build  to 10586.713
- Note: I have -not- installed the latest versions noted in the Early Access sticky on CA2A and Z3TA+2. It's running fine with the previous versions which appears to be the case for most users. 

The crash problem appears to be fixed. I am so-o-o-o thankful!!!

On Tuesday of this week, all of a sudden with me not doing anything, I'm not getting any more runtime errors. In disbelief, I've rebooted several times, double clicked a CWP file and it all opens fine, no runtime error continuing today.
 
 I stopped all runtime error testing on Monday, reverted back to my working image file and just worked as normal, getting runtime errors a few times just to check it, then Tuesday it's all fixed.

 
Keep in mind I'm one of those just using 2016.09, never have even tried 2016.11 and reverted back to my 10/23 image several times. My crashes are linked to me having an internet connection.
 
After countless tests, I've determined that if I revert back to my 10/23 image disconnected from the internet. I never get runtime errors until I reconnect to the internet and then if I disconnect again I still have the errors.
 
 In other words something from the internet changed my computer. But no more, since Tuesday. Has anyone else noticed any improvements on Tuesday? Jackson? Robert? Or is this a mujlti-prong fix?