Practical solutions for Windows 2000/XP blue screen

Although the stability of the Windows 2000/XP system based on the NT architecture has been greatly enhanced, and even Windows XP claims to be "never crashed", we will still see the blue alarm information shown in 1 from time to time, this is what we usually call "blue screen". What is going on?

I. Causes of blue alarms in Windows 2000/XP

Windows 2000/XP adopts a hierarchical structure. Its two layers are also called the mode, namely the user mode and the kernel mode.ProgramYou cannot directly access the hardware device. You can only access the device directly by using the driver.

However, even if the NT architecture becomes more stable, due to some reasons, such as hardware conflicts, hardware problems, registry errors, insufficient virtual memory, loss of Dynamic Linked Library files, and resource depletion, in this case, the driver or application may encounter errors, which may even affect the kernel layer. In this case, Windows will stop the system running and start the function named kebugcheck. By checking all the interrupted processes, and with the predefined stopCodeAfter comparison with the parameter, the screen will turn blue and the corresponding error message and fault prompt will be displayed. Because of this phenomenon, it actually means a crash, therefore, it is often referred to as "blue screen of Death" (bsod), also known as "Stop Information" or "Stop Information ".

2. Recognize the hidden information in the blue alarm

The Windows 2000/XP bsod window differs greatly from the bosd window before Windows NT4. The biggest difference is that the bsod window of NT only contains a common stop message code, however, Windows 2000/XP bsod contains two types of messages: Stop messages and hardware messages. The former is the error message generated when an unrecoverable software error is found, the latter is the error message generated when a serious hardware error is found.

Although the information in the window in Figure 1 looks complex, it generally consists of the following three parts:

1. error message

Go to "* Stop:" To * wdmaud. "sys" is a so-called error message, which consists of three parts: Error code, custom parameters, and error symbols. The meaning of each part is as follows:

Error code: hexadecimal number after stop;

Custom parameters: the composition of error code characters, which are defined by programmers and hard to understand;

Error code: kmode_exception_not_handled

After the error symbol, a memory location and file name are displayed. You can find out the memory location and source file when an error occurs. For us, the most useful information is the previous error code, which will be used when searching the Microsoft Knowledge Base.

2. Recommended operations

The recommended operations and steps are shown here, such as uninstalling the program, rolling back the driver, updating the bios, and installing patches in safe mode, however, in most cases, You need to restart the system before further operations can be considered.

3. debug port information

The information on how to set the kernel debugger is displayed, including whether the memory dump image has been written to the magnet otscmd! ?

In fact, based on the author's experience, in addition to the error code, the blue alarm does not have much practical significance for common users.

To debug the system, if a bsop error occurs in windows, kebugcheck automatically generates a file named memory. DMP error file, which is located in the C: windowsminidump folder. By default, the file size is consistent with the system physical memory capacity, we can compress the file and send it to the Technical Support Department of Microsoft to obtain the corresponding solution. However, the size of the file is so huge that how to send it is a big problem, therefore, few users actually do this.

Tip: Open the "System Properties → advanced → start and fault recovery" window, as shown in 2. Here you can see how to generate "Write debugging information: small memory dump, core memory dump, full memory dump, and none. Based on the analysis above, we recommend that you select "NONE" here ".

Iii. Process blue alert Trilogy

Although the blue alert window for Windows 2000/XP may display different information, either for hardware reasons, driver and system compatibility issues, or for some bugs in the application. First of all, we will eliminate the cause of the virus, and then we can proceed with the following steps:

Step 2: restart the system

When the blue alarm window appears, we should first consider restarting the system. In most cases, the problem can be solved after the system is restarted. However, in this case, you cannot use "CTRL + ALT + DEL" to perform hot start. Instead, you can only press the reset button to perform cold start, or simply restart the instance after power failure.

When you enter the system, enter "Control Panel> Administrative Tools> Event Viewer" or "eventvwr" in the "Start> Run" box. run the MSC command to go to the Event Viewer interface, as shown in 3. Check the events marked as "errors" in the System and Application Based on the date and time, example 4: an error of Service Startup failure is reported.

Step 1: restore to the last correct configuration

Windows 2000/XP has a blue alarm for no reason, and the operating system of the NT architecture will not lose its temper. It is generally caused by updating the device driver or installing some software, sometimes it is caused by your own system optimization or deletion of some important system files. At this time, you can restart the system, press F8, and select "Last correct configuration ", in this way, the valid registry information of the hkey_local_machinesystemcurrentcontrolset item in the registry will be restored, but the error caused by driver or file corruption cannot be solved.

Alternatively, you can press F8 to select boot to safe mode. If you can enter safe mode normally, it may be a problem with the driver or system service.

Step 2: Query error codes

Remember the English information in the 1 window, especially the error code "0x0000001e", then access the http://support.microsoft.com site from another computer, in the upper left corner of the "Search (Knowledge Base) in the "box, type" Stop *** "." *** "indicates the error code, which is convenient for reading. Generally, select" Chinese knowledge base ", however, in many cases, we may only find the answer in the "English knowledge base", or search on Google or Baidu.

If the above moves still cannot solve the problem, maybe we should consider whether it is a hardware problem, Windows XP can access the http://support.microsoft.com/default.aspx? SCID = KB; ZH-CN; 314062 view the hardware compatibility list (HCL), Windows 2000 users can access the http://winqual.microsoft.com/download/display.asp? Filename = HCl/win2000hcl.txt to view the hardware compatibility list, and then you can consider re-plugging the memory, video card, and network card, or try to replace one by one using the replacement method. The common problems are memory problems or power supply problems, if this is not the case, I am afraid I can only consider re-installing the system or formatting the hard disk.