Crashes in Cubase 12 pro and no response from Steinberg support

Hi, I did not have this problem until 12. When I close a project, Cubase freezes and the only way out is to ‘end task’ in windows task manager and restart Cubase. Really frustrating and affects workflow hugely. Should I roll back to 11? Will support ever respond to the ticket? Is support ok? I’m worried for them as they’ve not responded at all!! Any advice is appreciated.

1 Like

Hi and welcome to the forum,

Generate a DMP file and share it via Dropbox or similar service, please.

Use Microsoft ProcDump utility to generate a DMP file, please.

  1. Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your harddisk.

  2. Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)

  3. 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.

  4. 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).

  5. Launch procdump64 via Command Prompt:
    Cubase 12:
    procdump64 -e -h -t Cubase12

Nuendo 11:
procdump64 -e -h -t Nuendo11

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.

  1. 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 your help. I really appreciate it. I’ll do this now

I have no idea if it’s related, but I am seeing the same thing in Cubase 12 on macOS. I’ve reported it to folks here so hopefully that will be enough information for Steinberg to fix the problem. TBH though, I’ve seen this going back at least to Cubase 10.5, if not earlier.

1 Like


Could you link to your post, please?

Here’s the message but I had some private follow ups where I provided a traceback using these instructions.

1 Like