Just installed C 10.0.40 a few days ago on a new machine/win 10 install and everything seems to be running beautifully so far, no crashes and it all seems pretty stable.
Thought i’d look at the win event manager to see if anything is happening there and it seems every time i close Cubase the following error occurs…
Crashes of that kind are very often related to UI/GPU. I guess the Cubase crash dumps folder does not contain anything related to those events?
I’m investigating this kind issues, I can PM you the procedure to actually get a dump out of the silent termination (MS ProcDump).
You should not have issues like that with the card in signature: if you didn’t do it, I’d start with re-installing the GPU driver in custom mode and only select the video driver entry.
I’m seeing these - although I don’t know why you suggest it’s related to GUI or graphics card errors ?
ucrtbase.dll is from MS visual C++ and used by lots of people and lots of software - the actual error is c0000409, a USER MODE stack buffer overflow
In my case I get a very subtle and quiet crash on exit - you wouldn’t notice if you didn’t look at the windows log. I’m seeing this on cubase/nuendo and wavelab. It happens right at the end because all of the preference.xml files are written ok. I strongly suspect it’s either a plug or something on steinbergs end.
What is odd is that I deleted my cubase user preferences (because of another cubase issue !!) and the problem disappeared - Deleting these preferences deletes your custom plugin folders of course. Even after adding these back in the crash is gone in cubase but is still there in nuendo.
if you look through the forum you will see other reports of this same issue (and the same people saying ‘it’s your graphics card’ (random). I need to do some more experimenting - but I strongly suspect that lots more people are having this crash but don’t know because they never look at the windows application log - or the error reports.
Hello dr, good points, but I know for a fact that 90% (that’s why I wrote ‘very often’) of the ucrtbase crahses are termination commands from ucrtbase due to GPU / driver issues (I can’t share additional info, but there are specific buffer operations that trigger that). I actually gathered every support request that ever entered our system and filed the results.
understood - and to be fair you did say “often” - though this one was definitely ilok software - it’s on their release notes. ucrtbase is used by loads and loads of software (including wavelab - which is written in visual C++ IIRC)
In my opinion it’s dangerous to assume that any problem like this must be related to things you may have seen previously. I’m fairly certain that the kind of crashes that people report to SB are “show stopper” crashes that terminate the program. I’m also willing to bet that 99% of people running an ilok on windows were experiencing this crash but they just hadn’t noticed as they never look at their windows logs. This means the kind of issues that are being reported to you are just a small subset of the issues - so even more dangerous to assume anything, especially foolish to say "I know for a fact that 90% etc etc "
It’s also indicative of the kind of support that SB generally give in my experience - basically just reinstall random stuff and if that doesn’t fix it then we don’t know.
this came from filing issues and examining them, I call that experience rather than ‘random stuff’.
It is standard support to start with most probable scenario, point to how to solve that and how to obtain more effective means of investigation (ProcDump, not ‘then we don’t know’), which is what I did via PM.
ProcDump came up with the following, I wouldn’t really point the finger at iLok here:
A wrote a long reply but decided not to send, suffice to say what you imagine the steinberg support staff do with tickets and what actually happen are two very different things.
IF (a big IF) you get a reply at all it’s either irrelevant or telling you to turn it off an on again. Happy to give specific examples but I know nothing will change !
Just my experience (from using steinberg software since 1988)
Not the ones in the ProcDump, but you’ve gone a long way since then (also with the DAW builder )
Thanks for posting back, I’ll follow up via PM for the plugin topic and the BSOD if you don’t mind.
@dr: I sent you a PM, if you have pending issues I can help with, please let me know.
)