do you get any dmp files in your crash files folder? does it happen with all projects or just some?
No dump files. It just kinda freezes. Seems to happen on every project but not regularly. I usually reboot the machine and try again. It typically works then.
If it is always on loading a project, it might of course be a rogue plugin. I would suggest starting Cubase in safe mode
But select “disable third party plugins” instead of “disable preferences” (you can do that, too, if it turns out not to be a plugin).
Thank you, Pete. I did not know that.
Just ran into the same problem as above: C15 working fine all day and suddenly not responding anymore. FWIW: I was changing an output of a midi instrument from VE Pro (Synchron instrument) when it happened. PC explorer became (partly) unresponsive as well e.g. I can’t type anything in the searchfield in the Taskbar anymore.
Working on pc: W11, 64GB of RAM, i7-12700k, MSI Z790-P motherboard, all software on fast SSD’s.
Dmp file is in the attachment, I hope you can find something useful in it.
Cubase 15.0.6 64bit 2026.1.13 11.18.22.388-freezedump.dmp (1.7 MB)
# Child-SP RetAddr Call Site
00 00000000`00149b68 00007ffc`fc01944a ntdll!NtWaitForSingleObject+0x14
01 00000000`00149b70 00007ffc`fc01b8e9 mswsock!SockWaitForSingleObject+0x15a
02 00000000`00149c00 00007ffc`fe67f77c mswsock!WSPRecv+0x619
03 00000000`00149ce0 00007ffc`6cc6b200 ws2_32!recv+0x16c
04 00000000`00149d80 00000000`00000000 Vienna_Ensemble_Pro_x64+0x57b200
so Vienna Ensemble Pro would be the problem
Hmm, that would be a problem, this whole template is built around VE Pro… 
I’m running the latest version of VE Pro, I also have some music in templates without it, but this one is with it and is a quiet important one (long scene in movie).
D*mn, have to look into how to fix this
I think several users report this plugin as problematic. I guess contact the vendor, I do not use this instrument
Will do this. Thanks for your swift replies!
Is VEP allowed through your firewall?
The text from the dump above indicates that it’s waiting on the socket. That could mean it’s blocked, or you have other network issues. Ensure it’s a wired connection and shows up as private/trusted, not public, on both PCs.
Pete
Microsoft
Well, it appears that it’s not VE Pro causing the problem: I’m running a project now without any VE pro instances and the same thing happens again. Really frustrating to run into this issue. Here’s the dump file again.
If anyone knows a solution, please let me know 
Cubase 15.0.10 64bit 2026.2.6 12.15.24.871-freezedump.dmp (2.7 MB)
# Child-SP RetAddr Call Site
00 00000000`0015e6b8 00007ffb`5746af5f ntdll!NtWaitForAlertByThreadId+0x14
01 00000000`0015e6c0 00007ffb`5746c5ff ntdll!RtlpWaitOnCriticalSection+0x58f
02 00000000`0015e7c0 00007ffb`5746d872 ntdll!RtlpEnterCriticalSectionContended+0x1ef
03 00000000`0015e840 00000001`433ea526 ntdll!RtlEnterCriticalSection+0xf2
04 00000000`0015e880 00000000`4d697608 Cubase15+0x33ea526
05 00000000`0015e888 00000001`476c71c0 0x4d697608
06 00000000`0015e890 00000000`00000000 Cubase15+0x76c71c0
I have no idea what it is, but this is what the dmp file says. I guess the language is kinda the same as the last one with something trying to access something
Thanks for looking into it.
This is all abacadabra to me, the only thing I (obviously) recognize is Cubase. What critical process it is the system is saying it wants to enter, I have no idea.
A Critical Section is just a way to lock some code so that two threads cannot access it at the same time.
Steinberg would need to debug the issue so they can see what instructions the Cubase15+offset pointers point to. You should report as a bug and tag the thread appropriately.
Pete
Microsoft
For what it’s worth, I’m experiencing very similar behaviour. I’ve just recently added hardware to my set up and after 15 mins or so, the whole system grinds to a halt. It’s like something gets screwed up with MIDI processing somewhere. It happened just now when I switched MIDI inputs. It doesn’t recover until a restart. Audio Processing is fine, buffer is fine, CPU is fine.
The type and brand of hardware you are using would be helpful information here.
Pete
Microsoft
Weirdly, after I wrote this I got a BSOD (never had one in Windows 11), something about an IRQ - I didn’t catch it all. I’m thinking now it might be a USB issue, as I have two hubs and various things connected - I’m going to try and put the simpler devices on the hubs and the more intensive devices directly on the mobo.
Do you have the memory.dmp available from the BSOD? It’s usually in your Windows directory. You can upload it to a sharing service and post here or PM me a link and I will look to see if it’s the known issue with the MIDI ACX driver, or something else.
There’s no guarantee this is the cause (I’d need to check the dmp), but there’s one issue with the driver where if you plug in a device which immediately starts sending clock or other messages, it can sometimes cause a bugchk. The remedy is to move the device (if a MIDI 1.0 device) from usbmidi2-acx to the old driver (Generic USB Audio) in Device Manager.
The only other item of question on there is Overbridge. Most customers are having no issues with it, but a few have come to me with issues with Overbridge when there’s also something like the Montage connected. Haven’t yet tracked down whatever issue may exist there.
Pete
Microsoft