Hi, cubase shuts down itself after about an hour without any alert. There is no crash file. It works stable until shut down itself. Same problem occurred on Cubase 12 and Cubase 12.0.10 V.R versions. That problem never occurred before on studio one, cubase 11, pro tools.

Does anyone have a suggestion to fix this issue?

 

Last edited: Apr 19, 2022

You have explained by yourself.... Here

 

Are you sure the V.R version is causing this issue?

 

You have asked for possible solution, so I gave it one of them.... Maybe VR Activation manager causes that... Software itself is all okay, since I use "legit" version and not from Team VR, and I am just fine all the time.
SO other possibility is not the game, or maybe some 3rd party VST causes that, but most likely is Team VR Activation Manager....

 

It suddenly disappears completely without any alert. I've never seen any software suddenly disappear while running.This is not normal also it is confidence breaking.

Is there anyone using Cubase V.R version and having the same problem?

 

Last edited: Apr 20, 2022

First of all why are you using VR Cubase when R2R Cubase is way better?
1st problem is that you are using VR Cubase, then might be that something is making your Activation Manager to fail on license check, and that turns of Cubase without any alert.
So that problem can be just on your system, and maybe few of them, because all of that depends from programs you have installed on the system, and that problem is maybe just on your machine....
Do not search for solution for something that is broken from the very beginning and it is not possible to get fixed.
Instead , do not ignore my friendly advice because that is not polite of you, I am talking for your own good, and go with R2R and forget about VR and these problems....

 

1.) Try to run it as administrator.
It seems to be some kind of “hang on on close” maybe related to preferences or some plug in.

2.) I’ve had this for a while now, with C11 and also 12. Culprit is some Waveshell*.dll, meaning some Waves plugins (which I rarely use anyway, but have in some projects).
Have a look at the Windows Event log after you close Cubase, in “Application logs” (dunno if it’s called like that in english Windows) and search for the error entry. Sometimes it says in which module (aka dll) cubase crashed.

3.) I am also having this issue. Cubase actually does seem to close cleanly (I even checked last night to make sure there wasn’t still an instance running in Task Manager – I’m on Windows 10, fully updated, but I got the same message on startup today). I hadn’t paid attention to the details on previous startups, but I did capture the screen today:


capture1117×547 32 KB

In this case it is specifically saying it terminated with an error while executing a fille named Freeze, but I have no clue what that is, nor whether that was also what was referenced in the other cases.

The associated event log entry has an Event ID of 1000, and the following details:

(Sorry, I deleted the event log info because I just realized that, while that was the most recent Cubase error in Event Log, the time stamp was actually earlier than could be possible for this latest occurrence of the issue. There was no event log entry referencing Cubase, nor any that reference “freeze”, from when I closed Cubase last night, or perhaps early this morning.)

I am usually hitting the button that says to send the log files to Steinberg, though I may have forgotten this time due to documenting the screen, but it returns to working control so quickly that I’m skeptical it could actually have uploaded anything.

One more note with respect to the potential Waves association mentioned above: I do use Waves plugins, and I have had their Ocean Way Nashville Nx plugin in my Control Room inserts, but disabled, when closing Cubase Pro 12 due to doing a fair amount of mixing on headphones late at night. One thing I’d noted in Cubase 11 and earlier was that, if I attempted to close Cubase right after closing my project, and one of the Waves Nx plugins was active (I also have CLA Nx and Abbey Road Studio 3), the odds of Cubase hanging on closing, and needing to be killed from Task Manager, were reasonably high.

I’d since gotten into the practice of waiting a while to close Cubase after having closed my project, specifically waiting until the red color is available on the windows Close button for Cubase before trying to close it, and that seems to have made that issue either go away or at least appear extremely infrequently. And, on any occasion when it did hang, Cubase was always shown in Task Manager as not responding. I’ve continued the waiting practice with Cubase 12, and I specifically checked after last night’s session ended to make sure Cubase had disappeared from Task Manager after closing it, so it at least is not showing as being hung in with Cubase 12 – i.e. it is a different symptom than I’d been having in Cubase 11 when Cubase visibly did hang.

READ MORE:
https://forums.steinberg.net/t/cuba...nated-with-an-error-on-each-shutdown/770710/2

 

In case it might help anyone else seeing this problem, here’s an update on it on my system. It’s still too early to proclaim, “mission accomplished,” or that I’ve found the definitive catalyst for this issue, but some new findings from yesterday and this morning strongly suggest it does relate to Waves Nx plugins (I’ve been specifically using the Ocean Way Nashville one with Cubase 12 thus far).

I use the Waves Nx plugins (not only Ocean Way Nashville, but also Abbey Road Studio 3, and CLA Nx at various times) as a Control Room insert when mixing in the evening due to needing to use headphones instead of my monitors. Because I’d been working on mixes almost exclusively in C12, I was just leaving the plugin in the Control Room slot, just disabling it when it wasn’t needed (and usually also at the end of my sessions). In Cubase 11, having used the Nx plugins in a session seemingly increased the odds of a hang on exit, where C11 would need to be killed from Task Manager. However, in recent months, that problem was rare, perhaps partly due to Waves 13 allowing to avoid the extra head tracking window that was always there, whether you needed it or not, in earlier Waves versions, and partly because I was paying close attention to closing my project first, then waiting a while (specifically until I could hover over the Windows close button and see it turn red) to close Cubase itself.

With C12, with maybe one or two exceptions, I have not seen Cubase hang on exit and need to be killed with Task Manager in this scenario. However, I’d get the crash message on startup. Until yesterday, I hadn’t looked at the crash dump files, but I decided to do that yesterday and noticed I had 18 of them for less than a week’s use of C12, versus only 15 for Cubase 9.5, 10, 10.5, and 11 combined! I also looked at the time stamps on those files and noticed they were not from when I closed Cubase but from the start of Cubase sessions.

Since I haven’t been mixing the last few days, this gave me the idea to remove Ocean Way Nashville from my Control Room, close my project, exit Cubase, and restart C12 to see what happened. I still got the crash message starting the next time, but now I was starting this new session without the Nx plugin in Control Room. At the end of my day’s session, I tried restarting Cubase after exiting. This time no crash message. Also Cubase started this morning with no crash message.

As I mentioned above, it’s too early proclaim this information to be definitive, but it is sure seeming like closing a C12 session in which this Nx plugin (and probably any of the Nx plugins) was in, whether it was used or not during the session, may be the catalyst for these crash messages on startup. Thus, if you are having this problem regularly, it would be worth noting if you are using one of the Nx plugins in your session, and trying to see if you do a session entirely without it, if C12 starts up normally the next time.

If this it, I sure hope Steinberg and Waves can figure out why this happens and get it resolved as the C12 behavior is decidedly worse than the behavior in earlier Cubase releases.

https://forums.steinberg.net/t/cuba...ated-with-an-error-on-each-shutdown/770710/16

 

I haven't heard anything concrete from anyone that the r2r version works better. I use V.R because the installation process is very easy. There is no other particular reason.

 

Not every user gives good tips some tips are just wrong ! The V.R Version is O.K !

Hello @dogu19, try to read the text I posted. There are probably some Waves plugins that are buggy.

 

The culprit could be Waves plugins. The last time it shut itself down, waves plugins were active but it turned off many times, I don't know if waves plugins are the only culprit. It doesn't create any crash logs but starts with a suggestion to run with safe mode. It doesn't appear in event viewer. The possibility of a sudden shutdown in the middle of work is really annoying.

 

For now, turn off all the Waves. Then write if it still crashes ! We'll try to isolate the problem.

 

Which version of Waves are you using? If it's V13, I won't try to install it after uninstalling V12.

 

Before you install the new Waves, I would test Cubase to see if it still crashes, because if it crashes again, it wasn't Waves.

Install the latest R2R version: Waves - Complete v2022.03.13 Incl Emulator - 18.03.2022 - R2R

 

Before disabling plugin after plugin, run Windows Event Viewer and take a look at the administrative events.

To start it, go to start menu and type Eevent - it should show up immediatly.
You could also hit the Windows Key + R, then type eventvwr.msc and hit enter.

Now browse through the application errors until you find one that contains Cubase12.exe.
Click on it and read the informations below. Normally it should show what caused the crash,
maybe a faulty module/plugin, maybe something else.

 

Compared to Team R2R, O.K is not good enough!
Why your advice is better than mine is?
He didint mentioned Waves plugins, so why do you mention that or have I missed something?
Did you read and initial post?
He said Cubase just quits without any alert, not becase if Waves plugins... OMG!

That was happening with Cubase 10.5 cracked and more often with Cubase 11, due to bad crack while licence check/call...
So, therefore is no need to give any error, program just quit and that is all.
Suddenly and without any log file, or autosave progress of the project.
If you wanna to discuss about something just try to understand why is that happening!
You dont need to make me a ignorant, i gave him a proper advice to solve all problems...

I ve had simiral problem when i initially installed VR Cubase, then replaced with "legit R2R crack" and that happened when i updated Halion Sonic SE to latest version.
Cubase didn't even boot, end crashed immediately, and do you know why that, because, TEAM VR BURRIED CRACK FOR HALIONSONIC SO when i was about to clean it and install R2R version i have not done a proper clean up. So yes, dear mr BEAT, it is about license problem and nothing else.
Once i have back HalionSonic to v3.4. All worked fine because it had dedicated license on elicencer....

Because i have maybe little more knowlege about R2R crack i have tottaly right to comment and to say what is actually happening...

It is about VR bad crack and eventualy i will reveal the truth about R2R crack once Nuendo 12 and Wavelab 12 is released...

For now you too can live under the rock and keep guessing the problem!
IT IS A BAD CRACK AS FUCK! GO R2R, but you have to do deep clean up!

 

Last edited: Apr 20, 2022

PRESS CTRL + SHIFT + ALT key then launch Cubase,by yourself, and it will give you window with options to run safe mode, to temporarily disable all plugins, to reset Cubase settings to factory, etc and at end to find and open ERROR LOG/DUMP FILES from Cubase....
Try disable all plugins, but again, GO R2R bro and you will not have dat problems any more.

When there is the problem with 3rd party plugin, in most times Cubase will load project with faulty plugin, and then will freeze...
Due to faulty plugin it wont boot up.
Due to faulty licence, crack, it will, quit, not classic freeze and crash, but quit, just like you described!

Yes, i know, my advices always sucks.... ;)

 

Last edited: Apr 20, 2022

That's not true... Advices are like pills doctors give to their patient/Customers... Sometimes it helps and sometimes it don't.

 

I dunno man, where is the problem and why to make all that fuss without need, when that guy can simply go with R2R and have problems solved, but people are giving "pills" to him to keep VR, and compromise system even more, like R2R have not said how bad crack is that.
That are not my words, but R2R, who have almost 11k release, and now they are talking about Waves... Please, please... Just stop...
This makes me sad... But one thing that make it even more intresting is that those advices come from user i believed are credible enough and know what is good and what not... But not, everyone is jerking of on that VR uses legit installer and nothing modifies... No, nothing, but screwing your system.. Nothing more....

 

I think OP is more interested in using VR release because of simplicity of installation process... We can't make anyone choose what we like even if it's the right thing or the wrong... We can give our opinion to whom it may concern and just let that person decide... And on forum like these or even chat groups of our friends there is always a chaos and we need to choose the right words to say otherwise we could be labeled as roasted or offended.. As Eminem said in one of his song:
"I guess words are a M****F*****, they can be great
Or they can degrade, or even worse, they can teach hate"
So just chill and let OP decide! You have done great and enough...
Peace and love to all