Please upload the crash dump mentioned at the end of the error dialog.
Hi,
As always, please, describe the issue. When did the crash happened? Can you replicate it?
And attach the mentioned *.dmp file.
- Win: %userprofile%/Documents/Steinberg/Crash Dumps
Cubase 15.0.21 64bit2026.4.19 14.58.21.443.dmp (2.3 MB)
Martin, This has been happening randomly when I move things around in the new score editor It has also happened when I do an Audio Mixdown
Alan Russell
any thoughts?
Hi @Alan-Russell,
“my humble attempt at first aid”
I may be wrong (I’m not a prof. programmer), but let’s start:
-
are you still using older VST2 plugins, or did you remove any such older VST2 plugins recently, without emptying / renewing your Cubase user preferences?
-
the faulty module in this case seems to be Cubase15.exe itself, which crashed while trying to execute some (unknown) code at address 0x07, but which couldn’t be executed there at the given moment.
-
are you sure that your RAM has no errors (sometimes things like heap corruption can result from a faulty - or overheated- RAM chip)?
-
does this instability or crashing also happen if you temporarily use Cubase 15 only in safe mode, without any 3rd party plugins? If it does, or if it still crashes, this might point at a hardware issue, or even to some outdated OS components. You could also try a complete de-install of Cubase, including removal of your preferences folder. During re-install, no other software (except for anything absolutely necessary) should be running.
Cheers,
Markus
none of the above - Markus - thanks for your response When heavily working with the score editor, most lock ups happen.
I have a very souped up Dell tower - plenty of RAM. there was a recent firmware update - let’s take it here.
Alan Russell
Hi @Alan-Russell,
you’re welcome.
However, not sure if a mainboard’s firmware update itself can (usually) be the source of such program crashes or system freezes, this may or may not be.
Why I’d mentioned the older VSTs: some less strictly programmed VST2 plugins are said to have had the “bad habit” to occasionally write to one and the same RAM addresses multiple times, so that Cubase would no longer be able to fully control the situation. Most often this might only be a rather minor loss of control, but to ensure it’s consistency while running, Cubase would “stubbornly” report the incident to the user and take its steps to save a running project (as an additional project file version).
Did the error happen again, since we last talked? I haven’t used the Cubase 15’s score editor too often, for I’m using Dorico 6 anyway.
Best,
Markus
Hi,
The crash is in Cubase. Reported to Steinberg. Thank you.
Thank you Martin I still feel even having the latest update .21, that the new score editor when editing and deleting several notes after the highlighting is still an issue. I drag my mouse over the notes I want to delete and they don’t get highlighted if I click on a single note on another track and then go back to the other notes I wanted to delete then they get highlighted I do heavy editing with the score editor. My main computer is well equipped with the latest technology from Intel. I have lots of RAM I feel that the Steinberg team should spend more time in stabilizing the score editor for editing needs similar to mine
Alan
You are not alone. Selecting notes in the score works some times, but not always.
Same with the Display quantize. It doesn’t update properly.
I just tried a score made in CB 15 in CB 14. Everything works perfectly. So something broke in the 15 update.
@PaulWalmsley - is this one for you ?
I did have the same error- twice
Also very long time to close down Cubase, it took a long time to unload vst’s
I rolled back to 15.06- no problems till now and very fast shutting down
I just don’t like the workflow of exporting to Dorico and then coming back to cubase 15 pro There should be a greater effort on Steinberg to correct the interaction of its software with the new score editor this has been going on since cubase 13 pro.
have you also noticed that when you click on a note you could hear the note being played but if you go to another area on the stave, it’s complete silence