My copy of Cubase 14 crashes without a particular pattern or plugin.
Win 10 64b Alienware 17 R5 Intel i9 8950 16GB RAM GeForce 1070 Focusrite 8i6 1st gen
It does not always produce a dump file, but the latest one is attached for support.
Sometimes it all works and closes correctly but yet still opens the Safe Mode window on launch.
I would really love safety, performance and workflow improvements way way way before any new plugins.
Thanks
The crash occurred in the plugin SampleTank, not in Cubase. Maybe there is an update available for this plugin?
Cubase itself is on version 14.0.10, while you are using 14.0.5.
Thanks Johnny for mentioning the update, I had missed out, now updating.
Sampletank is up to date and the crashes occur even when it is not in the projects, so I am puzzled.
Still usable though, and I love Cubase, I use it about every day
I updated, reopened, then just had another brutal crash, total shutdown, no dump file written do disk.
Was on another project, had just opened BIAS FX2, which had a modulator FX connected to it to modulate the wah. Wiped C14 out
C14 does not officially support VST2s anymore and BIAS FX2 actually is a VST2.
Have you already checked the tiny VST2 box in the (Studio>) VST Plugin Manager? You will find it at the very bottom.
There are other reports about BIAS causing crashes as it does not support the VST3 standard. However, maybe it works just fine with the VST2 box checked.
Hi, I have that box checked and other VST2 plugins work fine.
BTW I think BIAS FX2 is VST3, that’s the plugin extension and it says so on the website too.
But it could be that it has graphical issues. Or that the modulator (env follower modulating the wah) causes a glitch somewhere.
Which version of BIAS FX 2 do you have? It seems VST3 is not available in the Standard version according to Thomann. Anyways, you already said you saw the VST3 extension. Where do you see the VST3, folderwise?
However, it might as well be something else as you said.
I run the latest version 2.7.0.6600 (over a year old …)
The file is called BIAS FX 2_x64.vst3, in the regular Common Files VST3 folder.
The PG website says VST3 as well.
I will have to test if any projects that do not have BIAS crash or not … Not sure yet.
Very sorry to read that you have so many problems. Please do test what causes the crashes if you can and send us all dumps or maybe even projectfiles that crash your C14, if you get any.
Hi Alex, I got a repeatable crash on this fairly simple project, when I open BIAS FX2 GUI, it goes through its internal loading screen then wipes out Cubase with no dump file created.
But as I mentioned those wipe out crashes happened when I manipulated Sampletank for example. So not sure BIAS FX2 is the issue. It could also be either some graphical problem with the card, or some weird USB power thing who knows with Windows … .
I’d love a resolve as I work on C14 daily and I love it otherwise ! Thanks !
NEW CRASH with Waves StudioVerse this time, no dump produced but here is a screenshot with the Windows Task Manager showing Cubase stuck.
This is an empty project based on my regular template.
I cannot state enough how I’d prefer stability and smooth workflow over new plugins.
Generate a DMP file and share it via Dropbox or a similar service, please.
Use the Microsoft ProcDump utility to generate a DMP file, please.
Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
For example:
cd C:\ Users \ \ Downloads \ Procdump
Note: the dmp file will be written into that folder.
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behaviour (see next step).
The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.
Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.
ZIP and share the DMP file via Dropbox or a similar service, please.
Hi Paul could it be because I am using a VPN ?
I have to, I am based in China, lots of services do not work without.
I did the same test with and without the VPN, always crashes with loading StudioRack.
After testing all my Waves plugins on a new empty project, several other ones crashed too (FlowMotion, H-Comp, Lil Tube )
I am at a loss, crashes with Waves, Arturia, and Positive Grid plugins.
And it is quite recent, I hope to get some help otherwise I will be due for a drive reformat and total reinstall with Win 11 …
Unfortunately, we have no way of telling exactly what is happening. All that we can see is that Cubase can’t continue because Waves is trying to contact the network. It could be the VPN, your Firewall, a problem with Waves’ servers, etc.
I suggest that you ask on Waves’ forums or their tech support. Maybe there is a way of using the Waves plugins in an offline way so they don’t need the network. Try running the Waves Central application to check the license states.
I checked WCA all is well and up to date.
But it cannot be a Waves issue as the Arturia MS-20 filter creates the exact same issue, hanging on a white GUI making Cubase irresponsive.
Attaching the dmp file for this one, also on an empty project.
I would be surprised to learn Cubase hangs because of an internet connection issue, that would be something to be addressed as a serious bug. Thanks for helping me !
It isn’t Cubase itself that is hanging, it’s Waves. Cubase has no control over what the plugin does, or if it returns from a function.
This latest hang is Filter_MS_20.vst3, but doesn’t appear to be network related. This could be a multithreading bug in MS-20 because it’s waiting for a lock that it has set in another thread. This appears to be entirely within the plugin and outside of the control of Cubase.
Cheers Paul ! Got it. I’ll message both Arturia and Waves then.
Good thing is I have enough plugins alternatives to get by, but the MS-20 is such a lovely filter ! I hope to get it sorted, it used to work well until recently !
