I’m headed over to Soundtoys next, but in the event anyone else is having this issue .
Surfing around, I’m not seeing similiar problems, so this is odd. I’ve attached the event log and chatgpts synopsis.
You now have two separate crashes caused by different Soundtoys plugins:
Plugin
Exception Code
Issue
Decapitator.dll
c0000409
Stack buffer overrun
DevilLocDeluxe.dll
c0000409
Stack buffer overrun
This indicates a broader compatibility or stability issue with your Soundtoys plugin suite on your system in the current setup.
both VST2 and VST3 versions are crashing cubase 14.
Most Likely Causes
Outdated or unstable Soundtoys plugin versions
→ Especially if you’re using a June 2024 build (your timestamp: 6669b5ad) — it may not be fully compatible with Cubase 14.0.20 or your system config.
Deep memory conflicts (buffer overflow) between Cubase 14 and Soundtoys plugins
→ Possibly due to certain project settings, automation states, or preset loads.
This is a brand new build. Windows 11 OS. All plugins and Cubase up to date.
My solve: The only way to bypass this is to log into Cubase with the 3rd party plugins disabled. Save as a new file, remove the sound toys plugins, close out, quit cubase. load back in, and replace the plugins. It is not stable. I can get the session to export, but when I open the file, i have to repeat the process.
No, I can’t confirm this issue here with Decapitator/DevilLoc on my side but I am running on Win 10 22H2. Which Windows 11 version do you use?
I guess you have the latest Soundtoys update - have you tried to reinstall the Soundtoys suite without VST2s?
Maybe the VST2 button in the Plugin Manager is enabled and you are accidently running VST2 versions of these plugins?
Can’t say I have had any problems with Soundtoys (v5.4.1.17134) on the latest Win11 either.
It is not completely unthinkable that is is a combination of plugins in your project, some weird incompatibility with other plugins.
Is this just the one project that crashes, or does it happen with every project you work on?
It’s 6 months later, and I’m still having issues with these plugins. If I leave them in a project, at some point the project refuses to open and I have to open the project with third party plugins disabled. I then take off the sound toys plugins. Save, and the project opens up again. Sucks because I love these plugins…and bought the whole suite.
It’s not random. Every new project I create has this issue.
I’ve gone and added them to the firewall in the event that was the issue. I’ve updated them to the latest version, I’ve deleted and reinstalled vst 2 only, vst 3 only, and both. Still the same result.
looking at the plugin manager, they aren’t blacklisted and are recognized by cubase.
Down the road, I’m hoping an update in either windows, cubase, or sound toys eventually solves this.
I have been running the soundtoys bundle problem free since 2009, in many different versions and combinations. Do not Cubase create crashdump files? have you the same issue with different versions of the soundtoys plugins?
have you heard anything from Soundtoys?
In the meantime, I’ve been running the Soundtoys suite also on a Win 11 24H2 rig - not a single problem. And I don’t recall having a problem with Soundtoys ever for the last 15 years…
Maybe it’s like @fese said and it’s a combination of plugins?
Can you upload a screenshot of your mixer next time this happens?
Owning them and not being able to use them - that’s unfortunate to say the least…
I had this problem for a while and contacted SoundToys and Steinberg. They fixed the issue for some months but it’s happening again!!! I am tired with the crashes, and my patience for fixing this issue is running low, so I guess I got no choice but to move on from Soundtoys ….
Outdated or unstable Soundtoys plugin versions
Deep memory conflicts (buffer overflow) between Cubase 14 and Soundtoys plugins
System-level conflicts (rare)
….