I started to suffer the problem on 10.5.2 (reverting to 10.5.1 seemed to clear it, but I liked the other innovations and didn’t realise how bad it was going to be).
I have been running C11 for just over week. No problems at all for six days. In fact no problems anywhere within C11 which is otherwise looking to very stable. Then I did have the same crash as before, then several more rapidly after that. I rolled back to a system restore point from a couple of days earlier.
The crash dump always comes back with the same error:
STACK_COMMAND: ~0s ; .ecxr ; kb
Waves NX uses opengl and would seem to be the culprit. I have opened a support ticket with Waves. I am on NX V12 which is the latest version.
I have had one more crash since rolling back!
Online, I found one or two descriptions of similar problems including one which made a good argument for a crash introducing a rogue entry to the system registry. And here is the thing, once that line of code is there, it can crash Cubase on closing regardless of whether any Waves plugins are in any particular project! This isn’t by any means proven, but does seem to make sense with my symptom. Apparently, removing or renaming it clears the problem until the next crash (for any reason), at which time a new bit of code is introduced.
I have found WaveShell entries here: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers …after suffering these crashes.
The writer goes on to say that he understands that Waves know what this is.
So, I am awaiting response from Waves, who’s support is generally pretty good. Meanwhile I am praying that I can avoid too much trouble over the next few days. It causes Cubase to fail to update Recent Projects lists, rendering settings, sometimes screen layout, preferences and so on. It definitely seems to be linked also to longer periods of work. A quick open/close test doesn’t seem to be a problem.