|
|
The need for system troubleshooting arises when an overclocking attempt is not successful. In the world of overclocking, the word successful is subjectively defined. Success, or lack thereof, is usually measured by whether or not the system boots and whether or not it remains stable over time. Symptoms of system instability include software applications that freeze, crash (with or without an error message), or otherwise produce unexpected and unwelcome results. Some users are content with a system that crashes once a day. Others require complete system stability for weeks at a time before they are satisfied. Whatever "success" means to you, it is possible to turn overclocking failures into successes by understanding what went wrong and taking the right steps to correct problems.
Overclocking can create system stability problems that would not occur at default settings. Deviations from normal (or default) temperatures, voltages, and operating frequencies of various system components can lead to instability, or even failure, after prolonged operation. To correct such problems, or to fix a system that will not boot after an overclocking attempt, it may be necessary to restore the system to its default configuration, or at least to a more stable configuration. Ways to do this include clearing the computer's CMOS data via a motherboard jumper, changing motherboard dipswitches or jumpers back to defaults, or reflashing the BIOS to force default settings. The risk of device failure is minimal if you exercise care and patience during overclocking. System instability is the larger concern. Nevertheless, failure or damage to hardware is a possibility. Troubleshooting can shed light on the causes of instability and help you get the kinks out of any overclocking attempt.
|
|