Thanks for the help, Ulf. Here are the additional results of the testing you’ve requested.
First, the VST2 path removals yesterday did not make a difference on first startup after booting today. To give some idea of the sequence on startup that first time, I started Dorico at 7:51 AM on the Windows clock. It ran through a number of status items then was at the audio engine initialization status fairly shortly after that time stamp. The next change I noted in the status items was the switch to “ping response received: from silk service” around 7:58 (it may have appeared a minute or so earlier, but this is when I noticed it). At some point between this time and the crash, I noticed a task bar icon for PCPushNotify that was there long enough for me to notice, but eventually disappeared. I’m not sure what this is from, and it may be something completely coincidental. While the ping response prompt was up, I also looked at Task Manager in the performance area, and I could see my C: drive (system drive, where applications and plugins reside) was showing 100% bandwidth use. (This is actually fairly common when plugins are being scanned.) I also noticed in Task Manager’s process area that there were three tasks starting with VST, one being the one you VSTAudioEngine5 and the others starting with VST3 and then something with “scan” in it (I did not take a screenshot, and I don’t remember if the names were the same or slightly different). At 8:06 AM, I noticed another task bar entry that did not have an icon or name, but hovering over it I noticed that it was Dorico’s file loading meter, which showed it at the 92% mark. (I probably had other windows covering up the actually screen.) Still at that same timestamp, Dorico disappeared (crashed without an error message).
Note that I did not do the Process Explorer test on the first start as I wasn’t certain if taking the dumps might affect whether or not Dorico would crash on the first start after rebooting. I might also note that I was starting Dorico by double clicking on the file I’d been working on recently.
While I wasn’t certain if the minidumps you requested might be different on a second Dorico start after rebooting, I did take those on a second start (also double clicking on the file to start). You can find the dumps at Dorico startup minidumps, 2022-12-11.zip - Google Drive. Short summary is that all 10 mini dumps, taken between 8:13 AM and 8:17 AM, are virtually identical. I used Windbg Preview’s “analyze -v” command to get stack dumps of each file, putting them in text files, and a FC between the first and tenth file shows the only difference relate to times and file names. In all cases, the top of the stack shows “ntdll!NtWaitForSingleObject+0x14”. (I might note that this is the same as what is at the top of the stack on the Cubase freezedumps I mentioned for Kontakt and Guitar Rig – my having noticed that in the earlier Dorico DMP file analysis is what lead me to mention the Cubase freezedumps.)
A few additional things worth mentioning:
I’m guessing the first two items will be expected, but here is what the Dorico process tree looked lie in Process Explorer:
Also, when I was searching for VSTAudioEngine (which turns out to be VSTAudioEngine5), it found quite a number of occurrences:
The other thing was that, on this second start, at some point it put up an error screen that I’m not sure I’ve seen before (though I have seen it mentioned by others in this forum):
This screen stayed up for a while, then Dorico crashed again.
After this I loaded Dorico without double clicking on the file, and Dorico did load to the hub, and I was successful in loading the document from the hub. After that, I could also open Dorico by double clicking on the file after having shut it down.
With respect to the Cubase freezedumps, I understand they are not crashes, and I appreciate the explanation. Perhaps these are new to Cubase 12 because I do not recall having seen the startup issues (i.e. prompts to upload a DMP file) or so many DMP files accumulating in CrashDumps in Cubase 11, nor the long Kontakt load times, though it is possible I may just not be remembering correctly on the latter. (I haven’t used Cubase 11 since I started using Cubase 12.0.0.) The freezedumps are really just an annoyance in that I sometimes forget to wait to see if I will get a prompt, and I usually walk away to do other things while Cubase is starting up as the startup time is so long, and, when I forget to check, sometimes I come back to that prompt, meaning the long load time will come later, and I’ll actually have to wait. (And it truly is almost always from either Kontakt or Guitar Rig.)