
10. Disable Crap You Don’t Need

When something goes wrong, it’s probably your fault. Computers certainly have their issues all on their own, but more often than not you’re going to cause a problem yourself. For example, AdBlock — as great as it is — can cause web sites to look like they’re not loading properly (or at all). It can prevent video playback if you have video ad blocking enabled, too. It should work, in general, but it’s not perfect and screws up from time to time. The same goes for any drivers or extensions in your computer. Sometimes you’ll install something incompatible by accident. Keep track of what you do and look at the third-party stuff you’re using to test and see if it’s causing the problem. Often times you can figure out which extension or driver (or whatever) is the problem by going down the list and considering if it relates to your issue.
9. Take a Break

If you’re working on a frustrating problem for more than 10 minutes, it’s probably a good time to take a break. Take a walk, get a cup of coffee, or do something else that will take your mind off the issues. Focus is only good when it won’t lead to an aneurism. Sometimes you just have to take a step back so you can approach the issues a bit later with a fresh perspective. It can be hard to do, but it’s often necessary.
8. Talk It Out with a Troubleshooting Buddy

When you’re stuck and don’t know what to do next, sometimes the best way to figure it out is to talk about it with someone else. Under ideal circumstances you have a troubleshooting buddy you can bother to discuss the problem and hopefully get some suggestions as well. If not, non-techies aren’t so bad either. Discuss the issue with them. Explain it to them in terms they’ll understand. It doesn’t matter so much if they can offer any help. The fact that they’re listening and you’re thinking about the problem in different terms can often lead you towards a solution — or at least the beginnings of one. If you’re stuck and don’t know what to do, stop searching online and talk it out. After a few minutes you should have some new ideas to try.
7. Make Sure It’s Not Just You

6. Check Your Logs

Logs are your friend, even if you don’t know half of what they’re saying. When they seem like a foreign language, even a quick glance can tell you what might be causing the problem. You might not understand the error codes or any of the details, but you should be able to see if the error pertains to a specific application or task. This will, at least, give you a lead to investigate so you can focus on discovering what the problem really is. If you’re running Windows, here’s a tutorial on finding your log files. If you’re on Mac, just open the Console applications in Hard Drive > Applications > Utilities. If you do understand log files, then you’re in really great shape (and probably do not need to be reading this tip.)
5. Perform Regular Maintenance Tasks

4. Set Up Remote Access

3. Use Alternative Search Engines When Looking for Help

Google’s great, but it’s not the best place to go for everything. More geek-orientated search engines like DuckDuckGo tend to turn up better results when you’re looking for troubleshooting assistance. When you’re trying to find someone else with your problem, you want a search engine that’s going to dig up plenty of forum posts with discussions and, hopefully, solutions. If your primary search engine isn’t turning up what you want, try DuckDuckGo instead.
2. Hit Up Helpful Q&A Web Sites

1. Restart

Seriously. We often forget to do it and it regularly solves the problem. It doesn’t matter if it’s an old Super Nintendo, a brand new laptop, or your smart or dumb phone — restarting is, in most cases, the first thing you should try when there’s a seemingly unsolvable problem. Remember to do it and save yourself a lot of trouble.




















Dre
Sunday, October 9, 2011 at 10:04 AMThere’s an easier to remember Down or Just Me site: doj.me :)
Dre
Sunday, October 9, 2011 at 10:06 AMOh, and you put 3 twice.
poltak
Sunday, October 9, 2011 at 10:29 AMOr just install Linux :\
Mike
Monday, October 10, 2011 at 10:32 AMYeah…I’ve *never* had issues with a Linux machine ;)
Sam
Sunday, October 9, 2011 at 10:31 AM“This will, at least, give you a lede”
lede? Seriously?
Logan Booker
Sunday, October 9, 2011 at 1:08 PMThanks, this has been fixed.
Bob
Sunday, October 9, 2011 at 12:16 PMRestart. Genius.
Nathan
Sunday, October 9, 2011 at 10:56 PMRestarting very rarely solves any problem, it just pushes it off to another time. It also destroys the state, so you cannot probe it to find out what’s actually happening, and fix it.
lakeman
Monday, October 10, 2011 at 12:05 AMsystem restore frequently works on windows
Stephen
Monday, October 10, 2011 at 12:39 PMWhere’s “Hit it”?
blackhuey
Monday, October 10, 2011 at 1:54 PM#8: we used to have a broom in the corner of the office. If any of the programmers had a problem, they would go and “tell it to the broom”. The simple act of explaining the problem (even to an inanimate object) often gave them a flash of insight to solve it.