print barcode labels c# Finding Troubleshooting Information in Visual C#

Paint Quick Response Code in Visual C# Finding Troubleshooting Information

Each Stop error requires a different troubleshooting technique . Therefore, after you identify the Stop error and gather the associated information, use the following sources for troubleshooting information specific to that Stop error:

The section titled Common Stop Messages later in this chapter This section is intended as a reference for troubleshooting Stop errors; however, it does not include every possible Stop error . If the Stop error number you are troubleshooting is not listed in Common Stop Messages, refer to the Debugging Tools For Windows Help . Microsoft Debugging Tools For Windows Help Install Microsoft Debugging Tools For Windows and consult Help for that tool . This Help contains the definitive list of Stop messages, including many not covered in this chapter, and explains how to troubleshoot a wide variety of Stop errors . To install Debugging Tools For Windows, visit http://www.microsoft.com/whdc/devtools/debugging/ .

Microsoft Knowledge Base The Knowledge Base includes timely articles about a limited subset of Stop errors . Stop error information in the Knowledge Base is often specific to a particular driver or hardware feature and generally includes step-by-step instructions for resolving the problem . Microsoft Help and Support For related information, see Microsoft Help and Support at http://support.microsoft.com . Microsoft Product Support Services If you cannot isolate the cause of the Stop error, obtain assistance from trained Microsoft Product Support Services personnel . You might need to furnish specific information and perform certain procedures to help technical support investigate your problem . For more information about Microsoft product support, visit http://www.microsoft.com/services/microsoftservices /srv_enterprise.mspx .

Stop messages report information about Stop errors . The intention of the Stop message is to assist the system administrator in isolating and eventually resolving the problem that caused the Stop error . Stop messages provide a great deal of useful information to administrators who understand how to interpret the information in the Stop message . In addition to other information, the Stop message includes the Stop error number, or bugcheck code, that you can use to find or reference troubleshooting information about the specific Stop error in the section titled Common Stop Messages later in this chapter . When examining a Stop message, you need to have a basic understanding of the problem so that you can plan a course of action . Always review the Stop message and record as much information about the problem as possible before searching through technical sources . Stop messages use a full-screen character mode format, as shown in Figure 32-1 .

As shown in Figure 32-1, a Stop message screen has several major sections, which display the following information:

Bugcheck Information Recommended User Action Technical Information Driver Information (if available) Debug Port and Dump Status Information

to fully display the entire Stop message. In such a case, only the first line may be visible, or the screen may be black. Wait several minutes to allow the memory dump file to be created and then use the standard troubleshooting techniques described in this chapter.

The Bugcheck Information section lists the Stop error descriptive name . Descriptive names are directly related to the Stop error number listed in the Technical Information section .

The Recommended User Action section informs the user that a problem has occurred and that Windows was shut down . It also provides the symbolic name of the Stop error . In Figure 32-1, the symbolic name is BUGCODE_USB_DRIVER . It also attempts to describe the problem and lists suggestions for recovery . In some cases, restarting the computer might be sufficient because the problem is not likely to recur . But if the Stop error persists after you restart the operating system, you must determine the root cause to return the operating system to an operable state . This process might involve undoing recent changes, replacing hardware, or updating drivers to eliminate the source of the problem .