Hello,
I have forwarded your problem/question to Stardock Support Team for their assistance. Please keep an eye on this thread for any updates. We appreciate your feedback and patience.

Basj,
Stardock Community Assistant

Hi Jaap,

You might also try controlling for Start11 and Fences by seeing if this keeps happening without either running on this computer.  If it does keep happening despite this, you could then try using a Windows Sandbox environment to test a fresh install of Windows (to identify if some other program or setting might be causing the problem).  

https://learn.microsoft.com/en-us/windows/security/application-security/application-isolation/windows-sandbox/windows-sandbox-overview

If it remains a persistent problem on your end with Start11 and/or Fences running, my take here is that your Windows log might be helpful, but probably not as extensive/useful as the WinDBG process outlined here for Crash Collection.  If you don't mind doing so, I would advise following the link basj has just shared above.

Adam McGuinness
Stardock Customer Support Specialist

I'll only disagree with the word "cause" here. 

In software (or any science based) testing, "correlation without causation" is a thing you might know.  In other words, even if there is a correlation between variables, this does not mean you can confidently say you've identified the cause of a particular issue. 

My suggestion is simply meant to narrow down the variables that may or may not be in conflict, at which point the crash dump collection process identified above might be more appropriate to investigate further. 

Adam McGuinness
Stardock Customer Support Specialist