View Single Post
  #2  
Old 09-06-2012, 02:10 AM
lerxst2112
Demi-God
 
Join Date: Aug 2010
Posts: 1,742
Default

Look in the logs. They are often filled with tons of great information like the last thing that was logged before the crash.

Another solution is to build with debugging information and attach the debugger to a zone that crashes often, then you will have a call stack and can tell the exact line the crash happened on as well as what led up to it.
Reply With Quote