I’m getting random Cubase 12 crashes, can’t work for more than half an hour without a crash. It will lock up for a few seconds then exit the program. Upon starting Cubase up again I get a link to the crash dump file and the culprit seems to be kontakt.vst3. I have the latest version of Cubase 12 and the latest version of Kontakt 6. Removing Kontakt isn’t really an option as my projects have many instances of it. Is there anything else I can try? I’m on Win 10.
Hi,
If the
culprit seems to be kontakt.vst3
then get in contact with NI support, please.
I have contacted NI as well, I wouldn’t be surprised if they say contact Steinberg though. I was hoping maybe there was a way of me reading the crash file and seeing if there’s any more info in it that could help.
Hi,
If you attach the *.dmp file, we can have a look.
thanks, the DMP file is too big to be attached but here’s a dropbox link to it:
I also have consistent crashes when CLOSING any project, using Komplete Kontrol. It happens every time without fail. The crash actually first happens when I try to open a new project. So I can only work with one project, and I have to restart Cubase, i.e. it “does it for me”. As soon as I load any new project with or without Komplete Kontrol, it crashes after I have used a project containing Komplete Kontrol. I have let NI know and I have followed all their troubleshooting guides. My guess is that something doesn’t work in the “closing phase” when shutting down a project.
Cubase 13 pro
Windows 11
everything updated.
Hi,
I can confirm the crash is in NI kontakt:
Kontakt+0x7df3ef
0x00000005`a5faf384
0x00000005`a5faf401
0x00000005`a347f401
0x00000005`00000002
0x00000005`a5faf1a0
0x2
0x00000005`a5faf38
There is no Cubase mentioned in the call stack at all.
1 Like
So this is the reply I received from NI, I went through the steps they suggested but none of them solved the issue so I created a new Windows user account. For some reason though when using Cubase in this new account it doesn’t seem to want to recognize the plugins I have installed (most of mine are in the programfiles/commonfiles/vst3 folder). I can go into the plugin manager and the folder paths seem to be correct but none of the plugins show up, I’ve tried the rescan option and removing the folder and adding it again but no joy. NI are wanting me to try this new Win account as a test but I can’t even get that working as intended.
On investigation, we found an old ticket from another customer who had the same problem as the one you described. In that case, it was caused by something wrong with the Windows installation where the C++ libraries and the .NET Framework were aborting during installation or when the NI app was crashing on start-up. Please try the following steps in order to repair the OS system:
** Repair potential issues using scf /scannow*
** Use the System File Checker tool to repair missing or corrupted system files - Microsoft Support*
** Reinstall the .NET Framework (mandatory for using the latest NI products)*
** .NET Framework installation guide - .NET Framework | Microsoft Learn*
** Reinstall the VC++ Installation*
** Latest supported Visual C++ Redistributable downloads | Microsoft Learn*
** Make sure that Windows is updated to the latest version*
** Update Windows - Microsoft Support*Afterwards, please do the following:1. Save the attached files to your desktop
2. Right-click on the files → Run as administrator
3. Now uninstall the desired product (e.g. Kontakt 6 and Kontakt 7).
4. Now restart the computer
5. Now open NATIVE ACCESS and reinstall the desired product.Does the issue still persist?
If yes, we recommend creating a new Windows Admin User Account and then trying to recreate the issue in the new user account. If the issue doesn’t occur in the new user account, settings or files in the original account might be causing the issue.
We would not recommend copying the old Accpunt into the new one. This will maybe end in the same problem as before.
Yep, that’s their go to solution, as they don’t know anything else.
This is not a good solution at all, and simply makes no sense. Most of your licenses won’t work in your new account. (You have to create a whole new user with a outlook account and everything in order to have a new user in windows.) But because your licenses don’t transfer, NI’s products hangs. For example, Komplete Kontrol checks all your plugins at start up, and as no licenses can be found, it can’t “Komplete” (ba dum tshhh)
I can’t even get Cubase to start with a new account as Windows is “confused” about what licenses and programs belong where. (If you haven’t installed all programs as “all users” for example…)
And if this for some reason would work, would I have to log in as a new user every time I want to work with Native Instruments? No, this doesn’t make any sense. I have even reset my windows install and it still doesn’t work, so it simply isn’t about a corrupt windows as they put it. But clearly a faulty software they refuse to fix and/or take responsibility for. The whole argument that it works on other machines doesn’t matter, as systems are different. It is not the first time NI have software problems for many users, and as my problems only occurs when the program tries to close and reopen it might “seem” like it is working.
BUT, this only happens in Cubase. Not in any other DAW. So, Cubase and Komplete don’t play nice together. And until Steinberg and NI actually will take a look at this I am afraid we are sitting ducks.
Cheers!
Keep clicking the “send log files to Steinberg”. Maybe that will get their attention
Cheers!
Hi,
If the crash is in NI Kontakt, what is the point to send it to Steinberg, please?
Well, maybe not much, but since the crash dump happens in cubase, and only Steinberg can read those files, they might actually take a look at it.
As I assume it is combination of those two. NI works in other DAWs for me. In my case, it crashes Cubase, so.
Hi,
Not at all. Everyone with some debug tools can read at least the basics (if the crash is in Cubase or a plug-in). If the crash is in Cubase, you can’t go deep in to the methods. I would expect the same, if the crash is in NI. I would expect, they have their code protected properly. But you can see, where did the crash happen.
I don’t think that spamming them with irelevant informations will improve Cubase.
Well, NI refuses to read those dump files, saying they can’t. I certainly can’t get anything out of them. And it would be nice to know what is happening.
Hi,
Everyone on Windows with the Microsoft WinDbg tool can read the files. The files are created by Microsoft, not by Steinberg.