Win 2000/XP Blue Screen Solution

The reason why Windows 2000/xp blue alert

Windows 2000/XP has a hierarchical structure, with two layers known as mode, user mode and kernel mode (Kernel mode), where applications cannot directly access hardware devices, and can only be accessed directly with the help of a driver.

However, even if the NT architecture is stabilized, due to some reasons, such as hardware conflicts, hardware problems, registry errors, low virtual memory, loss of dynamic link library files, exhaustion of resources, and so on, this can cause drivers or applications to be wrong, or even to the kernel layer. In this case, Windows aborts the system and starts the feature named Kebugcheck, which, when checked for all interrupted processing processes and compared to the preset stop code and parameters, turns blue and displays the appropriate error messages and fault prompts. Because this phenomenon actually means a panic, it is often referred to as "Blue screen of Death" (BSOD), also known as "Stop Information" or "Stop information."

Ii. understanding hidden information in blue alerts

Windows 2000/xp's BSOD window is significantly different from Windows NT4 's previous Bosd window, with the biggest difference being that the NT BSOD window includes only one generic Stop message code, but Windows 2000/ XP's BSOD includes two types of stop and hardware messages, which are error messages when a software error that cannot be recovered is found, which is the error message that occurs when a serious hardware error is found.

Although the information in Figure 1 Windows looks complex, it is generally composed of three parts:

1. Error message

In the "* * * Stop:" to "Wdmaud.sys" between the content is called the error message, by the error code, custom parameters, error symbols, such as three parts, the meaning of each part is as follows:

Error code: 16 digits after the stop;

Custom parameters: The composition of the error code characters, defined by the program personnel, the general user is difficult to understand;

Error symbol: KMODE_EXCEPTION_NOT_HANDLED

After the error symbol, there is also a memory location and file name that shows you the memory location and source file when the error occurred. The most useful thing for us is the previous error code information that will be used when searching the Microsoft Knowledge Base.

2. Recommended operation

This shows the actions and steps that the system recommends to the user, such as uninstalling the program in Safe mode, rolling back the driver, updating the BIOS, installing patches, and so on, but most of the time the system needs to be restarted before any further action can be considered.

3. Debug port Information

This will show you how to set the kernel debugger's information, including whether the memory dump image has been written to disk, and what port to use to complete this debugging.

In fact, according to the author's experience, the blue alarm in addition to the error code more useful, for ordinary users, the rest of the majority of information does not have much practical significance, only for reference.

To debug the system's needs, after a bsop error occurs, Kebugcheck automatically generates a debug file named Memory.dmp, which is located under the C:windowsminidump folder, which, by default, is the same size as the system's physical memory. We can compress the file and send it to Microsoft's technical support to get the solution, but the size of the file is so huge, how to send it is a big problem, so few users really do that.

Tip: Open the system properties → advanced → startup and recovery window, where you can see how write debug information is generated: small memory dumps, core memory dumps, full memory dumps, none, and for the reasons above, it is recommended to choose none here.

Iii. handling of the Blue Alert trilogy

Although the Windows 2000/XP Blue Alert window displays information that may be different, either for hardware reasons, or for driver-system compatibility issues, or simply for some bugs in the application. First of all, of course, the reason for the virus elimination, and then we can follow the following steps to deal with:

Step 1th: Reboot the system

When the Blue Alert window appears, the first thing we should consider is restarting the system, which will solve the problem in most cases after restarting the system. However, generally at this time has been unable to "Ctrl+alt+del" hot start, and can only press the reset button cold start, or simply power off after the power-on.

When you enter the system, from the control Panel → administrative tools → event viewer, or type the "eventvwr.msc" command in the start → run box, enter the Event Viewer interface, where you will focus on the events in system and application that have the type flag as "error" based on the date and time. For example, Figure 4 reports an error that a service failed to start.

Step 2nd: Revert to the last Known Good Configuration

Windows 2000/XP Blue alerts are not for no reason, the NT architecture of the operating system will not be angry, generally due to the updating of device drivers or the installation of some software caused, and sometimes even the user to optimize the system or delete some important system files caused by, You can restart the system and quickly press F8 to select Last Known Good Configuration, which restores valid registry information for the Hkey_local_machinesystemcurrentcontrolset entry in the registry. However, the error caused by a corrupted driver or file cannot be resolved.

Alternatively, you may try pressing the F8 key to select boot to Safe mode, and if you are able to enter Safe mode correctly, it may be a problem with the driver or system service.

3rd Step: Query error code

Write down the English information, especially the "0x0000001E" error code, then from another computer to access the site, in the upper-left corner of the search (KB) box, type "Stop * * *", where the "* * *" indicates the error code, for the convenience of reading, of course, generally choose the "Chinese Knowledge Base", But many times we can only find the answer in the English knowledge base, or we can search on Google or Baidu.

If the above is still not a problem, perhaps we should consider whether it is a hardware issue, access to the View Hardware Compatibility List (HCL), Windows 2000 users can access the filename=hcl/ Win2000HCL.txt View the Hardware Compatibility List, and then consider reseating the memory, video card, network card, or try to replace each one with the substitution method, more common is the memory problem or power problem, if this is not enough, I am afraid I can only consider reinstalling the system or the format of the hard drive.