Rob Hunter @robbobobbo.com · Dec 15 It pointed me to crash dumps, appeared to write parsers for them, walked me through WinDbg Preview steps to narrow things down. When it was time to take action, it gave instructions on disabling the offending module, and answered questions about the performance risks.
0 likes 1 replies
?
Replies
I get paid to work with computers (admittedly not PCs), so I'm smaht but there's no way I would have done this on my own. I've never touched WinDbg before, and wouldn't have taken the hours to figure it out. For the right problem space, these tools are magic.