I don’t judge or blame anyone. I just try to help you to find the source. So I would try to remove half of the plug-ins and try to scan the plug-ins again in Cubase. If it works, then the problematic plug-in is in the other half. If the scan fails, the plug-in is in this half. Then you take one half of the part, you discovered the problematic is in. And do the same. This is the fastest way, how to find the problematic plug-in.
Once you have the plug-in, we can try more. Like update the plug-in, for example.
You can also try to use Microsoft ProcDump utility to generate a DMP file, to find out, where the problem is.
Please download ProcDump64 from Microsoft (~650kB) and extract the archive to a local folder on your harddisk.
Run Command Prompt (cmd) as administrator (right click and select “run as administrator”)
Navigate (in the Command Prompt) to the folder with the extracted procdump file.
Note: the dmp file will be written into that folder.
Launch Cubase/Nuendo. You can work as usual. At any time, change to the command prompt and start procdump, to monitor Cubase/Nuendo for unexpected behavior (see next step).
Launch procdump64 via Command Prompt:
procdump64 -e -h -t Cubase10
procdump64 -e -h -t Nuendo10
The -h option will write a dmp file in case of an application hang. This might kick in too early sometimes, in case some action takes a little longer. Feel free to skip the “-h” option, if you are only up for fetching crashes.
The option -e will catch exeptions and the option -t terminations of the application.
- Prodump is now monitoring the Cubase/Nuendo process and will write a crash log, in case Cubase/Nuendo crashes or hangs. Perform the action that causes Cubase/Nuendo to crash and send us the generated crash dmp.
Share the DMP file via Dropbox or similar service, please.