First, the reasons 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 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 may cause drivers or for some reasons, such as hardware conflicts, hardware problems, registry errors, insufficient virtual memory, loss of dynamic link library files, and exhausted resources. The application has an error and even spreads 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.
1. Error message
The content between "*** Stop:" to "****** wdmaud.sys" is the so-called error message, consisting of three parts: error code, custom parameters, error symbols, etc. Composition, the meaning of each part is as follows:
Error code: hexadecimal number after STOP;
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, a memory location and file name are also displayed here to understand 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 Actions
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, you need to restart the system. Consider further operations.
3. Debug Port Information
This shows information about how the kernel debugger should be set up, including whether the memory dump image has been written to disk and what port is used to complete this debug.
In fact, in addition to the error code is more useful in the blue alarm, for the average user, most of the rest of the information does not have much practical significance, just for reference.
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, the size of the file is Consistent with the system's physical memory capacity, 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 is a big problem, so few users Really do this.
Tip: Open the "System Properties → Advanced → Startup and Recovery" window, as shown in Figure 2, here you can see the "write debugging information" generation method: small memory dump, core memory dump, Full memory dump, none, based on the above analysis, it is recommended to select "None" here.
3. Handling Blue Alert Trilogy
Although the blue alarm window of Windows 2000/XP may display different information, either for hardware reasons or for driver and system compatibility. The problem, or simply the bug is some bug in the application. First, of course, is the reason to exclude the virus, then we can deal with the following steps:
Step 1: Restart the system when
blue alert window, we should first consider is to reboot the system, large In some cases, you 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, enter the Event Viewer interface from Control Panel → Administrative Tools → Event Viewer, or type “eventvwr.msc” in the “Start → Run” box, 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 architecture Caozuoxitong not temper tantrums, are generally Due to the update of the device driver or the installation of some software, sometimes even the user optimizes the system or deletes some important system files, you can restart the system and quickly press the F8 key to select "Last A correct configuration", this will restore the valid registry information of the HKEY_LOCAL_MacHINESystemCurrentControlSet item in the registry, but can not solve the error caused by the 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
note of the information in English Figure 1 window, especially the "0x0000001E" this error code, and then accessed from another computer http: //support. 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 or Wufajiejue 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.