When I read the minidump file with windbg, I can get the information about which driver caused a bsod. There is even an offset shown like:
PhysMem!DriverEntry+109
the callstack shows:
PhysMem!DriverEntry+0x109
How can I figure out with this information, where in my code the cause is? I already made a map file, but now I am missing the link with the information.
Or is there another simple way to locate the cause with windbg and a symbols file (.pdb)? By the way, the bsod is generated at another pc, is that a problem?
TIA, Frank