Yeah, same result.
“Admin” is not the built-in Administrator account. “Admin” is just the profile folder attached to my Microsoft account login. I guarantee you that it’s a red herring
I have 551.52 installed from Feb 13, though this has persisted through multiple versions of the driver.
And what about the /T option? Does that do anything better?
Same result.
Process Hacker is not supported on Windows 11,.
See:
Perhaps try its successor:
OK, I am all but convinced at this point that this issue has something to do with Nvidia drivers. I hadn’t had this happen in quite a while, but it did happen today. I also had a video card driver update that had been waiting for the better part of a week, so I went to install it before I restarted, and sure enough, same as the last time this combination of factors coincided, the computer hard locked. Now, the question is what can be done about it?
I observe you are using the Nvidia Game driver. I use the Studio driver. The revision number is lower, but it works well for me. Perhaps try switching to that driver? At least you have a choice to test out.
Wat Nvidia based card do you have? Some older ones are known to cause trouble.
To be honest, I don’t know what to do either. As I said, I googled on unkillable processes and most likely this is caused by some stuck driver. Which one I can’t tell, so we have to find out somehow.
For that, please take a mini dump of the VSTAudioEngine by means of the Process Explorer. Look for the VSTAudioEngine process, do a right click on it and from the pop-up menu choose Create > Create mini dump. Thanks
I researched this. Exactly as with linux, a zombie process that can’t be killed is waiting pending IO from a device. It can’t be terminated until the IO request completes. Its a kernel design function common to multiple operating systems. That must give some clue.
Here you go. I nearly forgot to do this before restarting! I can’t attach it even as a compressed file because nothing will get it under 4 MB.
I frequently have problems (on Windows 11) if I shut down Dorico (latest version), and then re-start Dorico without waiting for a minute or two. Then I get the “waiting for audio engine” forever. I can kill all the Dorico processes I can see in Task Manager, but then I get something like “Dorico is not licensed” and I have to re-boot my machine.
I’ve learned to never shut down Dorico and then re-start to switch to another project. I just open the second project from within Dorico, and then leave the first project open.
It’s a strange problem, for sure!
Tom
It is unusual to have to re-boot your PC. Perhaps you should post your diagnostics?
I have occasional problems closing Dorico (on Windows) and am beginning to suspect Kontakt as the plug-in that misbehaves and causes VSTAudioEngine to hang.
In such situations, it could be that Kontakt or even others are displaying a modal dialog which just slipped behind the Dorico window. If that is the case then everything looks like locked, because the main thread of the audio engine is waiting for the user to prompt the modal dialog, and then also Dorico locks because it is waiting for an answer from the audio engine, which itself is waiting for user input.
Since @Tkearneyone appears to be using Windows, hovering over the program icon in the taskbar at the bottom of the screen should indicate the presence of hidden dialogue boxes. It’s worth a try.
@JustinM did you solve this yet?
Did you try my Nvidia driver suggestion? Do let us know what card you are using.
I have not solved it, but there have been multiple driver updates since that original post. I just installed 551.76 earlier today. I’m using an RTX 3070 and the studio driver didn’t seem to make any difference as far as Dorico’s concerned.
There may be many happy 3070 users but I have heard of a lot of issues with that model card. Some of the following posts here may be pertinent:
Understood…but I’ve had this video card in this PC since 2021 and this issue only became a problem since Dorico 5 came out.
So maybe Dorico 5 is pushing the card in ways previous versions did not. Can you try using your board’s onboard graphics for a while instead?
I do not have onboard video in this rig.
Unusual nowadays. What MOBO?