This is obviously from Kontakt (based on the DMP file’s stack trace). Does it only happen after your first Cubase session after a system reboot, or every time? The reason I ask:
On my old (Windows 10) system at one point, I had a frequent issue where the first project load with Kontakt (probably 6 or 7 or both) would get this sort of issue – i.e. Cubase generating a freezedump.dmp file in the first use after a reboot. It was “invisible” to me during that session because Kontakt worked just fine in the session. However, on the next Cubase session start, I’d get the screen with the “send log files to Steinberg”, which clued me into the existence of the DMP file, which further clued me into its happening with Kontakt. It wasn’t unique to Kontakt – Guitar Rig Pro could also get the similar issue.
What I eventually learned (from a Steinberg engineer in the Dorico forum, though I only saw the problem in Cubase) was that Cubase had some sort of simple timeout mechanism on starting out a plugin. If the plugin didn’t start within a certain amount of time, Cubase would assume it had hung and generate the freezedump.dmp file. Of course, if Kontakt were just slow in starting up, it would work fine throughout the session, at least beyond the slow loading time.
The underlying issue for me was a combination of two things. First, I have quite a few Kontakt libraries (I’m not sure how many I had at the time, but I checked the other day, just out of curiosity, and it is slightly over a hundred at the moment), and Kontakt must be doing something that probes each library on startup. Second, it turned out my system hard disk was dying, and accesses to it could be very slow. The reason it only happened on the first Cubase start after booting up was because the disk areas being accesses were cached in memory after that first start. Once I replaced that dying hard disk with an SSD, I never had the problem again.
The net was that the DMP file generation (which happened most days as most of my projects have at least one Kontakt library in them) was an annoyance, but nothing to worry about for Cubase/Kontakt reliability. On the other hand, it ended up being one of multiple early indicators that my system disk performance was going south (and the disk eventually failed.
If you’re only seeing this on the first session of the day (well, the dialog would happen on the second session), then you may want to check your disk to see if it may be going south. CrystalDiskInfo is pretty good for analyzing that sort of thing (and it’s free).
lol
