Hi Martin,
Thanks for the quick response!
You’re right - sorry. Unfortunately, a lot of crashes even don’t write the dmp files. Anyway, here are some dumps.
Cubase 13.0.41 64bit2024.9.15 12.11.01.102.dmp (2.0 MB)
Cubase 13.0.41 64bit 2024.9.15 2.56.35.670-freezedump.dmp (1.9 MB)
Cubase 13.0.41 64bit 2024.9.14 17.38.51.196-freezedump.dmp.zip (1.0 MB)
According to this dump file, the crash was caused by Generate.vst3. If that’s the synth by Newfangled, it would probably a good idea to notify them as well.
THX for analyzing the dmp.
I check them as well and as far as I see it’s all over the place from Arturia Plugins to Zynaptiq to no Plugin at all.
I will collect a few, but I also have to work and that’s for shure in 12 
Again, thanks to everybody for the help so far!
Yes. Hereby are the crash files:
NO crash files found in the designated directory(!?!), not even ONE. Had 4 or 5 stops/crashes already in about 1 week. The whole program just disappears without any warning.
System: i9 12900KF, 64GB RAM, motherboard PRO Z690-P DDR4, graphics Nvidia 3060 with latest drivers, Audient iD24 interface (ASIO buffer 256 samples) with ADAT to Fireface800. Midi: Midisport 4x4. No other fancy or old hardware connected to the PC… cannot believe this release passed a beta test team.
Hi,
If you are on Windows, and DMP files are not created, use Microsoft ProcDump, please.
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).
Launch procdump64 via Command Prompt:
Cubase 13:
procdump64 -e -h -t Cubase13
Nuendo 13:
procdump64 -e -h -t Nuendo13
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.
ZIP and share the DMP file via Dropbox or a similar service, please.
Hi Martin, sorry but this does not work. When Procdump is running and I open a project in Cubase I get a window with several vst plugins having complaints about “running in the presence of debuggers”. I have screenshots for you if needed. But this way I cannot startup the projects normally.
Hi,
This freeze comes from NI Kontakt 7.
Hi Martin,
thanks for your answer. As mentioned above I check the dumps as well with Windbg and as far as I see it’s quite random; project won’t always crash from the same Plugin and no particular Vendor cause more or less crashes.
Every Plugin is up-to-date and working fine in Cubase 12. It’s unlikely that so many different Plugins suddenly cause so much trouble, especially when everything is working fine in Cubase 12; so I assume there is something going on in 13.
I will collect a few more dumps and hope they will help to fix it for good.
Thanks for the help so far!
I was thinking of updating from Cubase 12 Artist to Artist 13, but reading this is making me nervous to go ahead with the move.
I guess there are people who have not had problems. Cubase 12 is working fine for me.
Hi,
Then download and install Cubase 13 Trial. You can test it at your specific system, then.
Great idea Martin (as per usual) I will do that.
Hi everyone,
here’s a quick follow-up:
As mentioned in my previous post, I collected more crash dumps, but the results were still inconclusive—Cubase 13 kept crashing at random, with no specific plugin or vendor consistently causing the issue. I checked every driver on my studio machine, did a Windows repair install, and tried countless troubleshooting steps, but nothing seemed to work.
However, I finally found the culprit! Well, silly me—I had installed Game Ready drivers on a work machine, which was causing all the instability.
After switching to the NVIDIA Studio Driver Version 561.09, the crashes stopped completely.
Surprise, surprise… it turns out that using Game Ready drivers on a work machine wasn’t the best idea. Lesson learned!
So, for anyone facing similar random crashes: avoid Game Ready drivers and go with Studio Drivers for production setups.
Thanks again for all the suggestions and support!
I am exhausted with the crashes on Cubase 14!!! This is affecting my workflow severely. I’m using Windows 11….Even the plugins from Cubase or extensions like WaveLab are making my life hell this month. I never had those issues with 12 or 13. Please someone fix it!!! Oh and don’t use Soundtoys plugins with Cubase 14. If you do, your project will crash badly!!!
Hi and welcome to the forum,
Please, provide the *.dmp/ips file(s), so we can have a look, where do your crashes happen.
Mac: macOS Console utility > Crash Reports (or ~user/Library/Logs/Diagnostic Reports).
Win: %userprofile%/Documents/Steinberg/Crash Dumps
I solved the issues by stopping the use of SoundToys plugins. Now my issue is updating Cubase 14 (newest update, as of today). The assistant keeps on giving me an error and asking to try later….
Hi,
Please, don’t mixup multiple topics in one thread. Thank you.