> Have you noticed any changes on the appearance of your CPU core balance? 
 
Mine were remarkably low and well balanced -until- the latest update. I've only had to time to run a few  larger projects since the latest issues but noting large discrepancies across the cores with #1 spiking considerably higher than all the rest. 
 
 


I noticed this exact thing last night. My system was running rock solid for months now. But last night with the new update, I did notice the cores much higher than normal (on an existing project), and the #1 core sometimes spiking in the red, which has NEVER happened previously. That being said, I have not experienced any of the other issues noted in this thread, and my system remains very solid thankfully.
 
~Jeff

Might this have something to do with VST3 plug-ins?

Please ensure that any crashes are logged with Cakewalk and report back the CWBRN # here to make it easier to follow up.  (@bitflipper)  As far as issues with Windows Update, it's possible, we're confirming that our redists are up to date with Microsoft.
 
Otherwise, standard diagnostic procedures apply.  That is, try new projects, remove the possibility of 3rd party plugins causing possible memory corruption, etc.  
Do know that we do a lot of testing with clean images of the OS to make sure we don't have issues with missing/mismatched system components and thus far we're not seeing any of the reported issues.  We also of course try systems that have had several version of stuff on them.  Still working to repro however.  Thanks and keep us updated.
 
Keith

Keith, feel free to bring you development environment to my house and debug on my computer.  Seriously, I'm an hour north of Boston and CA-2A crashes every time I open a project that has it.
 
I'm fairly certain that my problems started after I installed a new graphics card this weekend.  I downloaded the latest Nvidia drivers and that's when trouble appeared to start.  I was running 2016.09 at the time.  Upgrading to 2016.11 did not fix the problem.  I'm wondering if the Nvidia drivers installed a version of the C++ redistributable runtime that is not compatible somehow with some plugins.
 
Jim

Something is up with the 2016.11 Release
 
1 - Have noticed I get the 'Add Track' dialog appear at Random times
2 - Seems to be some issue with Rapture Session. Although I didn't immediately get an issue,  I now get a crash on loading some projects (during the project load process, the bug reporter doesn't kick in). I did a debug and found that the error was:
 
Unhandled exception at 0x00000000328F4A48 (RaptureSession_64.vst3) in SONARPLT.EXE: Fatal program exit requested.
 
So I tested opening a blank project, and inserting Rapture session -  I get the same crash.
 
So seems an issue with RaptureSession_64.vst3 ?
 
 

Jim Kalinowski
Keith, feel free to bring you development environment to my house and debug on my computer.  Seriously, I'm an hour north of Boston and CA-2A crashes every time I open a project that has it.
 
I'm fairly certain that my problems started after I installed a new graphics card this weekend.  I downloaded the latest Nvidia drivers and that's when trouble appeared to start.  I was running 2016.09 at the time.  Upgrading to 2016.11 did not fix the problem.  I'm wondering if the Nvidia drivers installed a version of the C++ redistributable runtime that is not compatible somehow with some plugins.
 
Jim

Jim, does the fault reporter kick in (from 2016.11)?
If so, please send us the minidump file and let us know the cwbrn #.
We can diagnose it given the dump file.
 
Keith

Sonar is crashing on my system after upgrading. I getting a Runtime Error after after loading then Sonar crashes and requires a reboot. The Runtime error shows the path of the program followed by the following: "R6025 Pure Virtual Function Call".
 
Crap, just tried rolling back and Sonar still crashes. It seems to crash on certain projects. I was able to open an older project but the program crashes when I try to open the current program I was working on.
 
Update, 
I just tried to open the same Project on my Laptop which is three days old and I get the same error.
 
New Update
I was able to do a little troubleshooting with the project before closing it. I removed the waves renaissance RVerb and a UAD reverb plugin and saved the project using a different name. After another reboot, I was able to open the project without receiving the Runtime error.   

Keith Albright [Cakewalk]
 
 
Jim, does the fault reporter kick in (from 2016.11)?
If so, please send us the minidump file and let us know the cwbrn #.
We can diagnose it given the dump file.
 
Keith

I don't recall the fault reporting kicking in (but I'll try again tonight).  I only recall a small Windows dialog coming up saying SONAR had unexpectedly stopped.
 

The fault reporter has not kicked in with any of my crashes so far.
Loading an existing project on freshly booted PC after starting Sonar results in SONARPLT.EXE crashing.
I've also had  "R6025 Pure Virtual Function Call" errors without the fault reporter kicking in.
@jackson white's and my issues seem to be similar

@Keith Albright
 
1. CWBRN-61566
2. I'm testing with the simplest possible test project. 1 audio track, 1 bus, no audio or plug-ins other than PC EQ (and 1x CA2A)
3. Started exploring the VST3 angle but the LP 64 EQ/MB are not VST3. RaptureSession and CA2A are VST3
    3a. LP 64 EQ / MB throw the "Runtime Error!" when running the VST Scan.
    3b. "CA2ALevelingAmplifier_64.dll" will hang VST Scan, requiring a close and rescan to finish the VST scan.
          Sometimes VST Scan will appear to hang on another instance of CA2A (only displays "CA2A" in the toast)
    3c. RaptureSession will hang VST Scan, requiring a close and rescan to finish the VST scan
 
There may be problems with other VST3s, won't have a chance to explore that until Thursday. 
 
4. FWIW I'm focusing on the CA2A as the only plug-in in regular use and the issue is -very- repeatable on my system. I wiped out my original (paid) install, (uninstalled via Control Panel, deleted all registry keys and reinstalled via the CCC) and can generate a "SONARPLT.exe has stopped working." every time I open a project after restarting the PC. 
 
5. The "Fault Reporter" has not been launched for any of these recent issues. (I was seeing it on some Take Lane crashes with previous updates.)