Cubase 12.0.70 freezes with NI plugins

ErezW
ErezW Member Posts: 3 Newcomer
in Komplete General

Hi, I own the latest Komplete, on Windows 11, with Cubase 12.0.70. All of the sudden, about a week ago, saving cubase projects began to freeze. I did some narrowing down and discovered it is NI-only related. The existence of plugins such as Kontakt 8, Guitar Rig 7 and possibly others causes that freeze. Additionally, if I disable the plugin, it freezes the session as well.

I'm completely up-to-date as far as software versions are concerns.

Any help will be appreciated.

Thanks!

Erez

Answers

  • ErezW
    ErezW Member Posts: 3 Newcomer

    I should also comment that due to the freeze upon closing the project, cubase produces a freeze dump

  • BIF
    BIF Member Posts: 965 Guru

    Hi.

    Pick one of the software items that causes the Cubase crash. Let's say, Guitar Rig 7.

    Try these things to see if things magically get fixed for you:

    1. Go into Cubase/Studio/Plugin Manager.
    2. Screen print the list of folders.
    3. Now, going through your list of folders, one-at-a-time, look to see if Guitar Rig 7 exists in more than one of those folders. If there is both a VST2 and VST3 version of it, I would remove the VST2 version and leave the VST3 version in.

    Try this.

    Another thing you can try is to recreate every VST2 and VST3 folder that Cubase uses, as an empty folder.

    Here's how I did it:

    A. Let's say there's a C:\Cubase\vstplugins folder.

    B. Shut down Cubase.

    C. Create a partner folder called C:\Cubase\vstplugins\empty, then rename vstplugins to vstplugins\hidden (meaning that now it's hidden from Cubase's view). Now rename vstplugins\empty to vstplugins.

    D. Do the same thing for every folder that has vstplugins that Cubase can see.

    E. Now your vstplugins folders are all empty. Your "hidden" folders have all the DLLs in them, but they won't be seen by Cubase.

    F. Now start Cubase. Make sure it doesn't crash. It shouldn't.

    G. Now move a couple of plugins from your vstplugins\hidden folder(s) into vstplugins, and restart Cubase (or refresh the plugins list in Cubase. See if Cubase crashes.

    H. Continue gradually re-adding your VSTs back until you find the ones that crash Cubase. Make a list. Are they 32 bit? 64 bit? VST2? VST3? A mixture? Is it only NI plugins that crash Cubase? Or are there others too?

    Get this defined better.

    If it's just NI plugins, then you could try reinstalling those instruments. But I say build the list first. Keep us posted.

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,971 mod

    @ErezW Any update?

  • ErezW
    ErezW Member Posts: 3 Newcomer

    I did all the analysis as you suggested and it was clear it's only NI plugins… However, I then discovered a physical RAM error in my PC, using microsoft diagnosis tools. The thing with RAM errors is that they could lead to "silent" corruption of persistent on-disk information… And from there all hell breaks loose… My PC is now at the doctor for a serious hardware check. I will then reinstall the entire computer from scratch. My gamble (or shall I say wishful thinking) is that everything will then be fine. I promise to update once I do that. Thanks a lot for the help in the mean time! BTW, the great idea of running the microsoft RAM check tool came from NI support!

    Thanks!

  • Jeremy_NI
    Jeremy_NI Customer Care Posts: 12,971 mod
    https://community.native-instruments.com/discussion/comment/193955#Comment_193955

    Thanks for the update, hopefully the issue will be fixed when your computer comes back.

Back To Top

Categories