I’ve been having some issues with cubase freezing during saves(I’m working on Windows 10, and Cubase 11), and when I try to force quit the program when using Task Manager, it never usually works, and I have to do a hard shut down. The problem with the hard shut downs is that they sometimes cause damage to the disk when this happens. I already spoke to tech support, and they say Cubase 11 is no longer supported so they can’t be of much help. And so I guess the next question is, if I upgrade to Cubase 14 from 11, will my current Cubase 11 projects play? Any help is appreciated. I have a dump file, but it won’t let me attach links…not sure what to do about that.
Hi and welcome,
Yes, all your previous Cubase projects will play in C14 (you might need to re-enable Vst2 support in the plugin manager). You might also need to update some of your plugins to their newest version.
I find it rather suspicious that you cannot even kill Cubase via the Task manager, I’ve never experienced that.
Have you tried starting Cubase in safe mode and see if that helps (Start Cubase in Safe mode / Temporarily disable preferences).
Does this happen with every project or might there be some problematic plugin involved? You could try updating your plugins to their newest version and see whether that helps.
(I think you can only attach links after a couple of posts here)
Ah I see. I’ll do some more posts and see if I can drop in the link. And yep I’ve updated my plugins just to make sure they’re up to date. I did run Cubase in safe mode, and it saved okay, but because it was in safe mode, I wasn’t connected to VEPro etc, so I couldn’t really do any work. The freezing save seems to happen after I’ve been running the project for a little while. It will usually save the first few times, which is odd. I will say though, that when I opened the dump file, it didn’t really point to any particular plugin that I could see, it just said “Cubase 11”. I’ll try and repost the dump file
So is there no real way to see what’s going on with a freeze/hang?
I’ve tried disabling the plugins/safe mode before, and while it works(as in the project opens), I really can’t test the system since it disables everything in VEPro as well, so all I can do is just sit there. It usually does the weird freeze/hang thing after I’ve been working for a little while(10-30 mins), regardless of the project.
Well, there are two scenarios for safe mode, one with preferences disable (which temporarily disables the current program preferences, e.g. some window setting etc), and the additional option to disable all third party plugins (which is usually helpful if the program crashes in a plugin while opening a project). Seems like you tried the latter one. What about the first one?
It might of course be that the hang is exactly caused by a plugin. Does the hang happen with all your projects? What is a common denominator of all those projects? VEPro? Could be that exactly this plugin is a problem.
You wrote that you have to do a “hard shutdown”… does that mean that you really reset the computer via the reset button? Or do you restart Windows?
It would usually do it in any project that I had worked in for around 10-15 minutes(not in safe mode, and with all plugins/preferences working). I had disabled plugins preferences before, and it started up fine, but I couldn’t really work in it and recreate the problem because it basically disabled my entire project. And in terms of hard shut downs, I usually have to reset the computer, as in, shut it down completely. BUT…I have an update…
I bit the bullet and bought Cubase 14 hoping that it would fix this problem, and it has! Normally I wouldn’t do an update while working on multiple projects, but in this case, it had to be done.
Things are working mostly smooth, but now my Arturia Keylab keyboard lost some of it’s functionality for some reason. I used to be able to right click on any knob in my Kontakt/VEPro and “learn automation”, twist any knob on my MIDI keyboard, and it would just work. Now, my MIDI keyboard has lost functionality in the regard. Do you have any suggestions as to why this has happened?
Cubase 14 is now freezing. As you mentioned in your previous post, fese, VEPro is one common denominator, but the VEPro server project usually doesn’t freeze up, it’s always Cubase. When Cubase freezes, I disconnect VEPro from Cubase to prevent corruption of the VEPro server project, since I usually have to do a hard shut down when Cubase freezes.
Imho you should be able to kill Cubase via the windows task manager. If that doesn’t work and you really need to hard reset your system (that means that not even a windows reboot works?), there is something fishy going on with your system. Hard to tell from here, though…
Some ideas to narrow it down:
disconnecting all peripherals from your system that you don’t absolutely need.
you seem to rely very much on VEpro, but just for a test, create a project without that, loading all libraries directly and see if you can recreate the freeze.
Okay this is great food for thought. I have a lot of extra drives(one is my backup drive) connected to my computer, and I didn’t realize this could affect the performance so drastically considering my computer is at least somewhat capable(i9-10850k, 128 gigs of RAM, all SSD drives, etc.).
When I run the test I’ll make sure to get a crash dump when/if it freezes and report back. Thanks for the help so far
Okay, it was working for a day, and then started freezing again. I tried disconnecting all of the extra controllers and drives from my system to no avail. It seems like it eventually locks up windows as well, and I have to resort to doing a hard reboot.
I also tried to create a dump file, but I keep getting the response: “procdump64 is not recognized as an internal or external command, operable program or batch file.” I’ll attach a link to my old dump file i was trying to upload earlier:
procdump64 is a separate tool provided by Microsoft that you need to install (see the link I provided above).
Your link requires people to be logged in to google, would be better if you provided one without that.
If eventually your Windows locks up completely, this is most likely no longer a Cubase-only problem, Cubase alone cannot do that.
Btw, how would you suggest I go about testing my system to find the problem? I used CrystalDiskInfo to check all my drives, and they appear to be in good health. I also used Memtest86 to check my RAM, and passed the test seamlessly. This seems like the worst possible scenario, because there’s no clear-cut obvious answer.
The crashdump doesn’t show any clear issue, but there are several threads of the VPro where those seem to be waiting for a network reply (in my interpretation):
VEPro plugin, as far as I know, communicates with the VEPro server via network (even if locally). Maybe there is something wrong there, do you have some VPN software installed, e.g.?
As I already suggested, I would create a project completely without VEPro, and see if you can replicated the behavior. If not, it definitely has to do with VEPro, and at least you have isolated the issue and maybe could check with VE for support. If the problem persists, I am out of ideas, tbh. But I would wager a guess that it is VEPro.
I think you’re onto something here. You’ve been a huge help so far, and I want to thank you once again.
I did some testing/updating over the past few days. I figured there might be some software issues, so I did a ton of updates(including VEPro).
I then started working in one of my projects, making sure not to save(with VEPro connected), since that’s where the mayhem happens. What I do for saves is I disconnect VEPro from Cubase, and THEN save Cubase. This I think goes to what you were saying before - when Cubase isn’t connected to VEPro, it saves fine.
I had been working for a few hours(basically a record at the point), and decided to disconnect and save again, but when I went back to connect the instances in Cubase, I couldn’t find them. They basically disappeared(for around 30 mins). And then out of nowhere, I checked again, and there were all my instances available again in Cubase.
My guess is that, before when I was trying to save(with Cubase instances connected), Cubase couldn’t find the VEPro server instances, and so it would just hang into oblivion. I guess the question is, why did the server instances randomly disappear, and what do you suggest I test from here to nail down why this is happening?
This dump is from a real crash, a null pointer read in Cubase itself. But in that case Cubase wouldn’t hang, it would simply crash completely. I am not sure if or how this has something to do with your original problem, seems like a different one.
The problem with VEPro is imho not a Cubase problem. My guess from your description is that the following happens: You save the project, Cubase asks every plugin instance for their current state. the VEPro plugins try to communicate with the server, but for some reason don’t receive an answer and hang indefinetely, as does Cubase.
I would try to ask VEPro support if they have any ideas.
