Kent Sandvik Posted October 26, 2010 Share Posted October 26, 2010 http://reviews.cnet.com/8301-13727_7-10330727-263.html Recommended reading in case you don't know heads or tails about crash reports. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted October 26, 2010 Share Posted October 26, 2010 Great Kent, thanks a lot for that link! Quote Link to comment Share on other sites More sharing options...
Kent Sandvik Posted October 26, 2010 Author Share Posted October 26, 2010 Thx. And yes, think like Sherlock Holmes when looking through mysterious crash reports. Look at the stack that crashed (or sometimes you need to do a more holistic investigation.) Look for specific strings that might indicate a third party driver/plug-in or something else meaningful. That's usually 80% of the work for then a possible resolution by elimination. Quote Link to comment Share on other sites More sharing options...
David Nahmani Posted October 26, 2010 Share Posted October 26, 2010 Also, google is your best friend. If you see a chain of characters you don't recognize in the crashed thread, copy and paste it into google, see what you find. If all the results point to a very specific plug-in, you know who the culprit is. Quote Link to comment Share on other sites More sharing options...
ptrickf Posted October 26, 2010 Share Posted October 26, 2010 good shout guys - thanks Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.