Event Manager Error Win 10

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…

Faulting application name: Cubase10.exe, version:, time stamp: 0x5d5e8df6
Faulting module name: ucrtbase.dll, version: 10.0.18362.387, time stamp: 0x4361b720
Exception code: 0xc0000409
Fault offset: 0x000000000006db8e
Faulting process ID: 0x11f0
Faulting application start time: 0x01d57f79de354591
Faulting application path: C:\Program Files\Steinberg\Cubase 10\Cubase10.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report ID: 021c19b2-8e9e-4970-a8f1-4d15f0747a61
Faulting package full name:
Faulting package-relative application ID:

Just wondering if this is anything i need to be concerned about?

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.

just to complete this in case anybody is searching for the answer - it seems like it was the ilok software - update fixed it

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.

Hi Fabio

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:

ffff988e`e1b4f2d8 fffff803`85720db5 : 00000000`000000ea ffff800e`f435f040 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffff988e`e1b4f2e0 fffff803`85720e8e : ffff988e`e1b4f3b8 fffff803`89ec3968 ffff988e`e1b4f3b8 00000000`00000000 : dxgkrnl!TdrTimedOperationBugcheckOnTimeout+0x45
ffff988e`e1b4f350 fffff803`89e49fd0 : ffff800e`f55db000 00000000`00000000 ffff988e`e1b4f4a0 fffff803`89ec3954 : dxgkrnl!TdrTimedOperationDelay+0xce
ffff988e`e1b4f390 fffff803`89e40da0 : ffff988e`00020564 fffff803`00020550 00000000`0002057c ffff988e`0002055c : atikmdag+0x59fd0
ffff988e`e1b4f410 fffff803`89ec3855 : ffff988e`e1b4f4f1 00000000`00000000 00000000`000007d1 00000000`00000063 : atikmdag+0x50da0
ffff988e`e1b4f450 fffff803`8b2c0026 : 00000000`000007d1 00000000`00000519 00000000`00000519 ffff800e`f5a26db4 : atikmdag+0xd3855
ffff988e`e1b4f540 fffff803`89ec6523 : 00000000`00000519 fffff803`8b2b53a8 00000000`00000519 000000a4`00000002 : atikmdag+0x14d0026
ffff988e`e1b4f590 fffff803`8b2d8f21 : ffff800e`f5a26db4 00000000`000f9801 00000000`00000000 00000000`00000000 : atikmdag+0xd6523
ffff988e`e1b4f5f0 fffff803`8b3514a8 : ffff800e`f4d98054 ffff800e`e867a9e8 00000000`00000000 00000003`00000030 : atikmdag+0x14e8f21
ffff988e`e1b4f620 fffff803`8b2b542d : ffff800e`e867a9e0 ffff800e`e867a9e8 00000001`00000018 fffff803`00000000 : atikmdag+0x15614a8
ffff988e`e1b4f680 fffff803`89ec2ed9 : 00000000`00000001 ffff988e`e1b4f768 00000000`00000000 ffff800e`e867a9e0 : atikmdag+0x14c542d
ffff988e`e1b4f6d0 fffff803`89e5a1ec : fffff803`8a0d9ac8 ffff988e`e1b4f930 ffff800e`e86baa00 ffff800e`f5024028 : atikmdag+0xd2ed9
ffff988e`e1b4f730 fffff803`89eff069 : 000000f4`000f9801 00000000`00000000 00000000`00000000 ffffe01f`3e39c8d8 : atikmdag+0x6a1ec
ffff988e`e1b4f790 fffff803`89e0600f : 00000000`00000001 00000000`00000001 00000000`00000001 00000000`00000001 : atikmdag+0x10f069
ffff988e`e1b4f7c0 fffff803`89e062ad : ffff800e`f5aadca0 ffff988e`e1b4f930 00000000`00000001 fffff803`800370d0 : atikmdag+0x1600f
ffff988e`e1b4f7f0 fffff803`89e0b69f : ffff800e`ed1fb040 00000000`00989680 ffff800e`f5630060 00000000`00002000 : atikmdag+0x162ad
ffff988e`e1b4f820 fffff803`89e11f9d : ffff800e`ed1fb040 00000000`00000000 00000000`00000000 ffff800e`f4bdfdb0 : atikmdag+0x1b69f
ffff988e`e1b4f850 fffff803`863bf7f0 : 00000001`dae3f4c7 fffff803`89cdcedc ffff800e`f435f360 00000000`00002800 : atikmdag+0x21f9d
ffff988e`e1b4f880 fffff803`858dddcc : 00000000`00000000 00000000`00000000 ffff988e`e1b4f930 00000000`00000000 : atikmpag+0xf7f0
ffff988e`e1b4f8b0 fffff803`858cfe5c : ffff800e`f50a80d8 ffff800e`f50a8000 00000000`00000000 ffff800e`fec1e010 : dxgkrnl!ADAPTER_RENDER::DdiResetFromTimeout+0x154
ffff988e`e1b4f950 fffff803`858d0966 : ffff800e`f50a0100 00000000`00000100 ffff800e`f50a8000 ffff800e`f50a89e0 : dxgkrnl!DXGADAPTER::PrepareToReset+0x184
ffff988e`e1b4f9a0 fffff803`859200f5 : fffff803`00000100 ffff800e`f90dd080 ffff800e`f90dd080 ffff800e`f435f040 : dxgkrnl!DXGADAPTER::Reset+0x276
ffff988e`e1b4fa10 fffff803`85920257 : 00000000`00000100 fffff803`80465aa0 ffff800e`e86dc9e0 fffff803`806232a0 : dxgkrnl!TdrResetFromTimeout+0x15
ffff988e`e1b4fa40 fffff803`800bd465 : ffff800e`f435f040 fffff803`85920230 ffff800e`e86dc9e0 ffff800e`e86dc9e0 : dxgkrnl!TdrResetFromTimeoutWorkItem+0x27
ffff988e`e1b4fa70 fffff803`8012a725 : ffff800e`f435f040 00000000`00000080 ffff800e`e866f080 000024ef`b59bbfff : nt!ExpWorkerThread+0x105
ffff988e`e1b4fb10 fffff803`801c886a : ffffa601`feec0180 ffff800e`f435f040 fffff803`8012a6d0 00000000`00000000 : nt!PspSystemThreadStartup+0x55
ffff988e`e1b4fb60 00000000`00000000 : ffff988e`e1b50000 ffff988e`e1b49000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x2a


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)

Seems it was the version of iLok manager i was running, the recent update has cleared all the errors on exit now.

Not the ones in the ProcDump, but you’ve gone a long way since then (also with the DAW builder :laughing: )
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.