I did say I won't post anymore, I just can't help myself!!!
Here is an alternative to using debugging tools for windows..
If still crashing even after windows update and doing what they've told you, I'd like to suggest you download Diag Tool, and install it to the problem PC..
http://www.microsoft.com/en-us/download/details.aspx?id=40336 The Debug Diagnostic Tool (DebugDiag) is designed to assist in troubleshooting issues such as hangs, slow performance, memory leaks or fragmentation, and crashes in any user-mode process...
Then use these instructions from this blog to generate a report...
http://blogs.msdn.com/b/chaun/archive/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process.aspx Go to the section from the mentioned blog titled:
LAUNCH DEBUGDIAG and follow all the steps in the next section titled:
SET UP A VERY BASIC CRASH RULE - they use an example against the notepad.exe process - you need to have loaded sonar and select the sonarprd.exe process instead...
Then when you've activated the rule in the steps in that section, your ready to reproduce the crash - once you do this we should have a juicy report to look over
Edit: If you can locate the existing sonarpdr.dmp you can use the DiagTool Analyzer, to do this simply run the analyser and select crash/hang/analysis option, then add data files button and navigate and add the dmp file and then hit start analysis..