Although the stability of Windows 2000/XP system based on NT architecture has been greatly enhanced, even Windows XP claims to "never crash", but we will still see the blue as shown in Figure 1. Alarm information, this is what is commonly referred to as the "blue screen". What is going on?
a reason Windows 2000 /XP outbreak of blue alarm
Windows 2000 /XP uses a hierarchical structure, its two layers, also known as modes, namely the user mode (User Mode) and kernel 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 and then stabilize, since due to some reasons, such as hardware conflicts, hardware problems, registry errors, virtual memory, dynamic link library file is missing, the depletion of resources and so on, this time 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 the 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 message" or "stop message."
Second, the blue alarm recognize hidden information
Windows 2000 /XP and Windows NT4 window of BSOD previous BOSD window has a very different, 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 in the window of Figure 1 seems complicated, it generally consists of the following three parts:
1. Error message
The content between "*** Stop:" to "****** wdmaud.sys" is a so-called error message, error code, custom parameter, error symbol composed of three parts, each part of the following meanings:
error code: STOP behind the hexadecimal number;
custom parameter: the error code composed of characters defined by programmers, usually It is difficult for users to understand;
Error symbol: KMODE_EXCEPTION_NOT_HANDLED
After the error symbol, a memory location and file name are also displayed here to know the memory location and source file when the error occurred. For us, the most useful thing is the previous error code information, which will be used when searching the Microsoft Knowledge Base.
2. Recommended Action
This shows the actions and steps taken by the system recommended users, such as uninstalling the program in safe mode, rolling back the driver, updating BiOS, installing patches, etc., but in most cases need to restart The system can only be considered for further operations.
3. Debug Port Information
This will show you how to set up the kernel debugger information, including whether the memory dump image has been written to the magnetic 獭 (6) 炊 炊 炊 诶 ! ! ! ! ! ! ! ! !! ?
In fact, according to the author's experience, in addition to the error code blue alert useful, but for the average user, most of the rest of the information is not much practical significance, for reference only.
In order to debug the system, after the system has a BSOP error, KeBugCheck will automatically generate a debug file named Memory.dmp, which is located in the C:WindowsMinidump folder. By default, this The size of the file is the same as the physical memory capacity of the system. We can compress the file and send it to Microsoft's technical support department to get the corresponding solution, but the file size is so huge. How to send it is a big problem, so it is very Few users really do this.
Tip: Open the "System Properties → Advanced → Startup and Recovery" window, shown in Figure 2, where you can see the "Write debugging information" GENERATION: Small memory dump, kernel memory Dump, full memory dump, none, based on the above analysis, it is recommended to select "None" here.
Third, deal with the blue alarm trilogy
Although the blue alarm window of Windows 2000/XP may display different information, or hardware reasons, or the driver and system Compatibility issues, or simply bugs in the application. First, of course, is the reason to exclude the virus, then we can deal with the following steps:
Step 1: Reboot the system
blue alert window appears, we should first consider is restarted The system, in most cases, can solve the problem after restarting the system. However, in general, it is not possible to use the "Ctrl+Alt+Del" hot start at this time, but only press the reset button to cold start, or simply restart after powering off.
When entering the system, from the "Control Panel → Administrative Tools → Event Viewer", or type "eventvwr.msc" command in the "Start → Run" box to enter the event viewer interface, as shown in Figure 3, here Focus on checking for events with type flags "Error" in "System" and "Application" based on date and time. For example, Figure 4 reports an error that a service failed to start.
Step 2: return to the last known good configuration
Windows 2000 /XP is not a reason from a blue alert, NT operating system architecture will not temper tantrums, Usually caused by updating the device driver or installing some software, sometimes even the user optimizes the system or deletes some important system files. At this time, you can restart the system and quickly press the F8 key. Select "Last Known Good Configuration", which will restore valid registry information for the HKEY_LOCAL_MacHINESystemCurrentControlSet entry in the registry, but will not resolve errors caused by driver or file corruption.
Alternatively, you can also try to press the F8 key to select boot to safe mode. If you can enter safe mode normally, it may be a driver or system service problem.
Step 3: Query error code
Make a note of the English information in the window of Figure 1, especially the error code "0x0000001E", and then access http://support from another computer. On the microsoft.com site, type "stop ***" in the "Search (Knowledge Base)" box in the upper left corner. Here, "***" indicates the error code. For the convenience of reading, of course, select "Chinese Knowledge Base". "But many times we are afraid that we can only find the answer in the "English Knowledge Base", or we can search on Google or Baidu.
If the above recipe does not solve the problem, maybe we should consider whether it is a hardware problem, Windows XP can access http://support.microsoft.com/default.aspx?scid=kb;zh- Cn;314062 View Hardware Compatibility List (HCL), Windows 2000 users can visit http://winqual.microsoft.com/download/display.ASP?FileName=hcl/Win2000HCL.txt to view the hardware compatibility list, then consider re-plugging Memory, graphics card, network card, or try to replace one by one, the more common is the memory problem or power problem, if this trick is not enough, I am afraid that you can only consider reinstalling the system or formatting the hard disk.