Cubase 15.0.20 Crashing when unmuting / unsoloing MIDI tracks with external synths as the output

Cubase
,
1

I’ve been running into an issue where sometimes unmuting, unsoloing, or soloing a muted MIDI track can cause Cubase to crash / become unstable.

Essentially once it becomes unstable though, I’ve just considered it crashed since everything locks up and all I can really do is just save the project, re-open it and go from there. The project file is fine, it’s just a very frustrating problem to run into.

I’ve not been able to produce it consistently, it just seems to happen after having the project open for some time. It however has seemed to be consistent enough to become a problem while working on projects.

The only thing that I’ve been able to tie them all together with is the fact it happens when i try to either solo a muted track, or unsolo a track. I’m not entirely sure what the crash cause is and I’ve not been able to get it to happen regularly.

I have 5 total crash dumps from the release of the latest update, 3 of which are from today.

Here are the crash dumps:
Cubase 15.0.20 64bit2026.4.7 18.38.56.516.dmp (1.1 MB)
Cubase 15.0.20 64bit2026.4.9 15.58.55.338.dmp (1.1 MB)
Cubase 15.0.20 64bit2026.4.12 16.38.15.008.dmp (1018.1 KB)
Cubase 15.0.20 64bit2026.4.12 16.56.04.278.dmp (998.8 KB)
Cubase 15.0.20 64bit2026.4.12 19.51.13.419.dmp (949.9 KB)

In terms of specs that I have, I’m on Windows 11 64bit 25H2 26200.8037, and running Cubase 15.0.20 Build 226.
I’ve got a MOTU M4 Audio Interface, and the midi ports being used are going through Windows MIDI & are my Yamaha MU2000EX (with the Yamaha USB MIDI Driver) and my MOTU MIDI Express 128

Cheers

2

@Martin.Jirsak
The first report indicates a crash in the file d2d1.dll while it is inquiring for the used DPI. Seems to have been called from Cubase.exe.

The last four reports look rather similiar with a good long stacks. All crashes occur in Cubase.exe.

Martin,
can you forward the reports?

3

If the DPI/Resolution of the monitor matters, then it’d be worth noting that my main monitor is 2560x1440 @ 240Hz with scaling at 125%, and my second monitor is 1920x1080 @ 144Hz with scaling at 100%

I’ve ran into a few other small issues with it at this size before but not enough to warrant a bug report since it doesn’t make Cubase unusable.

Hope this info is helpful

Also, Thanks for helping me understand the crash dumps since I had no idea what I was looking for, or even looking at when I tried to take a peak at 'em haha

4

If Martin is not responding within the next couple of days, please issue a support ticket, linking to this topic. This way the support department can forward the crashes to the development team.

5

Seems to still be an issue even after the latest update (Cubase 15 just crashed on me again), so I’ll go ahead and send the info their way.

Cheers