Cubase 13.0.41 on Windows 10. I am using a Steinberg UR44 interface.
I had opened a small project with only a few virtual instrument tracks. I did some work on it yesterday evening. I left Cubase running after I was done with the project open.
Tonight I went back to it. After making a few new adjustments, I was adjusting stereo balanced pan on a track and Cubase stopped responding with the cpu and disk usage meters at zero. I have to kill the Cubase process in Task Manager to get rid of it. This is not the first time this has happened.
Also, in Task Manage under Cubase, for some reason there are 6 instances of Microsoft Edge Webview2. I have no idea what that’s about. I don’t use edge as my browser, but I do have MS Office installed on this computer so I can access Excel. It makes me wonder if Cubase has a memory leak, pointing to the wrong address somewhere? Just a thought.
Interesting. Are you too running the latest Cubase version? Also, what audio interface? And do you see the Edge Webview2 in Task Manager under Cubase process?
I’ve error checked my SSD, trimmed it, SSD is 80% full. Virus checked and of course there isn’t any grey area software on it. 100% approved by Microsoft. All other software runs flawlessly.
When I look at the Cubase process in Task Manager, and open the list of subprocesses, that’s where I see the 6 instances of MS Edge Webview2. I do not know if those were there prior to the lockup, but I know they weren’t there when I first opened Cubase.
I’ll have to remember to look next time at some later time after opening Cubase to see if they are there.
I’ve checked the Cubase crash folder with a Windows crash log tool but I’m uncertain how to interpret the results which are fairly cryptic. Learning that utility is on my edu list.
Generate a DMP file and share it via Dropbox or a similar service, please.
Use the 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 hard disk.
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 behaviour (see next step).
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 exceptions 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 a similar service, please.
When the Hub is opened, Cubase accesses various Steinberg Web Content using MS EdgeWebView2. This is why there are several instances of it, which is normal (upper image). If the Hub is closed, the instances of MS EdgeWebView2 are normally unloaded again (lower image).
Access to the Steinberg Web Content can be deactivated in the Preferences: General > Show News in Hub. MS EdgeWebView2 will not be loaded then.
I suppose, but I assumed that wouldn’t be useful as it was not the issue of interest. I assumed procdump caused Cubase to end, so I gave up on that.
However, Cubase did itself create a dmp file from the hang of interest, I assume, because it asked if I wanted to send the file to Steinberg, which I did. Of course, half the time when I start Cubase there is a file it asks me if I want to send.
ProcDump itself can’t and doesn’t crash Cubase. If it crashed while initializing of Cubase just point to the fact, the issue is there while initializing of the faulty component/plug-in already. It just doesn’t appear while running Cubase a common way.
If you get the Safe Start Dialog message, that means, Cubase crashed last time during Quit.
It’s good that you sent the DMP file to Steinberg. It will help them. But if you want to get any feedback (for example to know, if the crash happened in any plug-in), you can share the DMP file here and we will give you a feedback.
Same here. Since updating to 13.0.41 the system hangs while working on some effects and moving tracks. One time Cubase stopped immediately and the computer did a complete restart. In another case I had to kill Cubase via task manager.
The audio performance meter shows a system overload and Cubase crashed.
This looks serious and it doesn’t look like a Cubase issue. If the computer restarts, it looks more like a hardware issue. Please, test your system. Make sure, all your drivers are up to date.
The drivers are ok. The hardware is brandnew and till this update the system ran without any problems. We usually work with 36-48 audio tracks, some external periphery, some VST-effects.
There came a conflict message like “system conflict: cubase.exe”.
In one case the audio playback failed for a few seconds, the tracks could not be edited at that time.
CPU is an AMD Ryzen 9 7900X 12-Core Processor 4.70 GHz, RAM 32 GB, HDD 2 TB. I think this is not the reason. Audio interface and driver are ok. as well…
