Figure 2 illustrates the filter I used to reduce the events to just those used by the DebugDiag process. No problem, this is where the filtering comes in handy. In the amount of time it took to reproduce the error, Process Monitor had logged 100,000s of events. I started up Process Monitor and reproduced the issue. I put that to the test when I received the error message, Figure 1, from DebugDiag while trying to analyze a memory dump.įigure 1, DebugDiag error, ShellExecute failed to display the report. He mentioned that there is no problem which Process Monitor cannot be used to help resolve. I attended TechReady15 and took part in a session from Mark Russinovich, the creator of Process Monitor and many if not all of the System Internals tools.
0 kommentar(er)
