Cubase 14 Artist Crashing - Brand New Computer

Cubase
1

I bought a brand new computer 2 days ago, loaded Cubase 14 Artist yesterday and it crashed twice today!

I bought this computer specifically to run my music studio. The specs were deliberately chosen to prevent this from happening and Cubase was the only program running both times it shut down and reset itself, so it’s definitely the software and not the machine.

I would appreciate any help!

Thank you.
Jeff

2

@jeffreysoble
Cubase is not the only thing running.
I know what you are alluding to but there are hundreds of programs running in the background which could have contributed to the crash.

You mentioned a new computer but did not provide specs.

I am afraid you are not going to receive adequate help.
Your question is ambiguous and does not help us understand your setup so we can make specific suggestions.

Here is an example:
“I was recording an audio track at 24bits/96khz with the latency set at 256MB. I am running an RME Baby Face. My projects contain 500 tracks, including 10 VST Synth. [More details].”

Again, you need to explain the above.
Remember, too much information is a good thing when attempting to get help.

3

Hello,

I am neither a computer nor a recording expert. As I said, this computer is literally 3 days old, and the only programs that have been loaded on it in addition to what the machine came with are Cubase 14 Artist and its associated VST’s, the Line 6 HD Edit for my Pod HD500x, Analog Lab V and ITunes. Very little has been stored on the internal SSD as I’m using an external 2TB hard drive so that I don’t overload the computer’s memory and slow it down. I have not yet added any of the additional VST’s that I’ve accumulated over the years and had on my previous machine, which was a very old laptop. The new computer is a desktop tower and the specs are…

  • Intel Core I7 14th Gen 14700KF 2.5GHz Processor
  • NVIDIA GeForce RTX 4070 SUPER 12GB GDDR6X
  • 32GB DDR5-6000 RAM
  • 2TB Solid State Drive
  • Windows 11
  • 2.5GbE LAN
  • WiFi 6E
  • Bluetooth 5.3
    I’ve created only 2 projects in Cubase so far and have only loaded backing tracks for both from Karaoke-version. I did split out the individual tracks so 1 project has 8 tracks and the other has 14. I haven’t done any actual recording yet. The program’s specs are set at the default levels. As I mentioned, I understand very little about music recording/engineering/producing. I use Cubase at a very basic level, essentially for demo recording, and I seek outside help when I’m ready to produce a final product. Both times that Cubase shut down, it was the only program open (other than the background programs that automatically run when you turn the computer on) and it was just sitting, and had been for several minutes. I was not interacting with the machine at those times. I don’t know if it matters, since I haven’t attempted any recording yet, but I don’t have an interface set up yet. At the moment, the Pod HD500x is set up straight into the computer itself. The Pod does have an interface, but not 1 that you really want to use for recording. It’s much better suited for playing live.

I had the exact same blue screen error happen with Cubase 9.5 Elements, and only when running Cubase on the computer that I just replaced, but it was a very old laptop, completely obsolete, and dying. so I assumed that it had been acting that way due to the age of the machine and that it just wasn’t capable of running sophisticated programs anymore, Cubase was just too much for it. I did not expect the same thing to happen on a brand new machine that several people who understand these things better than I said was more than powerful enough to run the program without issue.

I hope that this is good enough information. If you need anything additional to be able to help me, please let me know. I’ll try to provide as much as I can.

Thank you.
Jeff

4

So, when you mentioned crash, is this a blue screen?
So, Cubase is freezing and not responding?
How is it crashing what I mean is, does it just close without warning, or does it freeze up and you have to end the program in task manager?

Your specs look solid.

5

Yes, it’s the so-called “blue screen of death”. As I mentioned it happens when I’m not interacting with the computer, but the blue screen just pops up without warning, closing Cubase, and says that the computer needs to reset then it does do that.

Thanks

Jeff

6

If you have a BlueScreen then that is usually problem with the driver. Applications such as Cubase run at a higher level in the OS. If the application crashes then the OS will just close it and continue. Application like Cubase can ask the OS to play some audio through the soundcard or draw something on the screen, and the OS passes that to the driver. If the driver crashes then the OS can’t recover from it and it results in a Bluescreen (or kernel panic on Mac)

If you run WhoCrashed then this will tell you which driver it is. Check that you are up to date. Try disconnecting USB devices or wifi to isolate the problem.

7

I am running Cubase 13 Pro and 14 Pro on a similar CPU: i7-14700K.

I would highly recommend to switch of the Efficiency cores in the BIOS, this solved a lot of problems for me.

8

BTW: I am also running a machine completely only for music purposes.
i7-14700K
64 GB RAM
Scarlett 4i4 4th gen
2x4K monitors

I would like to get rid of all the “unnecessary” processes and applications, which are not needed to run Win 11 as a basic OS for a studio machine. All these tasks consume CPU power.
Would be great, if someone could provide here input or suggestions. It would be great to have a tool checking on that…

9

Thank you for the advice everyone. I’ll try this stuff out and see what happens.

Jeff

10

If I’m not mistaken, I had to do that for Cubase to load properly but I’ll check it out.

Thanks

Jeff

11

This does not seem related to Cubase directly but most likely a driver issue.
I have a lot of Blue Screens, but they are usually on start up’s which I attribute to bad ram or related to one of my hardware drivers.

This is most likely related to your connected hardware, like your Audio or MIDI interface or some other hardware driver.

Follow @PaulWalmsley recommendation, that will be the most helpful

12

Thank you so much Paul!!! It was the driver to my Pod HD500X. I’ve updated and I think I’m good now!

Best,
Jeff

1 Like
13

Excellent – good to hear you’ve got to the bottom of the problem.