Google and common sense are the best friends for solving technical problems.
Also owner forums might be useful, as well, as manuals.
I just keep trouble shooting till it works. If that doesn't work, I will research for days.
i am very fascinating about reverse engineering, also if you have some technical knowledge than you can easily got idea where system has gone wrong by google about its consenquences and finally if possible then do reverse engineering on it just by opening its parts and check it manually by attaching to other system, and 90 percentage fualt solve by replacing faulty part, other needs calibration and troubleshoot from soft part also
I try and fail.
I have googled for free tutorials. I have googled the error code.
There are many ways to get solutions. Write down your answer once you find it so you don’t have to search again in the future.
It was most enjoyable reading the many ways each of you approached solving a technical problem.
Having been around computer for more years than I am willing to share I have often shared with my IT students the following solution which fixes most hardware and or software problems.
1) Turn it Off, (not half off or kinda off but totally and complete off) at this point it is OK to double check. With experience this will come second nature.
2) Go have a beverage, Coffee, Coke, Pepsi are all fine as long as it has some caffeine in it. I discourage the use of Redbull or Mother both can create a undeserved sense of self importance which can come back and bite you on the ass down the track.
3) Take your time, This reminds everyone including the problem being solved who is in charge. If you rush and fix the problem quickly, well it musten't have been very complicate after all.
4) Once you are refreshed and have confirmed that no one has intervened while you were having your beverage. Turn this device back on. Once again make sure it is fully turned on, not kinda on.
You will be surprised how often this procedure has a positive outcome.
Depending on the issue I have depends on the way I solve it.
For hardware issues I will generally Google the issue first to see if it is a common issue or if there is a driver/firmware update. If this fails I will try to remove the troublesome hardware and check in another machine to see if the hardware itself has failed.
For software issues I will Google the error code and use forums or the software developers own forums to find fixes or workarounds. As a last resort I will make sure I have backed up all important documents to an external drive and then depending on the severity of the software issue, I will either refresh or clean install my OS. The OS depends on whether it is my windows pc or linux laptop that is having issues.
What will we do without Google????
Googling is a good start.
Stack Overflow tends to have good discussions.
Tutorials usually help me understand ideas better.
Ryan Bates had a good one for Ruby on Rails, but it’s a bit outdated now.
If Google can't help anymore, then trial and error until it works... even if it takes days.
Unfortunately, Google often does not find what you are looking for anymore. I'm on a few German-language forums, which usually helps a lot better than torturing yourself through wrong search results for hours.
By the way:
Hi, I'm the new one.
Troubleshooting steps :
1. Google the problems
2. Search the solutions on forum
3. Call the maintenance department
From my side in major cases I am copying the message with error and search using this key expression. In 90% this is usable case.
But when I do not found anything it means this is very rare problem or you use unique software. The best way to ask about this on the forums or other place with community of your software
I typically use Google when I hit an issue, but I’ve found out about SteamWorks about a year ago and they have a wealth of information from Windows Servers and System Center to help with PHP and other development languages.