I appreciate that you want to learn, and I can see how you'd think that 'sharing a little experience' is enough to get you started. The problem is that you don't appreciate how steep (or how high) the learning curve really is. Despite the title I have here I'm no expert, compared to the real experts on here I'm just average, but I've been working with operating system internals all my working life, and with Windows internals for decades. And you need to understand, at least at a high level, how Windows works internally because analysing a dump is often about following the function calls to determine what went wrong.
As well as enrolling in the Sysnative BSOD Academy you might want to get a copy of part 1 of the
Windows Internals book. Much of what's in there is important to know when kernel debugging. It will help you get started in debugging too, the authors use WinDbg in the book.
