Rob[atSound-Rehab]

bitflipper
This is a program bug (stack overrun), and can't be resolved by user action such as deleting aud.ini. We'll have to be patient and wait for a fix. I'm sure somebody is furiously working on it this morning.

 
that'll be a hard one to eliminate as it appears to be failry random
 
I have 2 machines with different hardware but identical DAW installation and win10 update level. One works fine with CA-2A, the other crashes the first time I insert CA-2A

sounds like a driver issue then, is that the only difference?

fwiw, i'm having no issues in another daw with the vst3 version of ca-2a

eta, this was a quick test with asio4all driving the onboard realtek

pwalpwal

chuckebabyIf the updates worked perfect there wouldn't be a separate download
Here is Windows 10 4.6.1:
https://www.microsoft.com/en-us/download/details.aspx?id=49981

separate installer downloads are made available for the huge swathe of enterprise PCs not using standard windows update, for example i regularly have to download standalone installers/updates for servers due to firewall restrictions, etc
hth

im simply just trying to help here. I have no crashes with CA2A on my system. So I could care less.
I am looking for a possible solution and not trying to debate..what enterprises don't use Windows update.
I do know one thing. Runtime errors have everything to do with .NET Framework. what's it going to hurt ?
 
So with that said, im out. gave a possible solution. im not 100% sure it will even work..
Its probably a bug in Sonar. but im not seeing it. so there's a debate.
Possibly im using Windows 8.1 ? I don't know. there's another debate.
 

Since the last two updates I've both vst scan issues and instances of crashes when trying to instantiate vsts...mostly waves. Hope they get this fixed asap.

boblev posted a great solution here:
http://forum.cakewalk.com/CA2A-LP-64-EQ-causing-Runtime-errors-m3522270.aspx#3523378
 
The bottom line is don't close the runtime error window. Leave it open, Sonar won't crash - all is well
This indicates that this runtime error should not even be happening, because nothing really is wrong. Otherwise Sonar would not be working properly after that.
 

bitflipper

Rob[atSound-Rehab]
that'll be a hard one to eliminate as it appears to be fairly random
 
I have 2 machines with different hardware but identical DAW installation and win10 update level. One works fine with CA-2A, the other crashes the first time I insert CA-2A

For me it's consistent and repeatable. But it only happens the first time I run SONAR after a reboot. After the first crash, it's fine.
 
Do you still see a difference between your 2 machines if you reboot both before making the comparison?

Bit,
you were right. if I reboot each machine, I do get a crash on each one, just like in your case "But it only happens the first time I run SONAR after a reboot. After the first crash, it's fine."

Rob[atSound-Rehab]

bitflipper

Rob[atSound-Rehab]
that'll be a hard one to eliminate as it appears to be fairly random
 
I have 2 machines with different hardware but identical DAW installation and win10 update level. One works fine with CA-2A, the other crashes the first time I insert CA-2A

For me it's consistent and repeatable. But it only happens the first time I run SONAR after a reboot. After the first crash, it's fine.
 
Do you still see a difference between your 2 machines if you reboot both before making the comparison?

Bit,
you were right. if I reboot each machine, I do get a crash on each one, just like in your case "But it only happens the first time I run SONAR after a reboot. After the first crash, it's fine."

this sounds like it could be some service that hasn't started up? then the first run/crash starts the service, so it behaves after that... just a thought

so now I made the mistake to do a full VST scan on the machines with 2016.11 and it crashes/stops in several Cakewalk VST2s and VST3s (Rapture Pro, CA-2A, Z3TA) but not in any 3rd party!
 
worst of all, rollback to 2016.09 does not change this. so how secure is the rollback procedure again?
 
when VST scan is executed a 2nd time it seems to get thru - so this appears to be a similar issue to the 1st time one of these cakewalk plugins is instantiated after a reboot, it crashes. 2nd time around it seems to work.

Rob[atSound-Rehab]
worst of all, rollback to 2016.09 does not change this. so how secure is the rollback procedure again?

does rollback also rollback the shared stuff? certainly the old, pre-monthly update system never used to, for example, if i had x3, and installed platinum demo, then uninstalled platinum demo, it would leave behind things like the vst scanner, shared stuff... noel even suggested that this was a way to get updated on the shared stuff without having to buy the whole kaboodle (sp?)

I am pretty sure that is accurate. Additionally, registry entries added will also remain. The best method to "rollback" is a system restore prior to installation. These days restore points prior to installations is good practice for any software.