Hi, I’m having this problem since i was on windows 10, I’m in the middle of a project and i get a random crash of all cubase closing without any error message.
I first upgraded to the latest cubase 12 (12.0.60 i believe), it didnt solve the issue.
I formatted and upgraded OS from Windows 10 to Windows 11, reinstalled everything (daw, vst, effects, licenses, everything) and i noticed an improvement of the performance, but then when working on the same project for 2 hours, random crash appeared again.
I checked the event log in windows and saved the files if anyone can help, my system specs are Intel core i7 6700 64gb ddr4 ram, a lot of ssd and m2 for the libraries
Windows 11 Pro
Libraries used in the project: Kontakt 6 full, Opus, Spaces II Reverb, native eq from cubase
Cubase 12 crash.zip (8.4 KB)
Thanks in advance, i hope to get this solved because i love this program!
The Cubase crash logs are what’s needed.
If they were created during the crash, they are located at
Unfortunately i dont have any crashdump file in that path, very strange.
Aditional info: the crash ocurred after i added 2 libraries with sineplayer, (the only 2 instances of sineplayer in the entire project), the rest is all kontakt and opus
If anyone have a similar problem without getting a crashfile from cubase, please share any valuable info here too
If you remove SINEplayer, does not still crash?
Right now im testing the project without sineplayer, and so far so good, but i remember that this type of crash have ocurred also without sineplayer in the project, i will test this more time and see what happens
Well, it just happend again, this time i did not add any new instrument vst, no log file in cubase path, same pattern as before
another info i noticed, it happens during playback of the project
Cubase 12 crash 2.zip (6.8 KB)
I can only offer the banal advice to rule out prefs problems by starting in Cubase Safe Mode with disabled preferences
THere are .dmp files referenced in the file you uploaded, maybe it’s still there?
i found only one file in that path (i think its from the first crash that happened when i wrote the first post)
WER.3d653114-435f-4388-9211-325505f96331.tmp.WERInternalMetadata.xml (6.5 KB)
Well after monitoring this issue in the task manager of windows, i noticed that during the playback of the project the amount of ram used increases from 40gb to 60gb (i have 64gb) so im thinking that this crash could be the windows closing the aplication to preserve the system stability.
I believe this is the issue and not some plugin or something cubase related, as the app dont show any dump file, i think this thread can be closed because it involves my hardware resources and not cubase, thanks for lending a hand Steve! It was really apreciated !
I did not know that was possible, Windows shutting down a program. I doubt it really.
Did you do this essential troubleshooting step?
Im testing it at this moment, I also have noticed something different and very strange.
I initiated cubase in safe mode with all the preferences disabled, I opened the project and kept watching task manager, when all the libraries and tracks were loaded, I started the playback, at first, the project with all the vst purged was using 16 gb of ram, after the first full playback it increased to 22 (something predictable because of the purged tracks)
But here is what things starts to get weird… for experimental purposes i started playback again from the begining without adding any track or vst, fx, etc any kind of new midi data or stuff to the project, when the playback reachs the end of the track (about 3 mins or so) the ram consumption in task manager were slowly increasing, up to 28.8gb
I repeated this procedure and with the 4th playback the ram goes up to 40gb and increasing
Every playback increases the ram consumption of the project, without adding ANY new track fx or thing
and when it reachs near the 60gb of consumption it crashes, and the most crazy thing is that kontakt, opus and sine are showing that the total ram consumption is much lower that what is reporting the task manager, really weird
Generate a DMP file and share it via Dropbox or similar service, please.
Use 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 harddisk.
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.
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:
procdump64 -e -h -t Cubase12
procdump64 -e -h -t Nuendo12
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 exeptions 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 similar service, please.
Thank you for the detailed guide, i did as it says, and started the procdump when the project was using 40gb of ram, i noticed some exceptions when the ram consumption was about 55gb+ and then it crashed when it reach almost the full 64gb, here it is the more detailed dump file i hope this helps !
https ://drive.google. com/file/d/1TM_A6s-kxTr3Jn4hyQiOg6uYLJqQ5ISY/view?usp=sharing
I used two blank spaces because i can’t add links (maybe because I’m new to the forum?) remove the spaces and the link should work fine i hope.
Thank you again!
I am not an expert but what you describe sounds to me like a memory leakage. Ie. one component allocates memory, then doesn’t need it anymore but forgets to tell that to the OS. Afterwards it just allocates new memory space. It never cleans up its mess.
Hard to say which component this might be. I would do the same procedure that you described above but on each run through I’d deactivate exactly one of the plugins, probably starting with the ones that use libraries.
Well, the culprit was OPUS, they released a recent update (1.3.8) that fixes the infinite increase in memory usage of the player, i’ve just updated it and tested the project, its using 15gb of ram and no increments at all, its working as it should now, what a relief, thank you all who participated and gave options to fix this problem, it was a sampler problem and not a cubase problem.
Sorry to bother you all if i knew that was a sampler problem i would have checked with the eastwest support.
Cubase for the win !
Have a great weekend