10.5 crashing on opening 10.0.4 project (Windows)

Hi all,

Trying to debug what is causing Cubase 10.5 to crash on a 10.0.4 project (which always loads without issue in 10.0.4) on Windows. Anyone experiencing similar issues or who can figure more out from the attached mini crash dump? (I have a full dump saved as well, in case there is more I can investigate with WinDbg).

I’ve had the project load successfully before, so this doesn’t reproduce 100% of times, but it happens far more often than not.

(I’m separately trying to debug Soundtoys 5.3.1 VST plugins being blacklisted, but I also experienced this particular crash on project load while I still kept those plugins on the blacklist, so I don’t think that’s the cause here).

Cubase 10.5.0 (built on 14 Oct 2019)
Windows 10 Pro (version 1809, build 17763.864)
Intel Core i7-3930K 3.2 GHz, 64GB RAM

Cubase105Mini_23ac_2019-11-15_12-15-24-243_0a78.dmp (336 KB)


I’m sorry, there is literaly nothing in the STACK_TEXT:


Same here - new is that 10.0.30 crashes too.
Cubase 64bit 2019.11.18 (864 KB)
Cubase 64bit 2019.11.18 (783 KB)


Cubase 10.0.30 is outdid now. Use either current Cubase 10.0.50 or Cubase 10.5, please.

Hi, please have a look to my attached files.
The second one is from 10.5

I too have the same problem, i how ever am running 9.5.550, upgraded to 10.5

Any ideas what causes crashes?

I have attached my dump file from 10.5 crash, if it may assist.
Cubase 64bit 2019.11.18 (628 KB)

I have installed an older version of Soundtoys (Soundtoys5_5.3.0.14027_64).
Than delete all Black- and Whitelists of Cubase.
Cubase 10.5 “accept” this older version of Soundtoys - no problems anymore with this issue.

Thanks for looking, Martin. From my full dump file (which is sadly 2.5 GB), looks like the faulting instruction was from a memcpy(); not sure what the source of the invocation was, though, or how to best hunt backwards to it:

00000000`983f9fa8 00000000`10876f40 : 00000000`00000000 00000000`00000000 00000000`00000000 c02e0000`00000000 : MSVCR120!memcpy
00000000`983f9fb0 00000000`00000000 : 00000000`00000000 00000000`00000000 c02e0000`00000000 40380000`00000000 : 0x10876f40

I should note that Cubase itself is not generating a dump file in %LOCALAPPDATA%\CrashDumps\ (which makes me think the crash occurs within Cubase code and not within a VST dll module? isn’t there some type of process isolation so Cubase can handle when 3rd party code crashes?). I set WinDbg up as a postmortem debugger to load when the crash occurs, and the file I attached was the output of running a “.dump /m” command in WinDbg, with no additional options – I guess that doesn’t have enough info to be useful.

I’m quite new to WinDbg, though, so do you happen to know which options from the .dump command would give you enough information? I can output another version from the full dump and attach, if useful.

Other potentially relevant info from !analyze:

CONTEXT:  (.ecxr)
rax=0000000032d0d040 rbx=00007ffdbe3dc3c0 rcx=0000000032d0d040
rdx=000000004cf86280 rsi=000000004c95a440 rdi=00000000486ce100
rip=00007ffdbe3dc3c0 rsp=00000000983f9fa8 rbp=00000000983fa120
 r8=0000000000000eb0  r9=00000000000000eb r10=00007ffd9a5c12b8
r11=000000004cf86280 r12=000000004cf86280 r13=00000000000000eb
r14=00007ffd99249440 r15=00000000000000eb
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010200
00007ffd`be3dc3c0 ??              ???
Resetting default scope

MSVCR120.dll!Unloaded+3c3c0 [f:\dd\vctools\crt\crtw32\string\amd64\memcpy.asm @ 101]
00007ffd`be3dc3c0 ??              ???

ExceptionAddress: 00007ffdbe3dc3c0 (MSVCR120!memcpy)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000008
   Parameter[1]: 00007ffdbe3dc3c0
Attempt to execute non-executable address 00007ffdbe3dc3c0


PROCESS_NAME:  Cubase10.5.exe

00007ffd`c7d2c3c0 0000            add     byte ptr [rax],al

EXECUTE_ADDRESS: 7ffdbe3dc3c0

MSVCR120.dll!Unloaded+3c3c0 [f:\dd\vctools\crt\crtw32\string\amd64\memcpy.asm @ 101]
00007ffd`be3dc3c0 ??              ???


This sounds familiar to me. Please, search the forum here. I believe, there are some articles.

Unfortunately there isn’t something like plug-in send box. Since Cubase 10.5 you can start Cubase without 3rd party plug-ins (by using Safe Start Mode). This Is helpful if you can’t start Cubase or load any project (and the loading stops at loading a channel).

Cubase 10.5 crashes when opening a 10.0.5 song. I’m on Mac Mojave 10.14.6


Could you attach the *.crash file, please?


if dumps are not written in Documents, chances are that you’ll find crash entries in the Windows Error Reporting in the System Information file, possibly reading ucrtbase.dll. Most of these crashes are actually termination commands that Cubase receives (thus exiting without generating any dump). You can use ProcDump to monitor the application and obtain a dump. I’d avoid the -h argument, it might trigger the crash too soon.

MSVCR120 is part of the MS Visual C++ Redistributable 2013, you might want to try and repair it (Programs and features or App & Features: right-click -> Modify -> Repair). There are a few VST vendors that use that library.
I don’t know the relationship, but there is also opcservices, which statically links to system ddls like ole32, kernel32 and msvcrt… so worth a try indeed.
Repairing is quick and painless, can solve post-update corruption that occurs at times… of course it could also be something else… like a library crashing a plugin that uses that redist.

If you can get info about that silent crash with ProcDump, either me or Martin will have a look. Thank you!

“Attach the crash file”

There was no crash file, everything just came to a slooooow halt. No play when I hit the space bar but maybe play for a sec ten seconds later. I’m not sure if I made this clear, but I was working in 10.5, went to open the version saved in 10.0.50, replied “yes” to activate, and tried to explain to the clients there what was happening. I just said “new version of the program, sorry about that”. Then force quit 10.5, opened 10.0.50 and kept working for hours. Lucky thing is that I didn’t lose any of my new work done in 10.5, it opened fine in 10.0.50


Sorry, in your original post you wrote it crashed, so we expected it crashed.