Cubase 14 constant crashes with basic operations

Cubase
24

Sorry, I don’t know the answer to that – this is not my area, and there’s only a small amount of stack information in a minidump so it doesn’t say what is going on further up the stack.

All I can say is that Analog Lab has about 26 threads running, and all of them are in a waiting state. The main thread is waiting for something, most likely the results of something in one of the other threads. Only someone from Arturia could say what it was waiting for.

Can you reproduce this with any of the stock Cubase plugins?

25

It doesn’t happen with Cubase instruments or plugins.
So far happens every time with those 3 :
Waves Electric200, Arturia Analog Lab, and IK Sampletank 4.
I think I will just plan a complete hard drive format and move on to Win 11, reinstall everything from scratch !
Cheers Paul anyways, not to worry, I manage to get my production work done, I love Cubase.

26

Hi,

Why you don’t get in touch with the plug-ins vendors/support?

27

I’d echo what Martin says – if you send the freeze dumps to Waves/Arturia/IK then they may be able to spot something.

On the other hand, a reinstallation can be a good way to fix latent problems with old plugin versions hanging around (on top of all the other background processes for things you installed and then forgot about)

28

Unsure why this thread is being hijacked by an unrelated issue, it’d be more useful to have a separate thread for that.

Anyhow, the macro is not the cause of the crashes since it also happens when I delete or disable a single track (the macro just selects all tracks in a selected folder and toggles enable/disable). There are no crashes when the target tracks are not connected to a hardware input from my interface.

30

Good bless you, a good man! I has been dying of these glitches since come to Cu14. You’ve made my life easier! Thank you so much! The only thing left to find out hot to preserve Cubase from assigning input busses automatically while creating new tracks when rendering audio, for example.

31

@Martin.Jirsak If this happens with multiple VST suppliers and comes and goes with different versions of Cubase, don’t you think that makes it a Cubase problem? I’m referring to Cubase freezing when VST is opened on 2nd monitor…

32

I insist there seems to be a problem with Cubase and some VST plugins opening on the second monitor.
Just got a complete freeze (no crashdump) when opening a Melda plugin that went on the second screen.
I forced Cubase to close. Unplugged my second monitor. Restarted the project, loaded the offending plugin, loaded fine on the first monitor.
Closed Cubase, plugged back 2nd monitor, reopened project, plugin showing fine on first monitor. Loading another one loads fine on the first monitor. But if I move it to the 2nd, close it, then reopen, then it is freeze.

So cut a long story short, I wish Steinberg engineers look into this issue.
My setup :
Win 10 64b Alienware 17 R5 Intel i9 8950 16GB RAM GeForce 1070 Focusrite 8i6 1st gen

Thanks @Martin.Jirsak

33

Hi,

Generate a DMP file and share it via Dropbox or a similar service, please.

Use the Microsoft ProcDump utility to generate a DMP file, please.

  1. Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your hard disk.

  2. Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)

  3. Navigate (in the Command Prompt) to the folder with the extracted procdump file.
    For example:
    cd C:\ Users \ \ Downloads \ Procdump
    Note: the dmp file will be written into that folder.

  4. Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behaviour (see next step).

  5. Launch procdump64 via Command Prompt:
    Cubase 14:
    procdump64 -e -h -t Cubase14

Nuendo 14:
procdump64 -e -h -t Nuendo14

The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exceptions and the option -t terminations of the application.

  1. Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.

ZIP and share the DMP file via Dropbox or a similar service, please.

34

Here is the file, made with a completely empty new project, just added one track and tried loading a Melda plugin. Opens fine if on prime monitor, but if moved to 2nd, closed then reopened, then total freeze.

And since this has happened with Melda, Arturia, Waves plugins, I do suspect there may be an issue somewhere in the Cubase framework with dual screens setup.

File :

35

Hi,

It asks me to login. Could you please share it without the login need?

36

Here is a WeTransfer link instead then :

@Martin.Jirsak

37

It’s good to see Steinberg representatives finally asking users to use Microsoft debugging tools. This is what Cubase users need for real troubleshooting support with their issues. I hope this becomes a common trend.

38

Martin is a forum moderator, not a Steinberg representative.

39

Antoine-B, I have had a similar experience with two desktop monitors running a Nvidia GeForce video card on a laptop. You didn’t say, but are you using a laptop? If you are using a laptop, does Windows lable your monitors as 1/3 - 2 -1/3? Basically, does it show you running 3 monitors (counting the laptop monitor that you don’t use) with one of the desktop monitors labeled also as ‘1/3’ because it is showing the same screen as what is displayed on your laptop?

Let me know?

40

Hi, thanks for engaging, let’s try help each other.
So yes I am using a laptop (Alienware with GeForce 1070) plugged to a Samsung widescreen monitor via HDMI.
But no it is not labeling as 1-3.
Is it the case for your setup ?
I would really suspect something is not handled well with multiple monitors as this crash happens for many plugin brands. Here is my Nvidia settings :

displays
displays824×816 58.4 KB

41

Check my reply above. Let me know your case too, hopefully we can get more info out to Steinberg this way and try solve it.
And if you didn’t see, check above as I found a way to at least work around the issue.

42

Thanks for the info. Here’s my setup and it’s different than yours, but I learned a few things here that you might want to consider.

First off, I use a Logidoc breakout box (that connects to the Laptop with a USB C connection) with 1 HDMI output and 1 DP output. (Remember that the laptop has 1 HDMI output on it and I didn’t use it.) My laptop is a 3 year old ASUS TUF 15 Gaming Laptop, running latest Win11, Intel i7 -11800H, 8 Core, 16 G ram, along with an Nvidia Ge Force RTX 4050 video card. (Note: the display screen on the Laptop boasted a refresh rate of 144hz, my desktop Dells are 60hz).

Here’s my experience. At first I connected two desktop Dell displays to the Logidoc, one connected vis HDMI, the other via DP. I did not use the laptop display although it duplicated one of the displays, whichever display I setup as the main one. This worked for about 1 year, although the DP display had some strange random sparkling snow, faint but always there. I swapped monitors and the snow followed the DP connection. Then one day there was a flickering of the DP monitor, sometimes turning off but then restarting on reboot. However eventually it turned off completely. The Logidoc was up to date.

Here’s where things get interesting. The onboard Intel video card had been asking for a driver update - but I had been avoiding it because I was (I thought?) using the GeForce video card. Why would I need to update it? But… I decided to update the Intel card… and nothing changed. I also updated my GeForce driver the next day as a new driver had been released. Nothing changed. Windows could not find the 2nd desktop display after many attempts. So, I decided to get a bit radical in my attempts to sort the problem. It had occurred to me that perhaps the Logidoc was a fail, and, after a phone call, Logitech sent me a new one, gratis. I installed it but nothing changed. At this point, following my radical leanings, I thought that perhaps a Windows Update had caused the problem? As I thought about things, I considered that if I DISABLED the Intel graphics card, and therefore the laptop was dealing with ONLY the GeForce card, things might sort themselves. So I DISABLED the Intel card. And before somebody starts saying that this was a very radical move, a mistake, know that this is exactly what I have done to my Desktop PC where I’ve run 2 monitors on an AMD Radeon Pro card without a hitch for years. However this did not bring back the 2nd desktop monitor - and - I now had the laptop and 1 monitor showing the same display. I opened the Nvidia graphics app and it confirmed what the Windows Display app showed. The 2nd monitor was invisible. I stepped away and went to bed.

The Intel video card. The HDMI output port on the Laptop.

When I woke up in the night 2 things occured to me. I should ENABLE the Intel graphics card, and then use the HDMI output on the laptop for the 2nd monitor. I made these changes and opened the Windows Display app. It shows only 2 monitors, labeled (1/3) - 2. Here, the Laptop shows the number 1/3 on the laptop and on the #1 Dell monitor and the #2 on the 2nd Dell monitor.

I know this is a long read, sorry. Q: Do you think there is any way to NOT make the laptop the MAIN display? I don’t think this is possible. The 2nd monitor can either mirror the Laptop or it can be made an extension of the Laptop screen - and I’m sure that’s what you’ve setup with your system.

BUT - looking at the Device Manager right now and my setup, here’s what I see in regards to the two desktop monitors and the Laptop monitor: the Laptop monitor is controlled by the Intel video card along with monitor #1 (fed from the USB C out of the Laptop into the Logidoc and out the Logidoc’s HDMI), hence the ‘1/3’ label which is plainly confirmed by the Device Manager - and - Monitor 2 is controlled by the Nvidia Geforce card fed from the HDMI port on the Laptop. If I open the Nvidia app, it shows only 1 monitor, not 2, not 3, and this is the #2 Dell monitor.

I’m sure this is a complicated read, sorry again, but I’m suggesting that your laptop screen is controlled by the video card installed on your MB, and your 2nd monitor is being controlled by your Nvidia card. Which is to say that there is probably something about the Nvidia card that is causing your problems. Not what you wanted to hear, but take a look in your Device Manager and confirm what drivers (Intel or Nvidia) are attached to your laptop monitor and your #2 monitor. Then open the Windows Display app and ‘identify’ your monitors, (s/b 1- 2), and then open your Nvidia app to see if it shows one or two monitors. Get back to me.

43

That was long indeed ! But I tried to look into it. First thing I switched which one is the primary monitor, same issue, Arturia, Melda plugins all crash when closed then reopened on the second monitor.
Here is a video showing the primary screen, after a few seconds you see the sound bar freezing when the plugin is reopened on the 2nd screen then Cubase goes frozen,

44

@Martin.Jirsak here is the dmp for the above issue shown with video capture.
Cubase 14.0.20 64bit 2025.3.29 15.15.19.478-freezedump.dmp (1.4 MB)
It’s really hard to deal with this as I get lots of crashes every day because of this dual monitor issue. Would love some help !