Please help! I upgraded to Cubase 13. 15 minutes into my project and boom, it just stops. this crap just keeps happening. Cubase 12 works just fine. should i wait on a update. Im not sure where this code is that Steinburg ask for after a crash. I be having to use cntl alt delete, and just end the program. I think my computer is powerful enough.
windows 11
intel 13th gen i9
32 gig ram
4 ssd drives and 1 hard drive. = over 1000 gigs of space.
nvidia Geforce rtx 3060 ti
Isn’t there an Optimise tick box in the Studio audio setup , i can’t work out if it’s there or not for 13th gen and newer . Just below Steinbergs Power management
Have you setup the RTX properly :
Open RTX control panel , choose 3d , change to program tag and add Cubase :
Programs Cubase : preferred max power
Vertical Sync FAST ?
Have setup a power plan for EVERYTHING never to sleep on your computer ?
Thank you for responding. It actually just freezes. The music keeps playing but i can not do anything. All the lights get stuck on the cubase software. None of my transport controls work on my external devices to stop the music from playing. After i end task and restart it has a grey screen that says cubase did not shut down properly.
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.
Im not sure what to do. Everytime I left click produm, it runs a cmd promt screen real fast in the background then disappears. I tried typing prodump in the command promt i pulled up manually,( as seen in photo) And that is the message i get.
So i will now run cubase 13 and see if it collects the data. After it freezes
Im not sure if this is the correct place to make these changes your refering to. I did add cubase to the list. Please let me know if i should change it to fast.
Update: Im not sure if its due to the graphics card adjustment That Highly-controversial pointed out but my cubase 13 has been running strong for over a hour. If it freezes again I will update. Thank you
One reason I found (and the same was not the case with V12) is problems with connected devices like the audio interface or or midi remote devices. Sometimes Cubase just stops taking any input, then it responds again when I reconnect my Novation MK3 device. I also observed that in rare cases a dialogue in the back (the pool window in my case) would block Cubase, and I needed to select and close that window (i.e. hovering over the cubase icon in the taskbar and selecting that window first). Sometimes however, Cubase just crashed with or without error message, i.e. when I am using the Halion 7 sample editor.
Overall, V13.20 has been the least stable version for me in a long time, but that may just be an unlucky combination of hardware, plugins and devices (I also got a new machine with V13 and switched from Windows 10 to 11, so I can not safely blame Cubase).
When I start Cubase, I can also see a “GE Force Experience” message from my Nvidia card, which is new, but I took it as a positive thing - but not sure.
There can be multiple reasons why your Cubase 13 freezes, and in many cases this is not due to Cubase itself. This needs to be investigated case by case to understand and solve the root cause behind it. If you’re lucky Cubase has already generated a freeze dump on your computer in Documents/Steinberg/Crashdumps otherwise you will have to follow the instructions here above:
Hello. Same problem here. Working perfectly on Cubase 12, since the upgrade to 13, crashes, freezes. Not a single time it closes without crashing, everytime i start Cubase the Safe Mode window pops up.
Did a clean windows instal, all the software, all updated drivers.
In the Cubase crashdumps folder just have two files. Cubase 13.0.21 64bit 2024.2.24 2.04.09.000-freezedump.dmp (2.0 MB) Cubase 13.0.21 64bit2024.2.23 19.23.05.616.dmp (2.3 MB)
In Windows crashdumps folder have some more
Running Windows 11 Pro 23H2 22631.3155.
Asus ZenBook Pro Duo UX581GV
Intel(R) Core™ i9-9980HK CPU @ 2.40GHz 2.40 GHz
32,0 GB
Samsung SSD 980 PRO 2TB
NVIDIA GeForce RTX2060
Clearly Cubase 13 is in beta release lol. Public beta, without mention of that! This is why I always wait a while before upgrading. Usually by .5 versions things are more stable.