Answer:
Take note of problems as soon as they appear. For example, if Windows or an application presents an error message (regardless of whether they freeze or shut down), write down any information the message provides. Even if there’s only an error code, document it, as it could prove helpful soon. If Windows or an application freezes or shuts down and doesn’t display an error message, write down the details of the crime scene, including what froze or shut down, any open applications at the time of the problem, your actions when the problem occurred (such as if you were saving a file), and any peripherals (i.e. mouse, printer) in use. If a peripheral is acting strangely, write down a description of its behavior (for example: “mouse pointer flits erratically around the screen”). Otherwise, it’s possible to get so deep into troubleshooting that you forget what the original problem was to begin with.
Think about any changes you made lately to your computer. Did you recently install hardware, software, or patches? Did you update device drivers? Did you make changes to your Windows configuration? Write down any recent changes you can remember, even if you think the changes couldn’t have any effect on your current problem.
Because looking for the source of a problem sometimes uncovers other problems, it’s important to stay focused throughout the process. Sometimes the problem’s source resides in the last place you look, so it’s also essential to prepare yourself for anything. Although you might get lucky and uncover the trouble in minutes, some troubleshooting requires substantial digging in several areas of Windows.
Finally, develop a sensible strategy that will help you solve the problem. If a hardware component appears to be malfunctioning, check the hardware utilities in Windows first, but be fully prepared to check other resources, as well, because software problems can negatively affect hardware, just as hardware problems can disrupt software. Write down what you plan to examine because it’s easy to become sidetracked when you’re exploring multiple areas. Then, when you find the source of the problem (along with a solution), make sure you document it for future reference.
To learn more about diagnosing software and/or hardware problems, refer to the article in the "See Also:" section below.
|