Cubase 13 crashing while using time warp/free warp

Is anyone else having this issue? I’m having to edit Drums in 12 because it keeps crashing. It isn’t giving me a crash log/dump to submit.

I will add it; whether Phase-Coherent is turned on or off doesn’t matter.

1 Like

Hi Jason,

I’m glad I found this post, I was beginning to feel like I was the only one.
Yes, I’m having the same problem plus a couple more related issues.

It appears that I can’t add a link to my post on the subject (or I don’t know how) but the title is:
Major Problems with Grouped, Phase-Coherant AudioWarp in Cubase Pro 13 if you wish to search it.

Not sure if it helps but I have added a vote to your post to see if it pushes it up the rankings.


1 Like


Are you on Mac or Windows, please?

Windows 11. Everything is updated.


Could you please use Microsoft ProcDump to force to create a dmp file?

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.

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

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

  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 a similar service, please.

I have the same problem. I reported it here some time ago:


Crash in this area suppose to be fixed in the next maintenance update.

Today I had a reply from Steinberg Tech Support and it seems to be working for me now on my Mac.

Here’s a link to my post where I put their reply…

[quote=“Rozza_uk, post:8, topic:893080”]
Today I had a reply from Steinberg Tech Support and it seems to be working for me now on my Mac.[/quote]

I am having the same issue where using the warp tool suddenly will close out the Cubase 13 project without notice. Any changes will be lost up till the last save. It happens at any time whether I’m using the warp tool for several minutes or a just couple of minutes. I thought maybe I was double clicking the mouse causing the crash, but even being careful it was still closing out. This problem I am having is while working on projects that were started on Cubase Pro 12. I am curios to try or a project created in CB13 pro.

What is interesting is, if I click on the search track function in CB13 my Mac will crash every time, with the same disappearing Cubase project, on projects created with CB12 but not with projects created with CB13.

So yeah, thanks for sharing your experience. It sounds like it may help me as well and I’m going to give it a try. I agree, it seems like getting in the habit of creating a new preferences folder is good practice. Something I always never give much thought about.

Soundngin - I have never used the track search function before (!!!), but I have just checked and it seems fine for me, I am using new prefs files though. Hopefully this works for you too.

Like you, all my crashing projects originated in Cubase 12.

I did get a quick reply from Tech Support when I asked why trying another hard drive might help. I’m now fairly certain this was not the problem for me (I use APFS) but here’s what they had to say…

Concerning of the hard drive, the problem is still being investigated. It seems there are some troubles when audio is exported directly to exFAT-formatted disks.
This seems to be the case with macOS 14 in particular. Was it your case?

If your hard drive is not exFAT-formatted, it probably was a preference’s conflict.