Cubase 15.0.30 64bit2026.8.17 15.10.50.909.dmp (2.2 MB)
There are times when this error photo multiplies at least 15 more times.
Alan Russell
Most of the time repeated crashing is caused by a plug-in.
I was having something similar happening a couple months ago. I didn’t have any expertise reading crash dumps, but used Claude to walk me through the process. Within 30 minutes I knew which VSTi needed an update.
You had exactly the same failure back in July… an access violation directly from Cubase. There are no plugins listed in the dump. What is it you’re doing on Cubase when the failure occurs? Is the failure random or does it always fail in specific circumstances?
This repeated error occurs when I’m heavily editing my orchestrations with the new score editor which in my opinion is very unstable and is highly susceptible to screen resolutions when moving around notes or highlighting them. Mayve an external graphics card is needed with more VRAM
It really costs me a lot of time with my workflow but this is how I need to work and I’m not going back-and-forth with Dorico using their available libraries I need to use the SWAM library feeling I’m closer to reality when I arrange.
Alan Russell
What Claude had to say about the two crash dumps you posted on the two threads.
Aug 10 — c0000005, rip = 0, “Attempt to execute non-executable address 0”. A call through a null function pointer, on the main thread inside DispatchMessageWorker → WndProc. The recovered chain (~45 frames) is 100% Cubase15 + user32 + ucrtbase — no plug-in, no MediaBay, no GPU driver, no MIDI. Last valid return address Cubase15+0x319403c. Without symbols that’s as far as it goes; it’s Cubase-internal.
Aug 17 — c0000005 reading address 0x38, i.e. mov rcx, qword ptr [r12+38h] with r12 = 0, faulting at Cubase15+0x31ad674. This one is diagnosable, because the callers are Microsoft code with public symbols:
Cubase15 ... message dispatch
TextShaping!ShapingGetGlyphPositions+0x47a
TextShaping!GenericEngineGetGlyphPositions+0xc1a
TextShaping!otlResourceMgr::detach+0xe8
TextShaping!CCacheSlot<COMMON_FONT_CACHE_DATA>::~CCacheSlot+0x42
TextShaping!COtlsClient::ReleaseOtlTable+0x71
DWrite!ShapingInterface::ReleaseFontTable+0x19
DWrite!FontFileReference::ReleaseFragment+0x23
Cubase15+0x46b8499 ... +0x31ad673 <- Cubase callback
** null deref **
DirectWrite is tearing down its font-table cache and calling back into Cubase’s own font-file-stream implementation (IDWriteFontFileStream::ReleaseFileFragment / custom font loader) — and Cubase’s object is already gone or partially torn down. That’s a font-loader lifetime bug, triggered during text shaping.
For the customer, that gives a genuine avenue while Steinberg looks at it:
- Check for recently installed / third-party / corrupt fonts, and remove suspicious ones.
- Try a different UI font or reset Cubase’s font & display-scaling preferences.
- Note whether the crash correlates with a particular window that renders unusual text (non-Latin track names, plug-in names, MediaBay results).
Pete
Microsoft
Thank you so much for this analysis and it’s the kind of support that is so appreciated by me and I’m sure others
Can you tell me exactly where in my cubase 15 pro preferences I should make a change and Can this be related to the new score editor window
- Try a different UI font or reset Cubase’s font & display-scaling preferences.
I’m sorry. I have no idea. You may be able to get some assistance from Steinberg given the information so far.
Pete
Microsoft
I did change the Font to Ariel and I have had no crashes so far.
1 week has past and NO crashes since I changed the font in another posting
Well I spoke To Early latest Crash Dump I was working very heavily with the Score Editor
Not sure of the cause on that one, but totally different error. It’s trying to execute memory marked as data from within the Cubase UI thread. No font APIs involved.
Also, no MIDI involved, which is something I always check for.
Pete
Microsoft
Thank you for your continued help maybe the excessive new score editing involvement that I was doing yesterday caused it in someway maybe I should upgrade my ram from 32 to 64
If you haven’t already, I strongly recommend you open a ticket with Steinberg Support directly. You can include a link to this thread if you wish.
I have sent these Crash Dump Files Many times. Is there a direct link you might have?
Here is yesterdays Crash Dump file - This morning Cubase Crashes more frequently
Try this:
https://helpcenter.steinberg.de/hc/en-us/requests/new
You will likely need to be logged in to your My Steinberg account first.
If you mean you’ve posted them here, keep in mind these forums are user-to-user, not official Steinberg support.
Pete
Microsoft
When the screen comes up that asks if you want to use the preferences or not there’s a small window though asking me do I want to send this problem to Steinberg and they always send hit the Steinberg when it is available so instead of talking to a technician which is probably impossible I just transmit the issue to them but I expect no answer from them until the next update. I feel I’m being realistic about this because time is money my friend.
Alan Russell
Thank you very much for the direct link to get help and they sent specifically every item with the issue description I have been having with the crashes including the project that I’m currently finishing up with great difficulty. I am looking forward to there response and I have all the time in the world to help them to troubleshoot this issue
Thanks again Mlib
Alan Russell
Steinberg technicians took a look at my issue and they’re blaming the plug-in but they’re not telling me what to do except to go to safe mode. If I deactivate these plug-ins in the project I sent them how can I troubleshoot the project? The problem lies in the new score editor
Gregory Jackson (Steinberg Media Technologies GmbH)
Aug 31, 2026, 23:10 GMT+2
Hello Alan,
Thank you for your email. After reviewing your crash dump, it is pointing to several SWAM VSTs, HOFA IQ-EQ, and HOFA IQ-Reverb. I would suggest starting Cubase in safe mode and disabling all third party plugins and see if you encounter this issue with the project.
Best wishes,
Gregory
Steinberg Support