constant crashes (without error msg) after updating to 10.5.12...

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

Michael

anything in your windows event log ?

you can also manually create a .dmp file

You both are running Ryzen CPUs, so perhaps it has something to do with that. Maybe something doesn’t agree with it in 10.5.12. Just a thought.

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 have the same problem (Intel CPU). Windows Event log:

Faulting application name: Cubase10.5.exe, version: 10.5.12.123, time stamp: 0x5e43de87
Faulting module name: Keyscape.dll, version: 1.0.0.0, time stamp: 0x5ad617ba
Exception code: 0xc0000005
Fault offset: 0x00000000000f90a8
Faulting process id: 0x4ef8
Faulting application start time: 0x01d5ec18f6d27d07
Faulting application path: C:\Program Files\Steinberg\Cubase 10.5\Cubase10.5.exe
Faulting module path: C:\Program Files\Steinberg\VstPlugins\Keyscape.dll
Report Id: 13808613-ac66-4375-b842-a23b92cfd5a3
Faulting package full name: 
Faulting package-relative application ID:

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


Faulting application name: Cubase10.5.exe, version: 10.5.12.123, time stamp: 0x5e43de87
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process id: 0x3454
Faulting application start time: 0x01d5ebfe1382e891
Faulting application path: C:\Program Files\Steinberg\Cubase 10.5\Cubase10.5.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: b73b6708-6273-4c54-9dbd-e32af4021a48
Faulting package full name: 
Faulting package-relative application ID:



Fault bucket 1558849315871690218, type 5
Event Name: BEX64
Response: Not available
Cab Id: 0

Problem signature:
P1: Cubase10.5.exe
P2: 10.5.12.123
P3: 5e43de87
P4: ucrtbase.dll
P5: 10.0.18362.387
P6: 4361b720
P7: 000000000006db8e
P8: c0000409
P9: 0000000000000007
P10: 

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Cubase10.5.exe_1395f56015c7c315197338daec84e68ba1d9205_b95daa24_9d6011fb-f237-49e1-be4f-9a09f4061a29

Analysis symbol: 
Rechecking for solution: 0
Report Id: b73b6708-6273-4c54-9dbd-e32af4021a48
Report Status: 268435456
Hashed bucket: 0782e982cfb6100975a2253192e48dea
Cab Guid: 0

Crash #2: Event Viewer > Windows Logs > Application

Faulting application name: Cubase10.5.exe, version: 10.5.12.123, time stamp: 0x5e43de87
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process id: 0x1f74
Faulting application start time: 0x01d5eb764e89f754
Faulting application path: C:\Program Files\Steinberg\Cubase 10.5\Cubase10.5.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: cdc07936-3118-4a57-b6a6-ea14164aea9d
Faulting package full name: 
Faulting package-relative application ID:

Btw, I ran two checks suggested by Microsoft when above exception codes appears to check if system files/DLL’s are OK. No problems found.

  1. DISM.exe /Online /Cleanup-Image /Scanhealth - which reported “No component store corruption detected.”
  2. sfc /scannow - which reported “Windows Resource Protection did not find any integrity violations.”

quick one to try - are you using ilok ? - is it the latest driver ?

next you can generate a dmp by:

download procdump - it’s free - and doesn’t permanently install on your system so there is zero risk.

hhttps://docs.microsoft.com/en-us/sysinternals/downloads/procdump

  1. start cubase

  2. You need to open command prompt as ADMINISTRATOR and run procdump - the command is

procdump64 -e -t Cubase10.5

exit cubase and procdump should generate the dmp file.

see if that makes sense

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?
Thanks

It might be VST3 plugin related. Try disabling “suspend VST3 plugin processing” in preferences.
See:

how do you know it’s he same issue - what crash are you getting ?

I already have it disabled so that can’t be it. Thanks for the tip though.

So today I reverted back to 10.5.10 using Windows 10’s Recovery to the restore point before I updated to 10.5.12.
I have been playing intensively for an hour now without any crashes.

EDIT: Update again. I just installed 10.5.12 again. Cubase crashes within the first minute after when opening up the same plugin I used without problems just before updating…

I guess the cause can be either the new eLicenser drivers included in the 10.5.12 update or Cubase itself.

The exact same cause of crash, see below:

Faulting application name: Cubase10.5.exe, version: 10.5.12.123, time stamp: 0x5e43de87
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process id: 0x2b60
Faulting application start time: 0x01d5ecef89506fb1
Faulting application path: C:\Program Files\Steinberg\Cubase 10.5\Cubase10.5.exe
Faulting module path: C:\Windows\System32\ucrtbase.dll
Report Id: acacad98-bfa5-4a6e-8859-413c488410d5
Faulting package full name: 
Faulting package-relative application ID:

I will follow the procdump instructions next… I got a message from Steinberg.

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 :frowning: 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

Michael

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):

  1. Download the tool “procdump” from Microsoft (<500kB) at https://download.sysinternals.com/files/Procdump.zip

  2. Extract the Procdump.zip to a local folder on your hard-disk (your “Downloads” folder is fine for this, ie C:\Users<username>\Downloads\Procdump).

  3. Run Command Prompt as Administrator (Start → CMD → Right-click on Command Prompt / CMD)

  4. In the command prompt, go to the folder where you extracted Procdump.zip, using this command line:
    cd C:\Users<username>\Downloads\Procdump (please leave the CMD window open)

  5. Launch Cubase

  6. Launch procdump64.exe via Command Prompt using this command line:
    procdump64 -e -t Cubase10

  7. Procdump is now monitoring the Cubase process and will write a crash log. Please note that performing this command will probably cause Cubase to crash (at least in this case).

  8. Collect, zip and send the files to Steinberg (you should probably contact them first and explain what is wrong). Or paste the link in this thread (you can use Dropbox, Onedrive or whatever).

I was getting constant crashes from a urctbase.dll also rumoured to be a display issue surrounding AMD graphics. Anyway, Steinberg sent me a link to this site and I followed these instructions. Windows told me at the end that it had indeed fixed something, but didn’t say what. Seems to have worked so far… How to Use System File Checker in Windows | Solvusoft

I pretty annoyed with iLok right now because running the procdump isn’t possible when using plugins using iLok.

“Debugger Detected - Saturation Knob This software cannot run in the presence of debuggers”


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. :angry:

1 Like

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.

To be continued…

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.