Thanks Juergen.
Like i mentioned some of these DMP files are a little old and already have been shared.
So even if im not using kontakt 7 in the project that will still crash the DAW? Because that is what happened.
Should i contact Native Instruments?
Hi,
I can see following crashes:
- WebView2Loader: I donāt know, whatās going on here
- 2x Cubase: This suppose to be fixed in Cubase 13.
- 2x Kontakt 7: NI plug-in
- GenericMultiCoreProcessor: Waves plug-in
- Howard_Benson_Vocals: plug-in
- Generate: I donāt know this
You should update your plug-ins.
Ah!
After a little digging it turns out Webview2 is a dll file that runs with Microsoft Edge which i just recently uninstalled.
Generate is synth plugin by New fangled audio i have updated since the last time i posted the DMP file that was associated with it aswell as the Ilok licenser that runs Howard Benson Vocalsā¦
Kontakt 7 was also updated at the same time. I have had crashes after these updates.
I need to check out the waves plugin.
I realy appreciate your help Martin 
1 Like
Right in the middle of a project im working on right now it just happened againā¦im totaly lost for wordsā¦if i get a DMP file i will post it.
EDIT: I got another 0KB DMP file that i cant even upload.
@AdamMassacre my suggestion:
Buy a 256GB SSD (around 40 $/ā¬) and install a fresh windows on it. Install only Cubase, the necessary drivers and the plugins you use. Leave your āoriginalā OS drive untouched, so you can always go back in case. Try using Cubase on the freshly installed drive.
This way you can assure the issue is not coming from any corrupted system files, etc. and by reinstalling you automatically make 100% sure everything is uptodate.
Iād suggest also to try with C13 as I have found it runs more stable. E.g. when freezing or disabling instruments C12 always crashed on me before on certain instruments (also Kontakt), while C13 just continues running.
EDIT: I donāt know your situation, but thats what I actually suggest everybody to do when having a āmultimediaā-PC: Install only audio related stuff on one OS disk and the rest on another and boot from the disk you are going to use, this prevents already a lot of issues.
2 Likes
Hi,
Generate a DMP file and share it via Dropbox or similar service, please.
Use Microsoft ProcDump utility to generate a DMP file, please.
-
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.
For example:
cd C:\ Users \ \ Downloads \ Procdump
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:
Cubase 13:
procdump64 -e -h -t Cubase13
Nuendo 13:
procdump64 -e -h -t Nuendo13
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.
ZIP and share the DMP file via Dropbox or similar service, please.
In all the tests I did, I thought I discovered the reason. I have 1 sound interface and I acquired a recent one and it was after I installed it on my system that the problems started. I believe it is an incompatibility with the new interfaceās sound driver with version 12. And this driver is updated. I used the same interface in Cubase 11 and had no problems. I also used the old interface on 12 and had no crashes. Test with another interface and see if the crashes continue. Iām on version 13 and so far I havenāt had any problems.
1 Like
As an extreme long shot, and if possible.
Create another User Account and open Cubase to see what happens and set up Cubase as you would normally.
I say this because something may be broken in the current User Account.
I once encountered all types of issues going on with Cubase and re-installing fixed nothing, plus four days of trouble shooting, I was too reluctant to do a complete install of Windows, DAW and Plu-Ins, so decided to open another user account to see what would happen. Cubase worked fine in this newly created account. The drawback was having to reactivated certain plugins, especially if deleting the troublesome User Account as I did.
Another example of this is when I was having issues with the SDA and couldnāt update, download or set path. It kept throwing up errors.
Opened another User Account and managed to update the SDA as normal and it seemed to work fine in this newly created account.
Logged back into my original account and the SDA was back to working order.
This may not be viable for some, but I would certainly try just in case.
Plucking at straws as usual.
Hi,
Which Audio Interface is the problematic one, please?
M-audio 192 /14
Hi,
Itās quite old one, isnāt it? Does it even have a driver for Windows 10/11?
The M-audio 192/14 driver was last updated in 2021. But it is still more recent than the other interface I have, Sound Craft MTK 12, with the latest driver in 2019. They are all compatible with Windows 10, which is the operating system I use.
Hi,
OK, thank you for the information.
Have you tried to reinstall the driver? I would try to install it as administrator in this case.
So i just did a HUGE clean up of my PC uninstalled a load of stuff deleted a load of stuff cleaned up all the clutter on my hard drives scanned my full PC for any naughty stuff fixed all the cluttered cables updated everything i could possibly find even dusted down all my hardware and fired up the vacuum cleaner sprayed some air freshner put on a nice calm dim lamp opened up a window made some fresh Teaā¦inhaled some cool fresh airā¦just about to fire up Cubase 12 for the last time before i make the jump to 13ā¦wish me luck fellas 
1 Like
I did this procedure several times, installing as administrator and it didnāt solve the problem. The strangest thing is that the problem is only with version 12. Versions 11 and 13 are running m-audio 192/14 very well.
Hi,
Iām glad to hear this.
Have you tried to rename/remove Cubase 12 preferences folder, please?
I uninstalled Cubase 12, deleting all program folders and preferences, uninstalled the Sound Driver and reinstalled it, updated all my original plugins, but even so, the problem was not resolved.
So you got a positive resolve updating to 13? no more funny business happening like in 12?..
Yes. Itās very stable on my machine and without the freezes I had with version 12. So far I like the update.
2 Likes
