Cubase crashes due to GPU Drivers

Cubase
41

We are not the only ones experiencing crashes with NVidia drivers and we are also not the only ones experiencing the error code 887a0005. We are investigating where the fault lies, meanwhile we are doing our best to make our software stable on every user’s machine case by case.
If you cannot run with another GPU on your computer then you should try the following:

  1. Install all windows updates
  2. Update your graphics driver
  3. If available try to disable HAGs. Go to Display Settings / Graphic Settings. Click the change graphic default settings under Default Settings and turn off HAGs Scheduling.

Cheers,
Armand

1 Like
42

I can see the point of starting again, but should i really need to do this if just one program has issues, and CB have stated there are issue with the driver for my card anyway?
It seems like I’d spend a lot of time re building my OS, only to still have a known issue anyway.
Ive said a few times but ive run loads of tests on the system, there are no issues being flagged anywhere. Definitely no malware, and ive refreshed all my drivers.
If i had a system that was unstable I’d certainly re install the OS, but its just one program, and even that isnt totally unstable some days.
Ive not had Windows 7 (or anything below 10) on this PC so its not that.

It seems CB doesnt like any other program running… I can cause it to crash by opening Firefox or Edge and going to Dropbox in these browsers. Not every time, but a majority of the time. It seems like CB has a grip on on these system while its open, and i didnt think this is good programming. No other program i own does this. I can do 4K video editing, work with huge raw files in Photoshop, with loads of layers, all without a glitch.

I appreciate not everyone has these issues, but i see it as if everything other than one program is working, then I’m not fooling myself that my system is fine, it is fine, its the application thats not as compatible as it should be.

43

I wouldn’t recommend you rebuild your entire computer for this. Just to be clear. :slight_smile:

44

I’d only rebuild the PC if there was evidence it would help. It seems like it might be a short term fix, which would take a long time to do.
I can live with a crash every now and then, although I’m not happy about it.

45

I don’t think there would. This forum moves very slowly, and judging by the posts on FB groups a lot of people have no faith in getting official help.

I did build the PC myself.

46

To give everyone more insight.

So far in all the similar crashes we’ve received, 99% of them happened with NVidia drivers. We do not experience such instability with other manufacturers. The balance of evidence that this lies on NVidia rather than on us specifically is I believe quite in our favor.

So why does this happen mostly with Cubase only? And not with other DAWs or games?
Well first, as I said, assuming NVidia drivers are perfect on any platform and with any application is a bit of an approximation here.
That being said. Cubase uses some graphics technologies that might not be too widely spread in other DAWs. There’s a reason for this and it is meant to be benefitial to the user’s experience. This codeflow seems to be not handled properly by NVidia drivers for hybrid desktop apps like Cubase (unlike proper games). We cannot bypass this technology so easily. This theory has been vaguely confirmed by NVidia a year ago. They also said they will consider fixing it. Meanwhile you have to take into account that Cubase is nothing to NVidia. We aren’t Ubisoft, Unreal and so on. So the priority here seems to be rather low on their side.

1 Like
47

Maybe email them using a @yamaha.com email?

1 Like
48

Ahah brilliant! But probably Yamaha isn’t much more relevant than Cubase to NVidia.

49

So the net result is that it might not be beneficial to the end-user experience, if the end user uses the most common graphic card around.

So whose priority should NVidia compatibility be, then?

I understand your explanations but from a broader perspective all this is either confusing or just plain revolting.

If your graphic code has documented incompatibilities with a major graphics vendor, it should be a high priority for you to fix those on your side, as you are totally aware that they probably won’t, for reasons outlined by you above.

50

If I remember rightly I replied in another thread, Are you still running Cubase “as admin”?

The fact that you’ve had to run like that previously suggests that there’s something deeper within your OS or File permissions that is the underlying issue here.

In windows go to to Settings > System > Display > Graphics Settings.

Then once in there you browse for the Cubase .exe that you’re running and set it to be integrated gfx.

Of course, is it possible that your Motherboard doesn’t have integrated gpu? If it hasn’t then this option is not possible for you.

1 Like
51

99% of similar crashes is a high enough number to warrant some kind of action. Even if you can’t find a way to fix, there’s ways to inform.

Why not notify the user when loading Cubase that it is recommended to disable the Nvidia GPU for Cubase.exe - if enabled? Such a simple check to carry out. And only needs a simple graphic/link to support page on ‘how’ to do it.

See, what’s being missed here are the silent majority who either walk away, or lose faith in Cubase as a product. Yet it could be very easily addressed with some common sense rather than finger pointing.

2 Likes
52

Should I avoid NVidia in my next compute build?

I was also potentially looking at getting the ASUS Zenbook Pro Duo, which has a NVidiaGeforce RTX 3070 GPU…

Is it all NVidia cards with these problems or just older ones?

It seems to me a lot of the problematic cards were released on Windows 7 just before Windows 10 release, and then had Windows 10 drivers released later.

53

Thanks for the link but ive already done this.
I do have onboard graphics, and have used it in the past, totally bypassing my Nvida card. I even used the HDMI out from thr motherboard. I still had issues, although not the one reported in this thread. But still, i had graphic issues with no Nvidia involvement.
My comment on asking where the setting was was in relation to the ‘right click on the .exe’ post, which isnt there, and i cant see why its been posted twice now. It doesn’t help at all.

Im in agreement with digitallysane. I’m not convinced about all this ‘it’s Nvidia’s fault’. Surely the code for CB was written to work with their drivers from the start. Did Nvidia change something? Is it a case of Steinberg refuse to re write their code, and Nvidia refuse to re write theirs? I can understand the latter, as pointed out, Steinberg are a relatively small company so Nvidia wont pander to them, but Steinberg have an obligation to ensure that their program does work with hardware that is very common amongst PC users. Why was it written knowing it wouldn’t work 100% in the first place?

‘We cannot bypass this technology so easy’. Ok, its not easy, but you need to do it to give your user base a better experience. Easier said then done i agree, but if its been going on for so long, and only now we hear about, something isnt right.

They need to put a note or disclaimer on their website IMO. Selling software that has a known issue with certain industry standard graphics card should be pointed out. I can imagine if it were other, bigger companies, a class action law suit could be on the cards. But then I suppose if they did that, with the majority of PC owners using Nvidia cards they might not sell so many copies of CB.

The fact that 99% of crashes are with Nvidia cards is not a surprise, as these cards dominate the market. There will naturally be more of these cards in a random selection IMO. The more worrying fact is the other 1%. This seems to show its not exclusive to Nvidia, although i like the 1% odds better.
.
Yes, we did talk about Admin mode before, and no, I’m not using it in this mode. I have to with older projects as i was getting strange issues with the waveform display, but now I’m back to user mode for new projects, but still with the following issue. The reason i was using Admin mode was POS would not close when i use User mode. Even with stand alone’ she like Halion, or Wavlab etc. All had to be run in Admin to ensure POS shut down when it was not in use. It would close eventually, but if i was switching applications I’d have to force quit it from Task manager.

Still, with all this said, CB is an amazing program, and the Dev’s have done an amazing job coming up with this. It just needs a bit more and we are good. There are obviously loads of bugs that arent GPU related that also need fixing though.

54

I will not reply to all the claims but I’m afraid there lies a couple of misunderstandings or things I cannot agree with. All I can say is that there’s a KB article about related issues. This is a known issue we’ve been discussing with NVidia, as a matter of fact this is popping up regularly on our radar.
I’m sorry if you feel that this is disregarded as such but I respectfully disagree about this.

1 Like
55

The most interesting part of that KB is just the brief at the beginning:

A new graphics sub-system has been introduced in Cubase 9.5 that seems to show incompatibilities with certain NVIDIA graphics processing units (GPU) and driver versions.

How is a gamedev studio that’s looking into buying in some high-end post software specifically pitched to game developers, supposed to react to this?

How is a film production/post-production studio (my case) supposed to take this?

I own an animation studio, I use Houdini, Unreal Engine, Adobe CC, Resolve, Scratch and some other highly GPU-dependent apps. I have no option but using NVidia cards in my workstations.

I started getting into Cubase (which I really like) and I’m evaluating Nuendo (which I love).
Crossgrading to Nuendo seemed obvious, but you just gave me a hard pause on that.

Investing even more money (and time) into the products of a company with such an attitude suddenly looks like an irresponsible thing to do.

1 Like
56

We believe this mostly happens on entry-level GPUs. I would give it a try first with a trial.

57

I have an RTX2070 in my workstation. Not the latest and the greatest, but certainly not entry level. Studio drivers etc.
And I have the issue described here: Media Bay dog slow to open / graphics issue - Cubase - Steinberg Forums
currently in discussion with support (aka, haven’t heard anything from them in more than two weeks).
It happens in both Cubase (LE and Pro) and Nuendo.

58

Wouldn’t they still use the same drivers as the higher level cards?

I’m a bit stuck with the GPU options we talked about earlier. I know where the settings are to change the preferences to not use the Nvidia card, and thought I had it set, it few days ago, but looking at it now the only option I have is the GTX780. Both for power and performance.
My Motherboard has an intel HD4000 chipset, but it’s only usable if it’s physically connected to the monitor. Device manager says it’s on and working, but I can’t select it without using a cable. As it will only run at 1080p max it’s not much use.

59

Unfortunately that kb is out of date, as Nvidia control panel no longer controls the GPU selection for individual applications. It’s done via the Windows (10) operating system now, as part of the GPU scheduling.

It’s no wonder @Davebass5 is confused as to where they should find these options to try a fix, as this is the second method I’ve seen written which is misleading.

It’s been 4 years since C9.5 released, and still an issue for 90+% of users experiencing similar crashes. I appreciate you discussing the issue, and not wanting bashing steinberg - it’s just a feeling of disappointment reading this. :frowning:

1 Like
60

To be fair thoses crashes are relatively rare and are definitely not broadly spread. We’ve had hard times trying to find a system here where they can be easily reproduced. That does not affect 99% of our users using an NVidia card.

2 Likes