Stop Analysis of Blue Screen of Death in Windows 2000

Win2000 may be an epoch-making operating system, but it still can't avoid the Blue Screen of Death. The purpose of this paper is to solve the BSOD problem and give a solution to how to deal with the general blue screen problem.

Introduction

What is the Blue Screen of Death (BSOD) problem?

BSOD is the error message displayed on the background of the blue screen. Generally this kind of error message is serious enough to crash your entire operating system, you only have the option to restart the cold boot.

Stop Messages and Hardware Messages

The BSOD of Win2000 and the previous BSOD message of NT4 are completely different. The biggest difference is that the BSOD in NT contains only one generic stop message type (the actual error code), but Win2000's BSOD contains two message types: stop message and hardware message. The stop message refers to the error message that is generated when the win2000 kernel finds a software error that it cannot recover. Hardware messages are error messages that are generated when Win2000 finds a serious hardware conflict.

Analysis of BSOD

BSOD can be divided into separate parts, each part containing valuable error handling information. These sections include:

1. The bug check section: This is the location of the BSOD that contains the actual error message. In this part, you should pay attention to the error code (that is, the hexadecimal number after the word <;Stop”) and the error symbol (the word immediately following the error code)

2 Recommended User Actions section: This section often contains some general instructions on how to correct the wrong steps

.

3, debug port information section: This section contains information on how you should set up your kernel debugger. The kernel debugger is a tool that allows you to manually connect to your computer and debug your process.

Stopping the four types of information

When the program or the driver has an uncontrollable error message or attempts to execute an illegal instruction, the system will stop the error message. This information usually consists of four types.

1, regular stop message: stop message when using normal win2000

2, installation stop message: stop message during the installation of win2000, usually exists in your system Caused by hardware devices that are not compatible with 2000.

3, executable program installation stop message: indicates the stop message that occurred in the fourth phase (execution program part) during the 2000 installation process.

4. Software Trap Stop Message: A stop message that occurs due to an error trap in the software and when the program attempts to execute an illegal instruction.

Regardless of whether win2000 is by far the greatest operating system or not, it can't be without errors. At least we know that in 2000, BSOD still exists. The following is a more detailed description of it:

The following is a specific example of BSOD:

*** Stop: 0x0000001E (0xF24A447A, 0X00000001, 0X0000000)

KMODE_EXCEPTION_NOT_HANDLED

*** Address F24A447A base at f24A0000, DateStamp 35825ef8d - wdmaud.sys

If this is the first time you've seen this Stop error screen, restart your computer.
< If this screen appears again, follow these steps:

Check to be sure you have adequate disk space. If a driver is identified in the

Stop message, disable the driver or check with The manufacturer for driver updates.

Try changing video adapters.

Check with your hardware vendor for any BIOS updates. Disable BIOS memory options

such as caching or shadowing. If You need to use Safe Mode to remove or disable

components, restart your computer, press F8 to select Advanced Startup Options,

and then select Safe Mode.

Refer to your Getting Started manual for more information on troubleshooting Stop errors.

Kernel Debugger Using: COM2 (Port 0x2f8, Baud Rate 19200)

Beginning dump of physical memory

Physical memory dump complete. Contact your system administrator or technical support group.

According to this specific example, follow the four parts of BSOD above, which are introduced one by one:

Bug check section:

This is the location of the BSOD that contains the actual error message. It looks like the following code:

*** Stop: 0x0000001E (0xF24A447A, 0X00000001, 0X0000000)

KMODE_EXCEPTION_NOT_HANDLED *** Address F24A447A base at f24A0000, DateStamp 35825ef8d - wdmaud.sys < Br>

where the error code is a hexadecimal number immediately following Stop, where it consists of the other four digits.

The error symbol refers to the KMODE_EXCEPTION_NOT_HANDLED that follows.

In some BSOD error messages, a memory location and file name appear after the error symbol. This information tells the location in memory and which file caused the error to occur when the error occurred. Of course you can see which information is determined by which stop message type. In some practical applications, you can only see the first line above. And here is usually the problem caused by the display service. Recommended user action part: