Issue 1: Frequent Crashes
I’ve experienced several crashes with these (and more)
Cubase 13.exe as the main cause
Kernelbase.dll
Softube Plugins
VirtualMixRack
I have no clue what’s going on.
My station is brand new, and this behavior began almost immediately after setup.
Issue 2: Severe Performance Degradation
Today’s session I encountered a beautifully unique issue while opening a project I’ve worked on several times on this system. Such a delight to have such odd laggy occurrences in a computer for 7k.
Laggy/Slow Behavior: The project opened, but the interface and actions are extremely slow. Pressing “Play” results in no response—meters show no activity, and there’s no output. ASIO Performance Normal: The ASIO meter indicates no CPU spikes or overload. System Check: All external matters are OK as far as I’m concerned.
Preferences: Nothing new, nothing special here.
Interface and Monitors: Works like a charm
Anti-Virus: Disabled to rule out interference.
More Context:
This issue occurred with the project in its original, unfrozen state. It was working perfectly during the previous session on the same new computer.
All plugins are legitimate and properly installed.
I will upload crash reports soon; a previous attempt was flagged as spam for including too many details.
Hello,
Try disabling anything that is related to virtualization in the bios.
Also Intel Eist
And C1 state
In the bios for the power its better to chose Use typical current instead of idle (power supply)
Disable anything that can be server related ( in the bios)
In windows go in control panel
Power option choose performance.
There’s not a ton of dual Xeon users on here, but here’s someone else on the Nuendo forum with a rig similar to yours and having at least one of the same problems (Kernelbase).
You might want to ping them and ask if they found a way around the problem.
I understand there is a problem with version 13 and 14 Cubase and Nuendo, with core counts over 32 on xeon (dual core - in my case but not sure if it’s high core counts ingeneral). I am led to believe that a fix will be forthcoming in an update.
My workaround has been to derate my system from 36 cores back to 32 cores using the BIOS - windows processor affiliation doesn’t seem to help.
Also, This is “playing back” - laggy and most importantly. Not a single sound.
Second attempt at starting up the project. Yesterday it worked normally after one restart.
No, you are on Windows 11 24H2. If you are not used to read dump files and Windows internals this is confusing, but the internal name is still “Windows 10 Build 26100” and this build number tells what the user will see outside.
Yeah I’m not well-versed in reading these. Thanks for clearing it up.
I kind of solved the issue! Or it seems like it, at least.
So I removed an AMD-driver / software, reinstalled the drivers to the SSL-interface, re-installed Cubase, turned off any virtualization in BIOS.
Tried it now and it works great. (will be updating here tomorrow and next-week in case the issues reoccurs. It worked quite well a few days last round before it started messing about again. I don’t feel across the river just yet.). I wouldn’t call it "128GB RAM-great"though. @nickas@KT66@OLiZ
Glad to hear you’ve got the thing running well for the moment, at least.
Your 128 GB of RAM is only going to contribute to performance if Cubase is using significant quantities of memory, though. A Cubase instance using 30 GB is going to run just as well on a 64 GB machine as it will on 128 GB.
How big is the memory footprint of your typical projects?
Usually quite large. The track I’m writing is a 7,5 minute song with both electronic & real instruments - active channels are roughly 369. (but I’ve rendered down pretty much everything to audio)
I am very constrained using 3rd party plugins as I’m mixing with the mindset of “less is more”.
There’s perhaps 3 instances of Kontakt running. I mean, sure, 369 channels is a little hefty - but I’m using offline processing quite a lot and rendering thing both for creative purposes and for CPU. (Shouldn’t have to care about the CPU with this new setup, in my opinion).
I turned the machine on today - same thing is happening with the playback. I’ve restarted it twice without luck.
This is frustrating…
However the CPU can’t be the problem here since I ran this project yesterday with 128 samples of latency and recorded live guitar with Neural DSP, without a single mishap.
Edit:
Memory footprint right before the new computer arrived was around 30GB.
That was in its most streamlined state since it literally slaughtered my previous Dell.
I’m guessing the amount of memory usage will climb a bit in the upcoming sessions. The less need I have to relentlessly render down instrument track the more memory it’ll end up using.
All in all, I got headroom and it doesn’t behave like CPU-issues.
EDIT:::
I uninstalled Norton all together and restarted - working again.
Hmm (Norton’s protection services were already disabled though. Perhaps something was getting blocked anyway?)
Norton is just another layer on top of windows security without actually improving system protection. Ive installed virus’s on purpose to try get some of my old programs back and both norton and windows just watched it go passed then had a go at me for my clean version of absynth. Its Beyond a joke now.
did you install any plugins? I got a few free plugins today and had issues after. I suspect alot of these free plugins contain malicious code . Meanwhile Steinberg keeps a close eye on them.
I got three Kernelbase crashes in a row- all in a separate mastering session and funnily enough when accidently double-clicking on any Weiss plugin I was working on. (Softtube)
A few things… that’s a lot of plugins but, in and of themselves, they shouldn’t be causing any problem. Norton, on the other hand, is a blight on DAW systems. Removing it completely is the best way to go.
You can post some of your dumps here and some of us will have a look. Kernelbase errors can be difficult to diagnose though, as it’s generally not Kernelbase that’s actually failing.
Although you’re getting crashes when opening Weiss plugins, I suspect it’s a red herring. We have the full set of Weiss plugins here and use them regularly without incident (along with various other Softube plugins).
I have a feeling that you have a call to Steinberg support on the horizon…
