16 Jan
2021
16 Jan
'21
12:52 a.m.
Forgot to add that to find out what the cause is the easiest way is probably having the installed image configured in a way that it'll write full kernel memory dumps to disk and then use !analyze -v in WinDbg on that generated kernel dump. At least that's what I remember from more than 1.5 years ago, so some of the info might not be 100% accurate.
Regards, Felix