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.

4
  • 6
    +1 Because this question can be useful for me to link to in the future. Commented Mar 20, 2011 at 20:42
  • 2
    Sometimes, before launching into a full, methodical problem solving approach, you should attempt a sweep of common low-hanging fruit: Run a full spyware scan, search the windows log for unexpected shutdowns and see what (if any) problems preceded it, check the disk space situation, run check disk, give Sysinternal's Autoruns a quick scan for unfamiliar/suspicious software. Have a simple set of tools to run which can quickly identify a large variety of hardware and software issues. If they find nothing, you've wasted little time and can commence a more thorough process.
    – Alain
    Commented Mar 21, 2011 at 13:15
  • 1
    Also, follow Mark's Blog for examples how annoying issues are troubleshooted with Sysinternals. Commented Mar 21, 2011 at 14:25
  • 1
    Good luck on troubleshooting, I would suggest to create a new question if you want more feedback to keep things organized... Commented Mar 21, 2011 at 18:31