After updating to version 10.5.12, Cubase has started to crash every time I work on a project.
Every time it crashes I have been tweaking plugins by mouse, these plugins has never crashed before (today plugins from D16 Group and Soundtoys).
It crashes without giving any error message, it just silently quits… No CrashDump files are created in C:\Users\myuser\Documents\Steinberg\CrashDumps\
Are there any other logs I can look at or send to Steinberg?
And please don’t ask me to trash my preferences, I just got everything where I want it to be… I will try it after copying my preferences files.
I have a similiar behaviour here. 10.5.12 worked fine for a day or two but today it just crashes - just closes without a warning or message. Sometimes even without a session loaded. Totally puzzled what might have changed here, trying to go back to 10.5.10
I need to find the 10.5.10 update so I can downgrade, but Steinberg always deletes the older updates from both Steinberg Download Assistant AND from the website. Why!? It’s not available on ftp.steinberg.net either.
This last update, 10.5.12, is by Steinbergs own words, a hotfix which has not been through the normal testing period.
Steinberg: Why do you delete the other older updates? Where can I download Cubase_10.5.10_Update_win.exe?
I had just loaded a very small project (with Keyscape as only plugin). I opened up Studio Settings to check a thing. Then all of a sudden Cubase was history. I didn’t even touch or open the Keyscape plugin that claims to be the “faulty” part. (the very same Keyscape that in no other Cubase versions has caused any crashes…)
I also have a Report.wer file from the situation attached to this post. Report.zip (4.77 KB)
Yes, windows events log are here. But is it possible to create .dmp files even if the program just quits? Normally, you can only create .dmp files when the program hangs or freezes. If you know how to, please tell us.
From windows event logs, seems like it’s the same issue every time:
Crash #1: Event Viewer > Windows Logs > Application
I’m having the same issue and must downgrade as I get constant crashes, so I’m in desperate need of Version 10.5.11
cant find it anywhere on the website, can someone please help me with a link to this update?
I don’t have time now to learn about dmp files and crash reports, so I went back to 10.5.10 which has been working fine since. One other problem in that context was effectrix, it crashes cubase for some reason when I load a session Nevertheless this doesn’t explain why 10.5.12 crashed here even without a session loaded.
afaik there is no .11 version available, so you’d need to get .10
Steinberg representatives are reading this thread, much appreciated.
I did the procdump and Steinberg looked at dumps. Unfortunately they could not find the issue at this moment, apparently it didn’t look like it was a Cubase/elicenser issue but maybe a graphics drivers or iLok drivers (located in the “surrounding” memory space).
For me, it’s a bit surprising since 10.5.10 works fine with the same graphics drivers and software iLok drivers.
Anyways, I will do whatever it takes to help solve this issue.
I will do some tests like uninstalling iLok drivers and downgrading the AMD graphics drivers to the version recommended by Steinberg.
I really encourage everyone that experience crashes with 10.5.12 to create the .dmp files. It only takes a couple of minutes to do in Windows.
These are the steps I got from Steinberg (but modified by me to be easier in this certain case):
WTF iLok, why do they even bother with debugger detection when hackers obviously have ways around it. Just a pain in the a** right now to find the issue. Elicenser doesn’t do this and it’s obviously much more secure than iLok.
So now I uninstalled the the iLok/Pace manager/drivers and tried to open Cubase again which wasn’t possible due to the iLok plugins throwing too many error messages so Cubase hanged itself.
After that, I downloaded the latest iLok Manager directly from ilok.com and installed it.
I spent 10 minutes playing around in Cubase 10.5.12 WITHOUT crashes, so far.
I have to spend a couple of more hours to be sure, but it’s too late now.
More than a few mentions on Google related to display drivers causing a fault here. Some recommend deleting your display driver and letting it come up in default mode - than reinstall the driver from scratch.