Reading call stacks from minidumps believe it or not is generally not the basics as you need to know the various different types of routines in Windows, etc. Of course there is what I guess you could call general stack reading, like running a
kv and checking to see if there are any driver calls, etc, regardless of the routine it was working with.... but any further than that, you're going to need to do some reading on Windows Internals.
Here's a pretty basic call stack containing a culprit driver -
https://www.sysnative.com/forums/bs...al-information-stop-0x0000009f.html#post55305
Here's where we get a little more in-depth into the routines being called, why, what they were doing, etc -
BSOD a day - Microsoft Community
(scroll down a bit to my post)
And if you did not know already, you read stacks from bottom to top. It helps to know routines as you can analyze further and come to conclusion based on the various routines being called.