Cubase 14.0.5 Crashes Constantly

Cubase
1

Hi all,

This is unreal. Cubase keeps on crashing like its the year 2010.
what on earth is going on??
and this is on a wav project with some vsts.

win11, Rme ufx ii, AMD Ryzen 9 3950x 16-core, all ssd inner drives, 128Ram, Nvidia 1650
unbearable!
Somebody have an answer?
Thank you
crash dmp attached HERE - CUBASE 14.0.5 dmp - Google Drive

2

I have just looked at one of the crash dumps, it fails in a plugin

image
image510Ă—286 6.53 KB

3

Thank you JuergenP

which plugin is it? I don’t have nothing on board called VCC…
can you understand what plugin it is?

thank you

4

vcc_channel and ni_release hints towards Native Instruments

Do you have anything from that company installed ?

You could try and clean them from your machine to see if the crashes dissapear :slight_smile:

Cumbersome but it might be worth the effort.

I have personally take everything NI out of my system as I find the NI system messy and buggy, that’s just me :slight_smile:

Best regards, Ole

1 Like
5

ni_release in the BUILDLAB_STR has absolutely nothing to do with Native Instruments. There are other things in the world that are abbreviated ni.

6

Well, I’m not saying that it is, just suggesting a debugging possibility.

7

A quick web search for “VCC Channel” suggests that it might be Slate Virtual Console Collection…

1 Like
8

Thank you.
I do use the Slate Digital chanel.
As for the Native Instruments, Im using a lot of their stuff (komplete 14 etc) and Steinberg support did mailed me that its buggy. Never the less tiday I was on a project that has the slate but not native and had a lot of crashes.

Thnx for the info

1 Like
9

Again, the “ni” in ni_release is not short for Native Instruments. It is short for “nickel” which is a code name for Windows 22H2.
(Windows as a service - BetaWiki)

10

I’m also having lots of crashes when using Slate VMR with Cubase 14.

I’m always getting a “EPL is corrupted” message, then Cubase crashes. It is to to with authorization issues. My iLok Manager is the latest version.

I’ve tried downgrading to VMR v.2, upgraded to v.3, the same problem still persists.

Since the OP is using AMD, and I’m using Intel, I don’t think this has to do with CPU issues.

I contacted them and it seems that iLok PACE is involved as well. I’ll keep you guys updated.