Cubase 13.0.30 freezing constantly - PLEASE HELP!

Hey there,
Since upgrading to C13 have had regular/constant freezes, as in daily. Here’s the latest dmp file if anyone would be so kind as to take a look and hopefully offer some advice and ideally a solution…
Pro built Composer rig, i9 128GIG RAM etc Running VEP7 as local server
Sessions are usually just midi tracks, minimal and no weird plugins. Previously was on Cubase 10 - never had this issue, driving me insane!
Cubase 13.0.30 64bit 2024.5.24 (1.6 MB)
Any help would be most greatly appreciated
Thanks in advance

Hi and welcome to the forum,

When does it freeze? What task do you do, when it freezes, please?

Hi Martin,
Nothing specific at all. It’s even frozen once with no session open on the hub page
Usually happens every 24-48 hours apart, often while have been away for a break and done nothing so unfortunately there’s no specific action I can correlate it to - it’s a mystery!


Could you please attach more of your freeze dump files to see, of there is any pattern?

Thanks Martin
I’ll send a few over in separate replies (as am limited to 2 attachments only
Cubase 13.0.30 64bit 2024.5.19 (2.9 MB)
Cubase 13.0.30 64bit 2024.5.23 (1.3 MB)

Cubase 13.0.30 64bit 2024.5.14 (1.9 MB)
Cubase 13.0.30 64bit 2024.5.15 (2.2 MB)

Cubase 13.0.30 64bit 2024.5.11 (1.7 MB)
Cubase 13.0.30 64bit 2024.5.14 (1.9 MB)

Cubase 13.0.30 64bit 2024.5.7 (1.7 MB)
Cubase 13.0.30 64bit 2024.5.8 (1.8 MB)


Reported to Steinberg. Thank you.

There is one NI Kontakt crash, but the rest is in Cubase. What Audio Device do you use, please?

Audio device is RME RayDAT pci express card

I think Kontakt is waiting for some event from Cubase here, the last stack trace doesn’t even have Cubase in it.

@Paul_Di_Stefano can you please try to remove Kontakt from your project and see if this avoids the freeze? Also make sure there is no instance of Kontakt running anymore, when you try this (by looking at the Task Manager).


In most of the freezes, Cubase’s engine is waiting for something. But it’s not clear, for what is it waiting.

Therefore I sould like to ask @Paul_Di_Stefano, if you could please enable the Usage Logeing in the Preferences > General. Then attach the *.log file linked to the *.dmp file (the same time-stamp), please.

Do you notice these freezes when moving your mouse? do you also get audio dropouts? Will the system freeze if you launch another app in the background?

THanks for everyone’s comments. To clarify there are typically no Kontakt instances in Cubase (except for the odd occasional - these are hosted in VEP7 and also critical to the work so need to be abe to use it
I’ve enabled Usage Logging and will post both this and dmp file when next freeze occurs
There’s no corrrelation with moving a mouse
No never get drop-outs
No the system doesn’t freeze when other application is launched in background
Thanks again

I Only ask this because i have seen with some desktops where the system interrupt priority for all devices connected are either set to undefined or all set to high. This causes all sorts of problems when running intense apps such as Cubase.

@Muzik4Life thanks for your input, appreciated…the system has be pro built & configured…
True to form & like clockwork (every 24 hours or so) another freeze whilst AFK
Have attached dmp and log
Cubase 13.0.30 64bit 2024.5.25 (1.8 MB)
@JuergenP I tried to attach the .json session file log from the (hidden) usagelogger folder which was generated but the forum platform is not letting me upload it as it is not an authorised file type… There was no other file created in the CrashDumps folder.
Please advise if I should be looking somewhere different for the log file you are requesting
Thanks again


Please, send a link via Dropbox or similar service. It’s critical to have it, otherwice we don’t know more than before. Thank you.

Please give this a try. Its possible the freeze could be down to MSI ( Message Signal Interrupts) not being ordered to meet your work needs. For example, every time you install your GPU drivers your system will resort to using Line Based Interrupts on your GPU. Changing back to MSI improves your latency a great deal. You will also find devices like your nic running at a high priority level, when working with a DAW this should not have such a high priority.

All the changes mentioned in that post are reversable and total time will take you 3-5MINS to execute.

All the best.

@Martin.Jirsak please find .json file link to dropbox as requested

Please advise if any issues accesssing
Thanks again

Really appreciate the assistance & your suggestions
The machine is a professionally built, pressure tested and specially configured for audio with a customised/locked down version of windows 10 by one of the most experienced specialist DAW builders who has many many clients who are professional composers and need rock solid system stability …latency is super low - it’s a beast of a machine…any system adjustments are implemented by the builder and so will pass these details/thoughts on for them to consider (as I’m not comfortable changing anything deep like this without their advice)…but thanks for the input…will be interesting ro see what Martin says with the log file I linked