fix
Simplify Troubleshooting with a Change Log
Posted by Lifehacker US Edition at 10:00 PM on August 7, 2008
System administrator Peter had some network troubles, but managed to resolve them by cross-referencing problem email messages to the dates in the change log—or journal of updates—he keeps.
I used that information to look through the log I keep of server and network changes and maintenance. It turns out that two months ago I made a change to the firewall rules, and the problem started the very next day. It was hard to see how this particular change would cause the machine to crash, but it was too coincidental, so I disabled that rule and restarted the firewall service. There have been no warnings, problems or crashes since. I hope you can see the value of good record keeping. If you are making changes to your network without keeping a detailed record of what you are doing and when you're doing it, it is going to be extremely difficult to diagnose problems later.

You already know how to create
The How-To Geek blog posts a truly helpful guide to figuring out what's causing Internet Explorer 7 to slow down, particularly on Windows Vista systems. Starting with running IE7 in safe mode, the guide is a boon for anyone not particularly tweak-savvy as it moves through disabling add-ons, confusing options boxes, and all the way to
Tech site CNET knows that finding the cause of a hanging or crashing application can be difficult, so they've rounded up several tips for hunting down the culprit when an application starts acting up. For example: 


