VSTAudioEngine5.exe is unkillable process

Re Nvidia, I picked up this information from a post in the Cubase category.

Try a complete total uninstall with DDU:

Then a customised sleek minimal fresh install with NVCleaninstall:

This is all very interesting…

I don’t get a Dorico crash dump in my situation. The next time I am seeing my problem, I’ll look for the VSTAudioEngine process, and do a right click on it and from the pop-up menu choose Create > Create mini dump .

I frequently use ā€œSampletank 4ā€ in my projects (it has a pretty good 12-string guitar). No Kontakt use in Dorico. No video use in Dorico. I don’t know if I have the problem when I’m not using Sampletank - I’ll try to keep a closer eye on things in the future.

I’ll also check for hidden dialog boxes.

Oh yes - I’m using an ā€œNVidia GeForce RTX 4060 Tiā€ - with the latest drivers.

As an ex-software engineer (40 years!!!) I know how hard it is to find and fix things if they are not easily reproducible!

Tom

I finally had some time after work today to give this a shot. I’ll report back when I have some sort of conclusive evidence one way or the other here.

It took all this time, but the zombie process finally happened again.

If it is zombied again, would you please create a new mini dump of the VSTAudioEngine using the Process Explorer app. Thank you very much.

Here you go. VSTAudioEngine5.dmp - Google Drive
Dorico Diagnostics.zip (1.1 MB)
I’ve also included the Dorico diagnostic dump.

Thanks for the data. Will have a look later…

Hm, now the stack of the audio engine’s main thread looks like:

> win32u.dll!NtGdiDdDDIDestroyAllocation2() Unknown Non-user code. Symbols loaded.
[Frames may be missing, no binary loaded for d3d11.dll] Annotated Frame
d3d11.dll!00007ffee50caef8() Unknown Non-user code. No matching binary found.

So it is not directly in the graphics card driver, but in the frame work where graphic routines get executed.

I’m experiencing the same problems of Dorico not responding or just seeming to shut down and disappear on its own without warning (the last time this happened, I had just clicked to open Chrome while Dorico was running). Then, Dorico cannot be reopened unless I restart my computer. I have also learned to wait for one Dorico project to open completely before clicking to open a second Dorico project, otherwise the program doesn’t respond and I end up having to restart the computer. (Dorico also stops responding if I switch the sound to headphones before waiting until I’m sure the project has had plenty of time to fully load). I read through this thread, and I don’t understand any of the IT terminology, so I’m sorry I can’t answer any technical questions. I’m just wondering if there was any fix that was discovered, or if I should just continue restarting my computer and being super careful with clicking/opening other things too fast. Sometimes, Dorico automatically produces a diagnostic report, so here is one if it’s of any help.
Dorico Diagnostics.zip (1.3 MB)

Unfortunately there are no crash dumps contained within the diagnostics you’ve attached, so it appears that either or both Dorico or its audio engine are ending up hanging, rather than actually crashing. The diagnostics don’t unfortunately allow us to determine what is causing hangs – for that, we need to sample the process when it is running.

Are you still experiencing these problems now?

I realize this thread is old now, but eventually this just stopped happening. I’m not sure whether it was a graphics driver update, a Dorico update, or a NotePerformer update, but something fixed it.