The theory behind troubleshooting looks the same no matter what you are troubleshooting. In order to be successful in your troubleshooting, you must have a structured method. The method looks like this:
Gather data about the issue.
Create a hypothesis, with the help of the collected data, about what will solve the issue.
Verify if the hypothesis is true or not.
If the hypothesis is true, go to step 8.
If the hypothesis is wrong, do some more data collection.
Create a new hypothesis.
Verify if the hypothesis is true or not (do step 5 through 7 until you find that your hypothesis is true).
Since you figured out what the root cause is, you either can or cannot solve the issue. If the issue is something you can solve, implement the solution and the issue is resolved.
Pretty basic stuff. This method can be used on anything that needs to be fixed. I used to work as a sound technician before I entered the world of computers and I used this process for troubleshooting issues...