Crashes when opening third party plugins + A temp fix. (I hope..)

Cubase
1

Hi

Earlier this year I upgraded to Cubase 13 Pro and are really loving it.
But…

It started crashing whenever I open some third party plugins.
It doesn’t seem consistent as to which plugin will crash Cubase, but to mention a few that have caused it:…

Soothe2
Waves Butch Vig Vocals
Waves SSL G-Master Compressor
In fact… Several Waves plugins may cause a crash.
(Don’t use many though)

It’s not the only ones, but can’t remember the rest on the top of my head.
The weird thing here is…
Take Soothe2 as an example.
I have a few loaded into a project. One on my guitars group, one on the bass track and one on a choir group which is side chained to the guitars group. When I open Soothe2 on the guitars and bass tracks, all good, but opening the one on the choirs group crashes it all. Also any additions of Soothe2 will also make Cubase crash, so removing the culprit to try to load in a fresh one don’t work.

As I wrote the above, I was testing on the side to see if I could make things work again. I reinstalled all Waves plugins and Soothe2 and at first it seemed to do the trick. I opened an empty project and tested on a clean slate. All the plugins loaded in nice and fast, and all seemed fine. I then opened the project I mentioned above, and again… All good.
So I started working again and all went fine.
Until…

The problem returned when I opened a plugin while the project was playing. This time it was Waves H-Comp Hybrid Compressor that crashed it. I rebooted Cubase and tried to open the plugin from a clean slate, but still it crashed. I un- and reinstalled all Waves plugins (again…) and they all worked fine after that.

I think the problems occur when opening some plugins while the project is playing. And after the crash occur, it seems like it’s broken “for good” and it will require a un/reinstall to fix it.
Of course you could say…
“Then don’t open those plugins while playing…”
But I’m sure we all can agree that it’s not a viable solution.

Naturally, every program installed is updated to the latest version.

I run Windows 11 Pro ver. 23H2

As for my hardware:
Processor: Intel Core i7-8700K CPU @ 3.70GHz
RAM: 32.0 GB
Sound: Focusrite Scarlet 2i2 - 2nd Gen
Graphics: NVIDIA GeForce RTX2070
Drives: 2x WDS100T2X0C-00L350 (2x 1TB SSD)

2

I’ve been having this issue since v11. Waves says it’s a Cubase problem, Steinberg says its a Waves problem. To add some more data for you…

It’s actually not when opening the plugin, it’s when opening the editor. The plugins that this happens to will work and even read automation data as if nothing’s wrong…until you try and open the editor. which leads me to my next added data…it’s not just new plugins. I’ve had this happen to plugins that have worked for months in projects to just one day give me a white gui and a frozen cubase when trying to open the editor.

it has nothing to do with the project playing or not. i’ve had it happen on the first plugin inserted into an empty project when i tested it.

of all my other 3rd parties, which admittedly i don’t use alot, work fine. it’s only waves, and for me it’s only the h-delays, h-comps, butch vig vocal, and abbey rd mastering. maybe submariner once. the others i use (less than 10-ish i think) it never happens on.

i also doubt it’s my hardware. r9 5900x, 128 GB ram @ 3200mHz, 3080 12GB, 2 x Firecuda 2TB (one system, one samples/libraries, Ironwolf 2TB (to record to), 2 x WD 6TB 7200 rpm spinners (backup space in a mirrored RAID), A&H Qu24

as oldman said, once it happens to a plugin it never seems to fix itself. i’ve actually tried uninstalling and unregistering the plugins, uninstalling waves’s installer software, and cleaning the registry of any mention they even exist and that’s not fixed it.

3

can’t believe i forgot this when i posted. at one point both waves and steinberg agreed that it was 100% me using v9 of the waves plugins and cubase only officially supporting v11 and up and that upgrading all my plugins would definitely fix the problem. Cost me a couple hundred bucks and wouldn’t you know, it did not fix the problem.

yesterday after posting, just for poopies’s and giggles, i went and uninstalled, cleaned the registry, redownloaded, reinstalled, and re-registered my waves stuff. Still fucked lol

4

I got the same problem as yours. Do you get anything to fixed?
It’s happens to some 3rd party plugins.

5

God I just found a fix for me. It’s Rivatuner that I install to check fps and temp when playing games. I think it’s also detect 3rd party plugins because it use graphic card. After just disable auto detection, there’s no crash so far.