Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • thanks for your answer and the suggested tool. I'm afraid you rather missed the point of my question - you suggest memory testing; somebody else suggested Adobe automatic software downloads. My question was; in these circumstances how do you decide what to do when there are a huge range of possibilities. Commented Mar 21, 2011 at 10:24
  • 1
    @Chris: As I said; when troubleshooting intermittent and unexplainable issues (In a none sw development situation ofcourse), if there's no log to start from, and no other markers to suggest where to start, I'd run a memory test. The logic being, it's relatively fast to run compared to trying to replicate an intermittent issue. Once ruled out then you start on the narrowing down and getting an idea as TomWij puts it.
    – Matt
    Commented Mar 21, 2011 at 11:11
  • fair enough. Commented Mar 21, 2011 at 11:16