Troubleshooting Techniques
Thursday, November 6, 2008 16:14The primary requirement for troubleshooting is to be methodical.
Don’t panic, don’t rush. Being patient and methodical is better
than being quick and sorry. Whatever the problem, the first step is
to develop an understanding of what are the possible causes.
Using a notepad and pencil (or pen) is helpful. First, note down the
symptom. The symptom is what you see happening, not what you
think may be happening. Once you know the symptom, the next
step is to identify the possible problems that might be the cause
for this symptom. Some symptoms may be caused by a single problem.
Usually, you will not be so lucky. Most symptoms can be
caused by one or more problems. Isolate the sub-systems (this
site covers all the major sub-systems) that may be causing the
problem. Then investigate each sub-system and eliminate them
from the possible problem checklist. Look at the example troubleshooting
table below to give you an idea on how you can
approach the exercise:
If you are used to troubleshooting, you are most likely following
something similar in your head already. Once you begin to think in
terms of the various sub-systems, the chances of you not finding
your problem are very low. Over time, and with experience, you
would be doing this naturally and automatically. Of course on
paper it looks terribly boring and to tell you the truth, it is! But, it
is a good strategy to use a methodical approach in troubleshooting
rather than dive straight in, start poking around, pressing keys and
buttons blindly and then regretting it later.
After trying everything and you are at your wits end with no
solution in sight, it is time to take a step back and forget about
it for a while—attack the problem after some time with a fresh
mind.
