Hmm, I've used debugger a few times & it's always shown me the path. One thing with bsod's sometimes the bsod itself will clue you in, sometimes the error report on reboot will.
For example, my xp box is bsod'ing every twenty minutes or more at the moment. When it goes, the bsod states atidvag2.dll has caused windows to stop working and the system will be shut down.
Ati eh? Bit of a clue there. Sure enough, disable the graphics card & the system ticks along nicely albeit with 1982 graphics. Point being, corrupted files can sometimes be helpfully named. Doesn't do it everytime, but a fair few.
With the debugger, you must, must have an up to date set of symbols for it or it won't work.