Hi,
Just to tell you that today I had several crashes which did not generate a dump file.
Cubase 13 .0 21 crashed when I was just moving tracks or using fade out / in functions.
I think that you need to attach the crash files…
Unluckily it didn’t generate any crash file.
There’s nothing at “Documents\Steinberg\Crashdumps”
2 Likes
I have also had this happen the last week, countless occurrences of doing super-normal stuff in Cubase and then BOOM-CRASH, no crash/dump file created and it doesn’t even allow me to open up the save-file pre-crash sometimes saying it is corrupted. Make sure you are saving religiously!!!
I’ve had to switch back to Cubase 12 Pro due to the poor stability of C13 until all the technical gremlins are ironed out. I hate feeling like a beta-tester on a point-release (that we all had to pay for no less) where not even the day-one patch (13.0.2 and 13.0.21) have solved any of the still-standing issues in C13.
What gives?
1 Like
And what if it doesn’t create one like it’s supposed to?
1 Like
You can use procmon to generate crash file, if cubase doesn’t.
2 Likes
Instal ProcDump and run it when Cubase stuck. Then open .dmp file using WinDbg to see what happened. Some of my problems with Cubase 13 are connected with Softube Console1. But most problems are gone after uninstalling Sonarworks SoundID. The only one persist - how can I live without SoundID?
Hi, have your reported this to Sonarworks?
Cheers,
Armand
Hi @Xion
Sorry to hear about your crash. We would like to investigate but for this we need a very clear way of reproducing this crash. Does this crash happen with any project, like you can reproduce it from scratch by just performing a few elementary steps? Or does it seem to only happen with a specific project? If the latter, we’d like to get your CPR project in PM via wetransfer link.
Cheers,
Armand
Hi,
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 behavior (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.
- 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 @Armand & @Martin.Jirsak
Unfortunately I won’t have time to take care of this before I return from vacation.
On the other hand, I can describe the behavior of Cubase 13 when this happened: Cubase crashes and restarts automatically (of course the work in progress is lost).
As for reproducing the bug, not so easy even if it happened to me twice in a row.
What I can remember :
1 - Vocal unmixing via Spectralayers one.
2 - import track (vocal only part) into my project (48khz to 44 khz).
3 - editing the track (fades, cut/paste etc…) with a few effects insert.
4 - moving audio clips (to align them with the project) crashes Cubase.
I use the Cubase 13 Pro demo version.