Recording vocals yesterday, screen went mad and crashed cubase. Kept most of vocals, realised I still had buffer on 128, so might have been that. Saved and closed. Opened pc today, said unexpected close down, open back up. Not a sign of recorded vocals. Managed to find them in audio project folder and re inserted.
Any ideas why. PC barely measures any stress on cpu
Core i9. 64gig ram 2tb ssd
Please upload one or two crash dumps here.
Sorry
How do I do that?
When Cubase crashes it produces so called crash dump files, with the extension .dmp.
These files contain information about the reason for the crash, you can find them in your Documents folder (I assume you are on Windows from your CPU description) and there under Steinberg → CrashDumps.
Thankyou
I shall do that tomorrow
Hi
Here are 3 of the most recent crash dumps
Cubase 15.0.21 64bit 2026.6.6 11.29.38.042-freezedump.dmp (721 KB)
Cubase 15.0.21 64bit 2026.6.6 14.09.41.378-freezedump.dmp (2.07 MB)
Cubase 15.0.21 64bit 2026.6.5 19.49.31.578-freezedump.dmp (2.08 MB)
I see the MIDI client in there.
Do you have any inMusic devices (AKAI, Rane, m-audio, etc.) attached?
Pete
Microsoft
I have m audio oxygen plus an Alesis QS8 with a focusrite scarlett souncard.
Midi controllers are plugged in through a powered USB hub. I do get regular intermittent disconnection from the m audio incidentally.
The QS8 doesn’t have USB, AFAIK, so I assume you are connecting it to something else over DIN?
If you unplug or power down or otherwise disconnect the inMusic (m-audio, in this case) devices, assuming they are using inMusic drivers, they will cause the MIDI stack to lock up. They can only be shut down or disconnected when not in use by an app. If you have intermittent disconnection, that could cause the driver to hang. (Not sure if this is cause or effect here in your case).
This is an issue with their driver. We’ve been able to work around the other issue with the driver which is where it hangs when we close it. That fix completed rolling out at the end of May for anyone who is up to date with Windows Updates.
The best solution, if the device supports it, is to uninstall the inMusic driver and just use our in-box driver for the Oxygen. I believe the Oxygen is class-compliant and so doesn’t need a separate driver.
Pete
Microsoft
Hi Pete
Could you explain inmusic driver and in box driver, and the steps I need to go through to implement the changes that you suggest
Thankyou
Dave P
Full instructions for uninstalling vendor drivers is on the MIDI Discord server Windows MIDI / Audio . Just read the full pinned post in #start-here
Pete
Microsoft
Hi
I have now got the Microsoft driver for my Oxygen 49, but the dropouts have become even more frequent.
As soon as I turn the keyboard off and then on again it reconnects within a few seconds, but I lose all the fader cc messages that I have set up, but retain the basic stop/Start/record buttons
Is it still crashing? If so, can you provide an updated crash dump?
Pete
Microsoft
Hi @feardbace,
since nobody seems to have asked you this before:
did you already try different USB cables?
The one that you’re currently using - or one of your hub’s USB A jacks - might’ve gotten worn off.
Growing mechanical tolerances and - hopefully this isn’t the case - partially broken cables can lead to intermittent loss of an otherwise working USB connection. Just a thought in between.
Best wishes,
Markus
Hi
Attached is a zip with the last 6 crash dumps. Hope this assists
Thankyou for your help
cd.zip (1.36 MB)
Hi Markus
I replaced the usb cable to the hub, also I went direct in to the PC and it still disconnects
TX
Hi @feardbace,
sorry to hear.
did you also try to connect the controller without the hub, if that’s possible?
The reason why I’m asking: sometimes, a combination between a device’s USB controller and a specific vendor’s hub (chipset) won’t work together reliably. This happens rarely, but nevertheless should also be checked.
Best,
Markus
From a quick scan, those crashes look like the types of crashes I would expect for the inMusic driver “hang on close” issue. This is a bit surprising because we fixed that bug in April. But if you are using an inMusic driver, and you have a faulty connection, that would cause it to “surprise remove” when in use, which will trigger the part of the inMusic driver bug we can’t work around.
Can you post an image of the “Sound, video and game controllers” section of Device Manager? (Right-click the Windows logo on your task bar, and then choose “Device manager”
Once I see what is listed, I’ll ask for a few more screenshots. Thanks.
Pete
Microsoft
Thanks. I’m actually interested in the first tab “General” on the Oxygen 49 properties, thanks.
I assume the generic USB MIDI Interface is what you use to connect to the QS8.
Pete
Microsoft
