Well, sir - you’ve got a mystery on your hands! Any other questions I have would deviate from your issue, so I hesitate doing that (like “did you build it yourself” or “did some local tech outfit install Windows for you,” etc.).
For purposes of actually supporting your issue, I’m not sure what next steps you would take. Martin may be able to provide some guidance, but if the team sees that OS_VERSION and BUILDLAB_STR value, they’ll most likely push back.
LOL - I suppose I’m going to ask anyway. Do you have your original media you installed it from? I mean, did you install it yourself, etc, and what’s the likelihood of doing a nuke and pave (reformat and reinstall Win11)?
I have an iso that Windows asked me to use 9 months ago. There was an update that interfered with Cubase.
That said, in over 2 months of tech support and that of aforementioned Martin Jirsak, I’m unlikely to reinstall Windows unless convinced it’s causing Cubase problems…
Perhaps you have knowledge that they don’t have? I’m far from a Windows expert but always prioritise Cubase on this Dell Music PC,
I don’t understand this. How did “Windows” ask you to use an ISO? Where did it come from? How did you get it, and why? In my opinion, these are absolutely relevant questions that need to be addressed to get proper support. Even the original crash dumps indicate you are using the OS_VERSION: 10.0.26100.1 BUILDLAB_STR: ge_release build. To be running an old beta version of Windows, but not know it, while also providing superficial information like “I have an iso Windows asked me to use” gives the appearance that something’s not totally kosher. Again, just my opinion.
If you “borrowed a copy,” downloaded a hacked version, or beat someone up in the AV club at school and took it doesn’t make the slightest difference to me But something’s not quite right. Short of getting a verified retail copy of Win11 and reinstalling it, I don’t know what your real options are.
That’s what I’d do, but you are free to do what suits you the best. I’ll leave you with that Happy Friday.
I had 10 crashes in the last 5 days. I have sent CrashDump files to the Steinberg service dpt and I’m waiting for an answer.
I WONDER IF THE CRUSHES ONLY APPEAR ON WINDOWS, since (if I’m not mistaken) I see Apple or Mac mentioned nowhere…
This is really new to me — I started using Cubase quite some years ago. So far, crushes were really exeptional. But now, this extremely annoying. I really hope Steinberg will solve this problem, before people start doubting… I really love Cubase, but nobody needs crushes this often. It’s simply bad!
Your post doesn’t tell us anything. If you want to post one or more of your dumps and tell us what you were doing leading up to the crashes, someone might have some useful input, otherwise it’s just another aimless complaint.
Hi @Alexander_D
Can you provide more info and context, please?
I don’t want to sound rude but this is like saying: “I was riding my bike the other day and then I had a crash. It MUST be the bike.”
I f I were you and I wanted help I’d start a separate thread…
I think I’ve had Cubase 14 crash maybe twice between 2 separate MacOS systems since I’ve had it, and it was due to something with Vienna Ensemble (I think, or it was another plugin). I mean TWO TIMES total, as in “ever.”
I have a relatively complex multi-workstation studio, and have a lot going on with routing between RME and UAD, etc, so saying “Cubase 14 is really buggy” is not something I’ve experienced at all. This is why it’s important to provide context and crash dumps, otherwise there’s really no substance to the complaint.
Posted just two links… but I can posted more crash files here. But honestly, seems that it doesn’t work more…
Also search bug is so annoying for me. I posted about this so often and also saw this bug on Gregs streams. But once again - Steinberg don’t want to reproduce this bug or search the reason…
Now we are waiting Cubase 15 with the new and old bugs…
In this crash file, it was a drag and drop issue involved with the UI of a plug in. You had these in memory:
FabFilter Pro-Q 4 4.02, Pro-R 2 2.04, Pro-L 2 2.24, Saturn 2 2.11
u-he Presswerk 1.1.6
Spectrasonics Omnisphere 2.8.7c, Keyscape 1.5.2c
Xfer Serum2 2.0.20
Native Instruments Kontakt 8.5.0
Wavesfactory Spectre 1.5.6
dSONIQ Realphones 2.2.0
Three-Body SpecCraft 1.4.1
While you can say “Cubase is buggy,” and on your system you may be right, to actually solve the issue you’d have to do some explicit testing with each different plugin, one at a time. Or just pay explicit attention and identify which plugin you were working on. I’m not saying it’s NOT a Cubase component, but to arrive at that conclusion you’d need to test very thoroughly.
I can assure you that Windows tech support sent me a link to download the iso which they were confident would solve my problems.
Trying to convince you is of little priority compared to my desire to have Cubase returning to its previous stability.
I’m left pondering your suspicion given that you are having a trouble/free run. Simply because you’re not having problems you can’t be blind to the fact that others are..?
I have no idea what that means. Your crash reports indicate are using an old beta version of Windows - all of them. If you don’t want to fix that, then all I can say is good luck.
I don’t know if you are connected with Steinberg, but at least I got the impression. Anyway, I wrote that I indeed have uploaded one of the dumps.
What happens is always the same and very simple: I get this very loud buzz-tone for some 5 seconds, the program stops working and closes itself after another say 15 seconds. I can’t point my finger to something specific that I do to cause it. I don’t do anything different that what I do for so many years now.
About the “aimless complaint”: if, when somebody reports a problem, and anyone else isn’t ‘allowed’ to report the same issue, the people from Steinberg would probably think that it’s just one isolated case and wouldn’t take it serious. I’d rather say that everybody must report it, because the higher the number, I guess the more important it would be for Steinberg to work on it, and the faster the problem could get solved. Don’t you agree?
I think you misinterpreted @KT66 's post.
Ideally, a thread should concentrate on one issue alone - the OP’s issue. If others can contribute to solve the issue by reporting a similar issue that might help to shed light on the case - that’s most welcome.
Posts which are basically about letting of steam due to another unrelated issue are of little or no help in this context. It’s understandable that you want to express your frustration, of course. However, it makes much more sense to open a separate thread and to provide details and context rather than taking away the focus from the original thread. Otherwise, it’s difficult to keep track. Exactly this happened here and it’s not helping anyone.
Having said this, please open a separate thread to make it easier for others to follow and to provide help. That’s just so much better for everyone…
Cheers!
Addendum: @KT66 is a normal user just like you and me - we are all here to help each other out.
But something’s not quite right. Short of getting a verified retail copy of Win11 and reinstalling it, I don’t know what your real options are.
