@John_Dahl could you by any chance upload a few dumps somewhere (5 to 10… or more if you have many, they might hold different info) and PM me the link?
Kernelbase crashes can occur to to a variety of reasons and without further analysis they might be runtime crashes, device creation crashes and anything in between.
The only common denominator I see is the use of OpenGL (as far as I know, all of the plugs you listed use it), but it’s a bit early to say anything specific.
Thank you!
@JuergenP @Fabio_B @KT66 @KT66 @OLiZ @nickas
I’ve sent the same link to Fabio in PM - but if anyone else is interested to investigate the crashes are available in this zip file through WeTransfer
Huge thanks to all of you. I really appreciate the engagement you all show to help me out.
I agree with what you’re saying here! Which is a bit disheartening haha.
Something deeper is causing it - I got these Kernelbase.dll crashes a few times with my old Dell as well, which points to an issue within Cubase.
Hope I get to the bottom of it.
Here is the memory usage from the CPU-heaviest part of the track.
I was thinking about the slots in use part here. Just below the data showing 4800 MT/S
“Slots in use, 2 of 8”
This is basically showing me that the two 64GB RAM-units are in use?
Hello, thank you for the dumps.
I’ll have to wait to have server access to properly resolve these:
Cubase 13.0.51 64bit 2024.12.6 15.11.13.856-freezedump
Cubase 13.0.51 64bit 2024.12.6 15.43.44.903-freezedump
Cubase 13.0.51 64bit2024.12.7 15.37.17.698
Cubase 13.0.51 64bit2024.12.7 14.33.17.665
The other crashes happened in the following components (see bold).
But I’ll enter them in our system in any case, should they hold some additional info.
Cubase 13.0.51 64bit2024.12.7 13.13.12.908
Kontakt_7+0x6e10d9
0x00000004850bfd60 0x000000044d24c040
0x000000044d24bff8 0x7 0x0075007300650001
0x74006c
Cubase 13.0.51 64bit2024.12.5 14.42.21.881 (vcruntime140!__RTDynamicCast+141)
KERNELBASE!RaiseException+0x8a
VCRUNTIME140!_CxxThrowException+0x97
VCRUNTIME140!__RTDynamicCast+0x141
Bus_Processor_3085b0000+0x5baa54
0x00000003965d9660 0x0000013800000161
Cubase 13.0.51 64bit2024.12.6 15.31.03.347 (vcruntime140!__RTDynamicCast+141)
KERNELBASE!RaiseException+0x8a
VCRUNTIME140!_CxxThrowException+0x97
VCRUNTIME140!__RTDynamicCast+0x141
Weiss_EQ1+0x63b8c4
0x000000038fc448e0 0x000000db000002b8
Cubase 13.0.51 64bit2024.12.13 8.05.55.688 (vcruntime140!__RTDynamicCast+141)
KERNELBASE!RaiseException+0x8a
VCRUNTIME140!_CxxThrowException+0x97
VCRUNTIME140!__RTDynamicCast+0x141
Tube_Tech_Equalizers_mk_II+0x5a20a4
0x00000004c4b04570 0x0000010300000246
Cubase 13.0.51 64bit2024.12.13 16.17.33.018 (vcruntime140!__RTDynamicCast+141)
KERNELBASE!RaiseException+0x8a
VCRUNTIME140!_CxxThrowException+0x97
VCRUNTIME140!__RTDynamicCast+0x141
Weiss_EQ1+0x63b8c4
0x0000000697e80890 0x0000007c000003c1
Cubase 13.0.51 64bit2024.12.13 16.20.04.969 (vcruntime140!__RTDynamicCast+141)
KERNELBASE!RaiseException+0x8a
VCRUNTIME140!_CxxThrowException+0x97
VCRUNTIME140!__RTDynamicCast+0x141
Weiss_Compressor_Limiter+0x60de64
0x000000015a679050 0x000001280000022f
[Edit: typo]
Thank you very much, Fabio! Very eager to hear more from you on this.
Have you tried unticking the Use OpenGL option for Softube plugs (from any plug but it’s a global setting)
Sure, if the memory is installed, the operating system will use it.
My comment about memory was just a sidebar. This is not something that’s contributing to any of the problems you’re currently experiencing.
@Fabio_B is the guy who’s on the right track and will hopefully lead you to a solution.
Given where the failures are in the dumps, I think @Grim 's suggestion is a good one to try also.
Ah! I’ll try it right away.
Do you reckon it’s software issues within Cubase that causes that to be an actual solution? I can’t swallow the idea that I need a stronger graphics card than my current one for production software.
Thanks for chiming in 
@KT66 > "Sure, if the memory is installed, the operating system will use it.
My comment about memory was just a sidebar. This is not something that’s contributing to any of the problems you’re currently experiencing."
For sure! Looking forward to hearing more from Fabio!
No, it’s a softube issue that seems to cause all kinds of problems on many systems on all DAWs. Stronger gfx has no bearing on this.
Ah gotcha! Hence their option to disable it when installing the plugins. Of course…
I’m using C13 on W11-24H2. I have a few annomalies and higher-than-normal cpu% but this helped my sessions when offline (as I often am; being up-to-date with all Windows security). I turn off “Real Time Protection” and have noticed my cpu% run lower. YMMV.
Project is now unplayable at 512 samples of latency. We’ve run stress-tests throughout the entire compute for 5 hours with Dell prosupport and we are finding no hardware issues.
The “big bad project” is 289 audio channels (60% of them are empty, 100% rendered audio).
It’s no more than 60 active plugins and most are stuff that are CPU-friendly.
There are no active instrument tracks at all.
I mean…
The Xeon W7 costs around $2500 on its own, which is more expensive than my entire previous computer.
The CPU-usage has yet to pass 22% even when the entire projects is completely unplayable due to ASIO spikes, again, at a buffer size of 512.
Hmm, my floor looks like a good place to cry on.
A xeon wouldn’t be my first choice for audio. And any dell would be my last choice for audio 
Anyhow…for performance problems the usual first steps
I got some guidance from with people having extremely solid results with lesser Xeon’s than this one (and I truly asked around and explained to the tech-departments at both Dell & HP what my needs were)
And the one’s with the bad results were with older Xeon’s with lesser “juice”.
Interesting benchmark which put me towards the Xeon.
(see attached image )
Ah, nonetheless, there shouldn’t be this level of problems. 
I loaded one instant of Neural DSP in an empty project, and at 1024 ms, the actual sound from the guitar was pure asio spikes (hit me up in dm if you want to see that spectacle lol)
Graphics is a AMD Radeon™ Pro W6400, 4 GB GDDR6,
Edit:
Will check latencymon!
Have you run the MMCSS fix and set it to maximum threads?
It’s something I do now as a matter of course.
Get rid of Norton , use window defender and set it NOT to scan your Audio projects folder and also I set it not to scan my Plugins folder and anything steinberg.
You could download Reaper and quickly set up the same project with the same plugins and see how things work so you can count out hardware issues that way.
M
Dell has requested to speak with Steinberg now to get to the bottom of this. Interesting to see the outcome there. Dell is confirming the workstation is functioning like expected. (but we’ll see about that).
Haven’t heard about MMCSS actually, would you like to expand just a bit on that?
MMCSS means Multi Media Class Scheduler Service, here is the description from MS:
here an article about possible issues in Cubendo and the app to raise the limitation:
@John_Dahl I see Fabio has linked.
I found that despite showing no errors using the MMCSS fix did wonders for my machine. No idea why, part of it was it somehow helped me be able to use windows RT midi for the first time and everything worked , but it generally made my new Cubuase 13 at the time system work without crashes, and has continued to do so . I had to re run the MMCSS.exe when I updated to C14 and windows 24H2 recently.
I can see no downside in running the fix so i do it as a matter of course now.
M
@Norbury_Brook @KT66 @Grim @nickas @Fabio_B @OLiZ
@JuergenP @janosmolnar777 @T20MAN
Big update.
First of all, amazing feedback from this forum. This was my first post and the level of engagement and tips were great. I appreciate everyone who chimed in. 
@Fabio_B has been a huge help, he is worthy of both beer and praise! (if I didn’t live in Stockholm I’d be handing over a case of ale’s.)
So… Dell narrowed the issues down to hardware malfunction within the motherboard and processor. They are sending out an on-site engineer to replace them both.
They think the faulty hardware have caused software problems as well - so they thought’d a clean replacement would be the easiest and best solution for me.
And honestly, I give props to Dell as well! For me their ProSupport is 5/5 every time they’re needed.
I don’t know how long it would’ve taken me to get to this point without all the help.
I’ll be updating with the new hardware in place. Hopefully it’ll live up to my expectations this time:)
@John_Dahl that’ s great news …well it’ not, but it is…
Good to know that pro support from Dell is exatly what it should be
Good luck with your new machine and I hope it gives you many trouble free years of Cubase use.
I’ve been using C14 now everyday in the studio since it’s release and it’s been faultless for me on my 9950x -RME-UFX III- windows 11 24H2 machine.
M
