You're probably familiar with the sinking sensation you get when a car's service engine light illuminates. That ominous, vaguely threatening feeling occurs again when your computer displays portentous and vague error messages. In both cases, drivers/users are left pondering, and maybe panicking, about the unexpected problem: What in the world went wrong? And what do I do next? Elusive Errors. Error messages aren't evil monkey wrenches that clog the gears of your computer's systems—but they are signs that something isn't quite right. Pinpointing the problem, even if you have a clearly written error message at your disposal, is not always easy because your computer is so complex, incorporating hardware, numerous programs, and an operating system that supposedly helps each of those components play nice. The next time you become livid at a vague error message, consider the multitude of challenges facing software developers. They not only have to create cutting-edge applications on tight deadlines, but they also have to make sure their product doesn't conflict with the programs and hardware components that will likely be on their customers' computers. Developers do their best to smash the worst of their software's bugs, but then the program's release date draws near, forcing companies to move forward in a hurry. Randy Camp, MusicMatch's vice president of software and research and development, says that in these situations, "programmers may forget to omit error messages created during the debugging process, or they may be overlooked because of time and money restrictions or higher-priority user-interface items." As a result, users may not only come across a vague error message, they might even see messages that programmers didn't intend for the public eye. When programmers beat their tight coding deadlines, they take a step back and try to write clear, concise error messages that help users diagnose and fix problems. But as you know, few error messages are really that helpful. One reason is that programmers just don't have the time (or enthusiasm) for creating top-notch error messages. As a result, their sloppy error messages utilize esoteric English or jumbled alphanumeric codes that mean nothing to end users. Worse yet, many error messages are composed by people who've never developed an application themselves, meaning the writers don't have an intricate knowledge of the product's inner workings. Other times, the opposite occurs—an engineer who helped build the program writes the messages, but does so in language that's of no assistance to end users. Still, unhelpful error messages are better than no error messages at all. Without them, programs would simply freeze, fail, or go berserk with zero explanation. Error messages give us a starting point for taking the first steps toward addressing problems that, if undetected, could damage valuable data. Hardware and OS errors. Your computer's hardware and OS spawn many of the messages you see, in part because the OS has such an intense job. It must coordinate the activities of all hardware and software and keep tabs on many separate OS functions, too. Programmers assure hardware and software compatibility by testing their OS with as many setups as they can, but there are always unknown configurations that cause problems. When an OS encounters unfamiliar or newly revised hardware and software, conflicts may occur due to incompatibilities, or because more than one product demands the same resources as another. There are a few OS-related errors that happen more often than others, and one is called a fatal exception error. Often called BSOD (Blue Screen of Death) errors because of the blue screen and white text that appears, fatal exception errors are the bane of all computer users, as these errors generally halt all programs and prompt users to restart their PCs. BSOD errors typically occur due to an incomplete or inefficient third-party program. Often the program in question requests system resources (such as memory) that aren't available, and if the program becomes unstable, the OS puts a stop to the process and requires you to restart your computer. Many users also see Windows protection or STOP errors, which usually occur at startup. Like fatal exception errors, protection errors freeze processes and force you to restart your PC. Protection errors happen for many reasons, such as driver conflicts, viruses and worms, a corrupted Registry, hardware malfunctions, and more. You might also encounter GPFs (general protection faults) or any number of illegal operation errors. GPFs occur due to a variety of hardware and software problems and often appear when your processor receives invalid instructions from an application. Illegal operation errors appear because the computer can't complete the instructions it receives, and thus, it stops the process and alerts you with an error.|
 These days, when a program crashes, Microsoft wants to know about it. When a programming problem shuts down an application, you may see a dialog box like this one, which offers to send data about the error to Microsoft's software development teams. | Other software errors. Just like OS programmers, the people who develop third-party programs must create software that will work with a sprawling list of hardware, as well as popular programs from other companies. That's a daunting task, in part because each program on the end user's computer needs to share the CPU, RAM, and other system resources. It's a failure to anticipate problems that generate errors. "In general, warning and error messages are used to indicate that a situation has occurred that was not expected," says Russ Miller, director of software development for Corel. Sometimes, an error message will offer a generalized explanation that the program isn't compatible with a hardware component, but that imprecise message won't necessarily help you fix the problem. Other messages may indicate that system resources aren't available because another program is working, but you still might not have a clue on how to resolve the conflict. These unclear errors are notorious for their unhelpfulness, at least to ordinary home users; nevertheless, many error messages offer more help than those of the past. For example, if you can't save a file in a specific format, a program might well explain why. And if an application is starved for memory, there's a good chance an error message will give you an accurate heads up. Things should continue to improve as companies provide a more aggressive reaction to errors. Microsoft lets users send error reports via email, hoping to glean information that will help the company's products work better in the future. Miller indicates Corel's applications offer a similar capability and says, "the software offers to transmit a snapshot of related system data via email that enables programmers and testers to get to the root of problems as quickly as possible and ensure the top concerns are addressed in future updates." What You Can Do. When you see an error message, be sure to make a copy of it. De-pending on the circumstances, you may be able to highlight the error message and its description using your mouse pointer. Then press CTRL-C to copy the message, open a word processing program, and press CTRL-V to paste the information into a blank document. Save the file for future reference. If you can't copy and paste the message, get out your trusty pen and notepad and jot down the message in its entirety. After you copy the error message, try re-starting your computer to see if that resolves any problems you experienced. Often, simply clearing your PC's memory with a restart will set things back to normal with no extra effort from you. Recurring error messages are more frustrating because of their persistence, but depending on the situation, you might be able to resolve such errors very quickly. Check out the following tips to combat common errors. New installations. Many errors surface soon after you install new hardware or software because conflicts often occur between the new product and previously installed components. To put an end to such messages, you might be able to uninstall the program or hardware (and hardware drivers) and then restart your computer to an errorless state. If you do find that removing a new product eliminates errors, you might have to do some research to figure out the source of the conflict before you can reinstall the new product. Check the manufacturer's Web site for updated drivers, search support areas for known conflicts, and contact technical support for assistance. Sometimes tech support gurus can help you tweak a setting to end software conflicts. Let it finish. Developing new computing habits can also limit the number of error messages you see. When you first start up your PC, let the hard drive come to a complete stop before starting a task; this lets your computer load all necessary drivers and operating system components necessary for efficient and error-free operation. The same concept works for your other programs. Let each program start up or shut down completely before you move on to another job. Look it up. You can investigate Windows error messages on Microsoft's support site (support.microsoft.com). Click Search The Knowledge Base, select your OS, and enter part of the error message in the Search For text box. You may well find information here to help fix recurring PC problems. Just The Beginning. Now you understand a few of the reasons that perplexing and annoying error messages wind up on your monitor. You also know that such messages often occur because too many components are competing for the same system resources. You will probably never own an error-free system, but with the knowledge you absorb here, you won't panic at every error message you encounter, and your computing sessions will be less stressful and more productive. by Nathan Chandler |