{"id":4457,"date":"2011-10-09T21:04:25","date_gmt":"2011-10-10T04:04:25","guid":{"rendered":"http:\/\/www.bspcn.com\/2011\/10\/09\/top-10-tactics-for-diagnosing-and-fixing-your-sick-technology\/"},"modified":"2011-10-09T21:04:25","modified_gmt":"2011-10-10T04:04:25","slug":"top-10-tactics-for-diagnosing-and-fixing-your-sick-technology","status":"publish","type":"post","link":"http:\/\/localhost\/wordpress\/2011\/10\/09\/top-10-tactics-for-diagnosing-and-fixing-your-sick-technology\/","title":{"rendered":"Top 10 Tactics for Diagnosing and Fixing Your Sick Technology"},"content":{"rendered":"
Written by lifehacker<\/a><\/p>\n Technology is great until it breaks and you have to spend hours trying to figure out what’s wrong before you can even fix the problem. Often times the entire ordeal will take even longer because you’ve failed to consider the obvious, or a particular strategy that worked in the past. Here are our top 10 tactics for diagnosing and solving the many problems that occur with your computers, smartphones, web sites, and more.<\/p>\n Thanks to everyone on Twitter, Facebook, and Google+ who helped out with suggestions for this post!<\/i><\/p>\n <\/em><\/p>\n <\/p>\n 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\u2014as great as it is\u2014can 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.<\/p>\n <\/p>\n <\/p>\n <\/p>\n 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. <\/p>\n (Thanks for the tip, Brian!<\/i>)<\/p>\n <\/p>\n <\/p>\n 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\u2014or 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.<\/p>\n <\/p>\n <\/p>\n <\/a>When a web site isn’t working, sometimes it’s not the internet. Sometimes it’s just you. How can you tell? You could ask a friend or just use something like Down for Everyone or Just Me?<\/a> Go there and type in the web site in question. DFEOJM.com will let you know if it can reach the page or not. If it can’t, it’ll report that it’s down for everyone. If it can, you might want to restart your router and, if necessary, start looking into other possible causes.<\/p>\n <\/p>\n <\/p>\n 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 lede 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<\/a>. If you’re on Mac, just open the Console applications in Hard Drive \u2014> Applications \u2014> Utilities. If you do<\/em> understand log files, then you’re in really great shape (and probably do not need to be reading this tip.)<\/p>\n (Thanks for the tip, Dan!<\/i>)<\/p>\n <\/p>\n <\/p>\n Regular maintenance is important, whether you’re on a Mac<\/a>, Windows<\/a>, or Linux<\/a> PC. Sometimes the issue you’re seeing is the result of a permissions error, a bad cache file, hard drive fragmentation, a messy registry, and so on. Obviously these issues don’t apply to every operating system, but performing maintenance tasks for your specific OS (guides linked earlier in this paragraph) can often clear up the problem. And, if you make these maintenance tasks a recurring duty, you may not run into some issues at all. <\/p>\n <\/p>\n <\/p>\n Whether you need to fix an issue on your own computer when you’re away or you’re helping out a friend or family member,setting up remote access<\/a> makes a huge different in the troubleshooting process. When you can’t be there, it’s as close as you can get. There are many options<\/a>, too. You can simply set up VNC<\/a> or use a service<\/a> to take the hassle out of the process. Many chat apps like Skype and iChat have screen sharing features as well, so you’re bound to be able to get through if someone else is around. When you can’t be there to troubleshoot the problem yourself, remote access is the next best thing. <\/p>\n <\/p>\n <\/p>\n <\/p>\n Google’s great, but it’s not the best place to go for everything<\/em>. More geek-oriented search engines like DuckDuckGo<\/a> 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<\/a> instead. <\/p>\n (Thanks for the tip, Kevin!<\/i>)<\/p>\n <\/p>\n <\/a>When you’re not sure what to do or who to ask for help, there are places online designed to solve your problems. As mentioned in #3<\/a>, there are plenty of specific forums, but sites like StackExchange<\/a> offer a focused format for asking questions and getting answers on a variety of topics. (We have a few other suggestions as well<\/a>.) If none of those sites do the trick, you can always email us<\/a>. We’re always on the lookout for good Ask Lifehacker topics, so if your issue is broad enough it may be a good problem for us to solve for you. Alternatively, our Help Yourself<\/a> and Open Thread<\/a>s are good places to ask each other for assistance on a more specific issue.<\/p>\n (Thanks for the tip, Wagner!<\/i>)<\/p>\n <\/p>\n <\/p>\n 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\u2014restarting 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. <\/p>\n (Thanks for suffering through iPod troubles for this one, Whitson!<\/i>)<\/p>\n <\/p>\n <\/p>\n Bonus: Balancing Sasuke – The McDonalds toy that became an internet sensation in Japan [Xpost r\/otaku]<\/strong><\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Written by lifehacker Technology is great until it breaks and you have to spend hours trying to figure out what’s wrong before you can even fix the problem. Often times the entire ordeal will take even longer because you’ve failed to consider the obvious, or a particular strategy that worked in the past. Here are […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[],"tags":[],"_links":{"self":[{"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/posts\/4457"}],"collection":[{"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/comments?post=4457"}],"version-history":[{"count":0,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/posts\/4457\/revisions"}],"wp:attachment":[{"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/media?parent=4457"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/categories?post=4457"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/localhost\/wordpress\/wp-json\/wp\/v2\/tags?post=4457"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}10. Disable Crap You Don’t Need<\/h5>\n
9. Take a Break<\/h5>\n
8. Talk It Out with a Troubleshooting Buddy<\/h5>\n
7. Make Sure It’s Not Just You<\/h5>\n
6. Check Your Logs<\/h5>\n
5. Perform Regular Maintenance Tasks<\/h5>\n
4. Set Up Remote Access<\/h5>\n
3. Use Alternative Search Engines When Looking for Help<\/h5>\n
2. Hit Up Helpful Q&A Web Sites<\/h5>\n
1. Restart<\/h5>\n