What all to do when Nuendo starts Crashing

You are not alone we’ve had the same problem for weeks its weird as it seems to be a memory issue. We’ve just been mixing on latest picture and crashing frquently. From time to time, Nuendo or some software that Nuendo uses can become confused. It will typically cause Nuendo to crash immediately upon trying to open it. A re-install of Nuendo will not fix it.. If this happens, you are competent with file management, and are willing to be responsible for any consequences (most of the time it would only be re-setting all of your preferences) then consider trashing those prefs. If you become confused or unsure of why you are following a specific step, I would recommend that you stop and call Steinberg tech support.Here is the list of possible things you can do to fix it


1. We may have a possible solution by ncreasing your page file size in windows to do this first check you have at least 10GB of free space on your system drive. To change the page file size; right click on my computer icon on desktop go to properties & click the advanced tab, click the setings box for performance and then the advanced tab on this new window. Under virtual memory click change then click the radio button for custom size, we have increased ours to 6000 for both initial and maximum. We found this helped at 12 hr today and since then we haven’t crashed yet

2.  Try to load all the backup project you have.

3.  Have nuendo on another PC  and open the project there..

4. If Cubase/Nuendo hangs or quits during the start up or while loading a specific project file it is likely that an installed VST plug-in is causing trouble.
Temporarily hiding installed VST plug-ins from Cubase/Nuendo is an easy and effective way to verify if a specific plug indeed is sabotaging your sequencer.
Of course, for this operation you need to know all VST plug-ins folders Cubase/Nuendo is knowing…

Locating VST Plug-in Folders

* In Cubase/Nuendo, select “Plug-in Information” from the “Devices” menu.
* Make sure the “VST PlugIns” tab is selected and click on “VST 2.x Paths”.
* The VST 2 paths known to Cubase/Nuendo will be listed. Write them down, make a screenshot or simply memorize them.
* Additionally consider the VST 3 plug-ins folder: C:\Program Files\Common Files\VST3

Hiding VST Plug-ins

The following steps describe only one possible application of the “hiding stragegy”. Of course you can have your own approach if you’ve understood the basic idea.

* Quit Cubase/Nuendo.
* Navigate to the first VST plug-in folder (refer to the note or screenshot you’ve made before, or your memory).
* Assuming the folder is named “VSTPlugins”, rename it to “VSTPlugins_hidden”. This will hide it from Cubase/Nuendo.
* Restart Cubase/Nuendo.
* If necessary, load the problematic project. In this case Cubase/Nuendo will complain about missing plug-ins. Simply ignore corresponding error messages.

If the problem persists you know that it is obviously not related to a VST plug-in inside this hidden folder. In this case rename the folder to its original name and repeat the procedure with the next VST plug-ins folder on your list.

If hiding one of the folders actually fixed the problem you still don’t know the bad guy but, after all, you know where he is living… In order to identify the problematic plug-in create a new folder next to the hidden one and give him the original name, in this example “VSTPlugins”. Now you can move the most suspicious plug from the renamed folder (e.g. “VSTPlugins_hidden”) to the new one (e.g. “VSTPlugins”). Restart Cubase/Nuendo and see if it still runs correctly. Repeat moving plug-ins and restarting Cubase/Nuendo until you’ve finally isolated the trouble maker. In case you have a lot of plug-ins installed moving half of the them at a time might speed up the search.

5.  Unload the update installed on the PC one by one and see if the problem is getting fixed.

6. Load a Blank Project then load the offending crashing/refusing-to-open project but not to activate it. Then lose the empty project and hey presto, crashed project opens. The crash portion can be difficult to find (usually a VST load issue) so you may find that even re-saving the project does not get rid of the error – annoying, yes, fixable, yes.


Following are the additional steps we found at a forum, if you are a new Nuendo user, these are in more detail.

1.) Close Nuendo

2.) Make a safety of your preferences if they are important to you..
– Go to My Computer/Tools/Folder Option/View/ and enable “show hidden files and folders”
– Navigate to C:\Documents and Settings\”YourName”\Application Data\Steinberg\Nuendo 3
– Copy (do not move) the entire Nuendo 3 folder to another folder on your desktop for safe keeping (do not move them)

3.) Trash your specific Nuendo preferences..
– Navigate to C:\Documents and Settings\”YourName”\Application Data\Steinberg\Nuendo 3
– With a safety copy made as described above, Delete the “Defaults.xml” file.
– Next open Nuendo and it will re-create this file
– If this does not allow Nuendo to boot, then Close Nuendo and delete “Configuration.xml”
– Next open Nuendo and it will re-create this file
– If this does not allow Nuendo to boot, then you can replace both of these re-created files with the original files from the safety folder..
– You may also try deleting another listed file that may seem to associate with a recent change (and may have caused Nuendo to stop booting.) Just go slow and manage your safety files carefully..

If none of these work, then your issue may relate to something else besides Nuendo preferences.

This is a starting point for what will hopefully end up being a well written and thorough description on how and why to trash preferences.. I am pretty sure that many of us have hit this wall at least once.. I hope I can save good people willing to do a search the trouble of losing productivity.. If anyone can think of other ways to improve and revise this initial post, please post them and I’ll edit them in.. If anyone can think of key words to add that will aid in people using the search function, please let me know so I can add them..

Additional advice : “Look for “J Bridge”. It’s a VST bridge software that allows you to use all the RAM you’ve got on x64 systems, even if your host application is x86. I’ve been working with it for several months.”


If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.

Check-out Our Portfolio