11-06-2011, 02:14 PM
The proper way is to attach a debugger and let that handle the problems.
So, download OllyDbg (a debugger). Well use it to catch the crash, and give us the information we need. Once downloaded, extract somewhere permanent (like C:\ollydbg). For as long as its setup, you should never move or rename this folder, otherwise it wont be able to catch any crashes for us!
Now run OllyDbg (you can say "yes" to removing the old PSAPI DLL). At the top, click on the menu "Options" and then select "Just-in-time debugging".
Hit the first button ("Make OllyDbg just-in-time-debugger"), and then hit "Done".
You can now exit OllyDbg, and proceed to trigger (or wait for) the next crash. When it crashes, Windows should ask you what to do - we want to "Debug" the server (or client!), so select "Debug" as shown below:
Finally, OllyDbg will appear - but its containing windows may not be fully visible. If theyre not shown as in the screenshot below, drag them out so theyre similar. Also note my comment in the below screenshot: scroll up 3 or 4 lines, so that we can see the code directly prior to where it crashed at.
Now youre good to take a screenshot and post it in your help thread!