just an update...it;s Rapture Sessions that crashes system...Regular Rapture is fine

Looking forward to hearing what the bakers have to say. This release has been a series of crashes, drop outs, clicks, buzzes, etc. Until now, Sonar had been working fine. I've made no changes to my system between versions. I hope there's a fix in the works. It seems to be only certain system configurations that are affected though. Many forum members have stated that their installs work fine.

CA-2A problem also. Not causing crashing but when it first installed it was available as a plug-in and I could insert it in the console FX box but after this recent update it has appeared as a small version in the pro channel so what's up with that.  I want the original as a plug in. Has anyone experienced this change ?

In SONAR, the CA-2A is PC module, VST2 and VST3 format plug-in. Depending on your VST3 migration settings, the VST2 plug-in may not show in the plug-in list but the VST3 should.

I got an email from Cakewalk support this morning and they suggested I do a clean install of Sonar...they linked me to guide and procedures for a few registry edits and stuff. After Clean install procedure  first things were working ok and now right back to same problems with Rapture Sessions, CA-2A, LP 64 and LP Multiband plugins. Only those Cakewalk products are having issues...all my other plugins and synths work fine. 

thornton
I had a problem with ca2a crashing inserted to the prochannel and GMP suggested to totally uninstall and reinstall. tried it and so far it has not crashed thank God.

You're right, uninstalling CA-2A and then reinstalling it, solved the problem. But it doesn't always solve the problem, sometimes it can create a worse problem, if for some reason VST scan gums up the works by stalling on CA-2A. I also got in a situation where I reset VST scan and then since it would stall on CA-2A it wouldn't' finish the scan and I lost many of my VSTi synths and VST FX.
 
Since I have saved a lot of image files I have the luxury of reverting back to a previous file when things go totally haywire. You can read about that from the several posts I've done in the past week all related to this issue.
 
As of now, I'm pretty pleased because I can get work done. I'm using 2016.09 and on 1st boot up, I open Plat and get a runtime error message, I'm careful not to close that window by hitting OK. I just move the window way out of the way and then everything works just fine. All the plugins and everything.
 
So I'd encourage everyone to at minimum do several system restores where you save the restore points or better yet make image files, which are a little more dependable. I’m glad to see someone at Cakewalk reporting that he’s found the problem and they’re actively working on a solution.
 

Just curious? Is this all a win 10 issue? Because I have dragged, dropped, inserted multiple (in some projects 5 instances) copies of CA2a, rapture, etc into several different projects and no issues at all. I am on win 8.1x64 though. I do have a pretty powerful machine, but not crazy. Just an i7.....Lots of ram though . 32gb. Hmmm. Hope everyone gets a fix asap
 
 
Edit: Not sure if it matters but I did notice I do NOT have a VST2 of CA2a, only the vst3 version?

Stratman: I'm using windows 10, but I have heard that some windows 7  and others have been affected. I didn't see your comment about not having vst 2 version of CA-2A. Funny.. I'm having issues with Rapture Sessions as well and it has vst 2 and vst 3 version too. As a test I could temporarily remove dll for vst 2 versions...maybe worth a try. Many users are not having issues since last update. It's a system problem possibly, depending on individual configurations...the work around I stumbled into is a bit cumbersome..hope a fix is coming soon.   

It appears to be related to a combination of the latest Win10 update and some obscure artifact in a few CW VSTs. A few Win7/8.1 users have checked in to say no issues, but there are also Win10 users who have not been affected. Or at least can get up and running after a couple of reboots. I did some checking on VST2 vs. VST3 with no useful conclusions, probably more of a red herring. 

Yesterday I bit the bullet and installed 2016.11 on my Win 7 machine. This is my primary DAW so I started by doing a full system backup and created a Restore Point in Windows "just in case"
 
The updates installed without a hitch.
 
After experimenting for a couple of hours, inserting synths, Midi Editing, drawing automation, tweaking Fx plugs, I 'm happy to report that NONE of the symptoms on display with my Win 10 computers manifested themselves.
 
I worked on several different projects with widely varying plugin configurations, including CA2A, Rapture Pro, Z3TA+2, LP64 etc.
 
So this, to my mind, firmly points the finger at a Win 10 problem.

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

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".

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). 

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