XP Blue Screen Solution Tips

Computer Shop News: First, the reason for Windows 2000/XP outbreak blue alarm

Windows 2000/XP uses a layered structure, its two layers are also called mode The user mode (User Mode) and the kernel mode (Kernel Mode), the application is unable to directly access the hardware device, and can only be accessed directly by means of the driver.

However, even if the NT architecture is stable, it will be due to some reasons, such as hardware conflicts, hardware problems, registry errors, insufficient virtual memory, dynamic link library file loss, and resource exhaustion. This can lead to errors in the driver or application, and even to the kernel layer in severe cases. In this case, Windows will abort the system and start a function called KeBugCheck. After checking all interrupted processing and comparing it with the preset stop code and parameters, the screen will turn blue and display the corresponding Error messages and fault prompts, because of this phenomenon actually means a crash, so often referred to as "Blue Screen of Death" (BSOD), also known as "STOP information" or "stop information".

Second, know the hidden information in the blue alarm

The Windows 2000/XP BSOD window is very different from the Windows NT4 previous BOSD window. The biggest difference is the NT BSOD window. Only one generic stop message code is included, but the BSOD of Windows 2000/XP contains two types of stop messages and hardware messages. The former is an error message that is generated when an unrecoverable software error is found. The latter is a serious hardware found. Error message generated when an error occurs.

Although the information may seem complicated, it generally consists of the following three parts:

1. Error message

At “ Stop:” to “ wdmaud. The content between sys & rdquo; is the so-called error message, consisting of three parts: error code, custom parameters, error symbols, etc. The meaning of each part is as follows:

Error code: hexadecimal after STOP Number;

Custom parameter: The composition of the error code character, defined by the programmer, is difficult for general users to understand;

Error symbol: KMODE_EXCEPTION_NOT_HANDLED

After the error symbol, Also shown here is a memory location and file name to understand the memory location and source files when the error occurred. For us, the most useful is the previous error code information, which will be used when searching the Microsoft Knowledge Base.