Constant crashes after recording midi in Cubase 15

Windows 10. Latest version of Cubase 15.

This problem arose today out of nowhere, working in a template that i’ve been using without issues in Cubase 15 for the past 2 weeks. All evening I’ve tried to nail down if it’s down to a certain plugin or Kontakt library but to no avail. It seems to happen anyway. Sometimes after 5 minutes, sometimes after an hour. But so far always when i press spacebar to stop recording (or any other key, i tried). Playback is fine. Computer is not breaking a sweat.

I get a stop error message, then Cubase exits, i have no opportunity to save.

If i create a new project, and import all the tracks from the cursed project, it will crash at some point, too.

(I have not been able replicate this error in Cubase 14, yet. That’s not to say that it won’t happen, because it’s hard to troubleshoot when it’s this random.)

I have freshly re-installed my system 3 weeks ago and so far everything was running smooth.

I have dmp files but Windbg doesn’t seem to be able to handle them. They are large, like 500mb, but i’ve put them on dropbox Transfer - Dropbox

Thanks

What, is the instrument you play?

Is it recording MIDI data, and outputting to hardware, or are you listening to the sound of a VST Instrument, while you record.

Additionaly to @emotive inquiry about the source, can you give more precisions about the “stop error message” ? A screenshot would have been perfect, but even without it, the message content could give us hints.

1 Like

Yes, monitoring while recording, no hardware. It happens both in Kontakt as in Uviworkstation.

The library or instrument within one of those doesn’t seem to matter.

I’ll get a screenshot of the error message but it won’t help you much, it’s very vague. Just says that cubase15.exe has gotten unstable and i have to save my work (i can’t btw). Then it exits

OK, I see the type of message. If I remember well, it also points to a crash dump file, which should be located in your \Documents\Steinberg\CrashDumps folder. Any recent file related to the issue in here ?

If so, I suggest to post it/them here. I’m not competent to take a look in it, but there are several forumers here that can, and could help find the culprit(s) from it.

Meanwhile, have you tried to launch Cubase in Safe Mode, using the Disable program preferences option ?

this is from the dmp file that ive been able to open in Debugdiag. the faulting thread gives:

Faulting Thread Arg 1 Arg 2 Arg 3 Arg 4 Source ucrtbase!abort+4e 0007ffa00000003 0007ffa00000003 00000004fbfeb30 000000000000000 Cubase15+44efc1b 000000000000000 000000140000000 000000146fe9128 00000004fbfdf70 Cubase15+44efb2c 000000140000000 00000014397c202 00000014397c202 0007ffa00000000 Cubase15+44efacd 00000004fbfdec8 00000004fbfdf08 00000014397c202 000000000000001 Cubase15+56cde88 0000001478ead94 000000140000000 00000004fbfdf70 0007ffadf940e7b VCRUNTIME140!__C_specific_handler+9f [D:\a\_work\1\s\src\vctools\crt\vcruntime\src\eh\riscchandler.cpp @ 389] 000000000000000 00000004fbfe470 00000004fbfeb30 000000000000000 D:\a\_work\1\s\src\vctools\crt\vcruntime\src\eh\riscchandler.cpp @ 389 ntdll!RtlpExecuteHandlerForException+f 000000000000000 00000004fbfe470 00000004fbfeb30 000000000000000 ntdll!RtlDispatchException+244 ff0000000000000 ff0000000000000 0000001937debf0 ff0000000000000 ntdll!KiUserExceptionDispatch+2e 000000000000001 000000000000000 0000001b17c53d0 0007ffadf9347b1 Cubase15+1bc817e 0000001937debf0 00000004fbff4e8 0000001597822b0 0007ffadd83f05b Cubase15+1bc60b8 000000000000001 fc5000000000000 00000067e593e20 000000159782348 Cubase15+1bc4c7e 0000006896c62d0 0000001937debf0 00000067e5940a0 0007ffadf9347b1 Cubase15+1bc299e 0000006896c62d0 00000004fbff7b0 00000067e5940e0 0000006896c62d8 Cubase15+1bcfeaf 000000411d7d380 0000005fba99640 000000002b76ed0 000000000000000 Cubase15+1bd9c54 00000067e594020 00000000b5c1a28 000000002b76ed0 00000017c36f368 Cubase15+3426587 000000145df05a8 000000000000000 000000002b76ed0 00000000b5c1a28 Cubase15+3427b44 00000000b5c1978 00000000b5c18d0 00000000b5c1978 00000000b5c18d0 Cubase15+3426af6 00000000b5c1978 000000000000000 00000000b5c1a80 00000004c78f590 Cubase15+344d971 00000004c78f590 000000000000000 000000000000000 000000000000000 Cubase15+397c202 000000000000000 000000000000000 000000000000000 000000000000000 kernel32!BaseThreadInitThunk+14 000000000000000 000000000000000 000000000000000 000000000000000 ntdll!RtlUserThreadStart+21 000000000000000 000000000000000 000000000000000 000000000000000

sorry for the formatting. anyway, not sure if this helps anything.

i have deleted preferences and started over but to no avail in this specific project.

I have looked at your dmp file, but I cannot really work out what happens exactly, except that Cubase (as your warning message says) decided that it encountered some error and would rather raise an exception and crash “gently” than continuing. I don’t see any sign of a plugin being the culprit.

What MIDI keyboard do you use? Just for testing, do you have another one you could try? Or try another UDB/MIDI port for your keyboard. Just to see whether it might be related to corrupted MIDI data (don’t know whether Cubase might crash from that, just an idea to test)

Also, after the crash, the next start the Safe mode dialog should appear, I would click the “Send log files to Steinberg” button. You could also open a support call and point them to your crash dump.

Thanks for looking into that, appreciate it.

Indeed i concluded that it seems no plugin is the culprit. This would make sense with my earlier findings that C15 works stable and solid, leading up to this crashy project. I use a Roland A-88 and have done so for 8 years or so. I could try with another though.

On the subject of corrupted midi data, i also think in this direction. I do not really know why or how midi can get corrupted.

Thanks

Im too having that issue and it seems to be kinda related to when i have just moved the mod wheel on my keyboard. And its even more instantenous when i play the builtin pad with my midi AND i press more that one midi note (2 or more Chords on the pad) but when i click then with the mouse or virtual midi (pc keyboard) its okay. i have both cubase 14 and 15 but I didnt get the same issue in 14 though. Could you kindly test this on you system to see if this is a bug with cub 15? Thank you.

maybe related, but i can’t replicate that with the chord pad and modwheel. but it’s hard to replicate anyway, because it can be gone for an hour so it’s hard to test