The "blue screen" phenomenon is closely related to memory size, CPU frequency, optical drive, hard disk fragmentation, etc... During the use of computers, blue screens are often encountered. There are many reasons for computer blue screen. The hardware reasons can be summarized as follows:

1. The screen shows that the system is busy, please press any key to continue...

1 , Insufficient virtual memory causes system multi-task operation errors

Virtual memory is a unique method of WINDOWS system to solve the problem of insufficient system resources. It generally requires that the remaining space of the hard disk in the main boot area is 2 times of its physical memory. -3 times. In order to make full use of the space, some enthusiasts fill their hard drives to capacity and keep in mind the demanding requirements of WINDOWS. As a result, the virtual memory has an operation error due to insufficient hard disk space, so a blue screen appears. To solve this problem is very simple, try not to fill up the hard disk, and frequently delete some temporary files and swap files generated by the system to free up space. Or you can manually configure the virtual memory, select Advanced, and transfer the default address of the virtual memory to another logical disk. This avoids blue screens caused by insufficient virtual memory.

2. CPU overclocking leads to calculation errors

Overclocking is a common thing for enthusiasts, so various failures caused by overclocking are inevitable. Overclocking itself is to achieve higher performance on the original basis, but due to overloading operations, too many internal operations are caused, causing the CPU to overheat, resulting in system operation errors. Some CPUs have better overclocking performance, such as INTEL's Celeron processor and AMD-K6-2 processor, which are relatively good, but sometimes some inexplicable errors may occur. (For example: I once tried to overclock the INTEL Celeron 300A to 450, and the floppy drive read the disk without accepting the command). The overclocking capabilities of INTEL's sub-200 CPUs and AMD-K5 are not that good. It is recommended that when a high-end CPU is overclocked, the heat dissipation work must be done well. It is best to install a large fan and some heat dissipation materials such as silica gel. As for some low-end CPUs, I suggest you not to overclock, otherwise overclocking will not achieve the desired effect but will often cause blue screens and affect the normal speed of the computer.

2. Computational errors caused by mutual incompatibility or damage of memory modules

This is the most intuitive phenomenon, because this phenomenon can often be seen when the computer is turned on. The computer cannot be started, and the screen prompts that there is a problem with the memory, asking you if you want to continue. This error is caused by physical damage to the memory or incompatibility between the memory and other hardware. At this time, the only option is to replace another memory.

3. The optical drive is opened abnormally when reading a disk.

This phenomenon occurs when the optical drive is opening data by mistake, resulting in a blue screen. This problem does not affect the normal operation of the system, just eject the CD or press the ESC key.

The above are several reasons that caused the blue screen that I encountered during computer maintenance. There may be other inexplicable problems that cause the computer to have a blue screen. In any case, when encountering this kind of problem, you should carefully analyze the cause of the problem before starting to solve it.

4. The remaining space of the hardware is too small or there are too many fragments

Since Win9X needs to use the hard disk as virtual memory when running, this requires that the hard disk must retain a certain amount of free space to ensure the program's performance. normal operation. Generally speaking, the minimum space should be more than 100MB. Otherwise, the "blue screen" may be related to the remaining space of the hard disk being too small. In addition, too many hard disk fragments can easily lead to the appearance of a "blue screen". Therefore, defragmentation every once in a while is necessary.

5. System hardware conflict

This phenomenon leads to "blue screen" which is also common. What is often encountered in practice is the setting conflict of the sound card or display card. Check whether there is a device with a yellow question mark or exclamation mark in "Control Panel" → "System" → "Device Management". If it exists, try to delete it first and restart the computer. Win9X will automatically adjust it, which can generally solve the problem. question. If it still doesn't work, you can manually adjust or upgrade the corresponding driver.

Software causes and solutions to "blue screen"

Closely related to hardware is software. Sometimes software also plays a "indispensable role" in the "blue screen" phenomenon, loading too many files. There are problems with programs and registry, incompatible software and hardware, and problems with drivers. Compared with hardware reasons, they are less easy to detect, so you need to pay more attention...

1. Loading too many programs at startup

Do not load too many applications at startup (especially if your memory is less than 64MB), so as not to exhaust system resources. Under normal circumstances, system resources should be no less than 90% after Win9X starts. It is best to maintain it above 90%. If it is lower than 70% without running any program after startup, you need to uninstall some applications, otherwise a "blue screen" may appear.

2. Applications have bugs

Some applications have flaws or errors in their design, which may conflict with Win9X or compete for resources when running, causing Win9X to be unable to allocate them. The memory address may have encountered a protective error. This kind of BUG may be unpredictable and is most common in free software. In addition, because some users are still using pirated software (including pirated Win9X), these pirated software will destroy and lose part of the source code during the decryption process, making the software very unstable and unreliable, and often leading to "blue screens".

3. Attacked by unknown programs or viruses

This phenomenon usually happens when we surf the Internet, especially when surfing. When you go to some BBS sites, your IP may be exposed and attacked by "hackers" using some software. The best way to deal with this situation is to install some defense software on your computer. Furthermore, when logging into the BBS, you need to set up security settings and hide your IP.

4. Version conflict

Some applications need to call a specific version of the dynamic link library DLL. If the old version of the DLL overwrites the new version of the DLL when installing the software, or deletes If you accidentally delete a useful DLL file when applying the program, the above call may fail, resulting in a "blue screen". You may wish to reinstall and give it a try.

5. Errors or damage in the registry

In many cases this is the main reason for a "blue screen". The registry saves important data such as Win9X's hardware configuration, application settings, and user information. If the registry has errors or is damaged, a "blue screen" is likely to occur. If your computer often displays "blue screens", you should first consider that there is a problem with the registry, which should be detected and repaired in time to avoid greater losses.

6. Software and hardware incompatibility

New technologies and new hardware are developing rapidly. If a "blue screen" often appears when new hardware is installed, it is probably related to the motherboard's BIOS or driver. The program is too old to support the hardware well. If your motherboard supports BIOS upgrades, you should upgrade to the latest version or install the latest device drivers as soon as possible.

Windows 2000 "Blue Screen" Analysis and Solutions

Win2000 may be said to be an epoch-making operating system, but it still cannot avoid Blue Screen of Death. The problem is that the "blue screen" (BSOD) of Win2000 is completely different from the "blue screen" message of previous NT4. The biggest difference is that the BSOD in NT only contains a common stop message type (which is the actual error code), but the BSOD in Win2000 contains two message types: stop messages and hardware messages. The stop message refers to the error message generated when the win2000 kernel finds a software error that it cannot recover from. It is divided into four types: regular stop message, installation stop message, executable program installation stop message, and software trap stop message. ...... Regarding the blue screen of Windows 2000, based on the phenomena and countermeasures summarized above, we will analyze it in two aspects:

Analysis of the stop information of the blue screen of death in Windows 2000

Introduction: What is a Blue Screen of Death (BSOD) problem?

BSOD is the error message displayed on the blue screen background. Usually this kind of error message is so serious that your entire operating system crashes, and you have the only option of cold booting again.

Analyzing BSOD

BSOD can be divided into several independent parts, each part contains valuable error handling information. These parts include:

1. Bug check part: This is the location in the BSOD that contains the actual error message. In this section, what you should pay attention to is the error code (which is the hexadecimal number after the word "Stop") and the error symbol (which is the word immediately after the error code)

2. Recommended actions section: This section often contains some general messages that guide you on how to correct the error.

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

The following is a specific BSOD example:

*** 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.

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

Beginning dump of physical memory

p>

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

Based on this specific example and the four parts of BSOD analyzed above, the following will introduce them one by one:

Bug check section:

This is the location in 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

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

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 when the error occurred and which file caused the error. Of course whether you can see this information depends on which stop message type. In some practical applications, you will only be able to see the first line above. This usually indicates a problem caused by the display service.

Recommended actions for users to take:

In the above example, the recommended actions for users to take are as follows:

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.

The Recommended User Action section is usually Recommended User Steps to take when encountering an error message. As you can see in the message, a BSOD may be solved by simply rebooting or clearing out enough free space. While such methods may occasionally work, the actual solution to BSOD is often far more complicated.

Debug Port Information Section:

This section contains information on how you should set up your kernel debugger. I will introduce in detail what the 2000 kernel debugger is on a future website. In the above example, this part is:

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.

Four types of stop messages

When a program or driver encounters an uncontrollable error message or attempts to execute an illegal command , the system will generate a stop error message. And this information usually consists of four types.

1. Regular stop messages: Stop messages that occur when using win2000 normally

General stop messages are usually the most difficult error messages to solve, because there may be countless reasons. causing errors to occur.

2. Installation stop message: The stop message during the installation of win2000 is usually caused by the presence of hardware devices incompatible with 2000 in your system.

The solution is to check the hardware devices in the system and find devices that are not listed in the 2000 compatibility list. Then contact your hardware device manufacturer to see if they can provide you with a driver for the device. If they can't, then you'll have to remove the device from your system and replace it with another compatible device.

If all of your hardware is compatible, you may have two conflicting hardware devices. To solve this problem, first remove any unnecessary hardware devices, then reload 2000. Once 2000 is successfully loaded, add all removed devices back to the system. Doing this can usually solve the problem, or at least tell you which hardware is conflicting.

3. Executable program installation stop message: Indicates the stop message that occurs in the fourth stage (execution program part) of the 2000 installation process.

Installation 2000 has two stages in the installation process of executable programs. The first stage is to disable hardware interrupts and load some basic components, such as the hardware abstraction layer.

The second phase is to initialize all the hardware in your system. If you get a stop message error when you reach this stage of the installation process. You need to run the diagnostic program again to determine whether your hardware is working properly. Then reinstall 2000. If you still encounter this error message, then you need to contact Microsoft Technical Support.

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.

A stop message that occurs due to an error trap in the software and when the program attempts to execute an illegal instruction. For example, this error may occur when a program attempts to write a string to a variable that originally holds a number. If you encounter this type of error, you need to write down the error message and what software caused the error. Generally, these software have new versions to correct these errors.

Steps you may need to solve the problem when you encounter a stop message:

First determine whether you have made any changes in the system recently. If you have, these changes are often the source of the problem. Try removing or removing new hardware or software to see if that resolves the problem. Check the hardware in the system. It is best if there is a hardware detection program, you can run the program to detect it, and reinsert your memory card and expansion card at the same time.

If your stop message occurs during startup or just after startup, then this may be a problem in one of your services or device drivers. You can try booting the machine into safe mode. If your 2000 system can successfully boot into safe mode, then your guess is correct.

At the same time, make sure that your anti-virus program is designed to be compatible with win2000 and kept updated at all times. If the error still occurs, go into your CMOS settings, disable options like cache or shadow in the BIOS, and then reboot.

Windows 2000 Blue Screen of Death STOP treats the "symptom"

Theoretically, pure 32-bit Windows 2000 will not crash, but this is only theoretical. Viruses or mismatch between hardware and hardware drivers will cause Windows 2000 to crash. When Windows 2000 freezes, the monitor screen will turn blue, and then a STOP fault message will appear. Below we introduce the general STOP troubleshooting methods and special STOP troubleshooting respectively.

General STOP troubleshooting

1. First use the new version of anti-virus software to check whether there are viruses on the computer.

2. If Windows 2000 can start, check the information in Event Viewer to determine the device or driver that caused the failure. The method to start "Event Viewer" is: "Start"\"Settings"\"Control Panel"\"Administrative Tools"\"Event Viewer"\"System Log".

3. If you cannot start the computer, try to start the computer in "Safe Mode" or "Last Known Good Configuration", and then delete or disable newly installed add-on programs or drivers. If you cannot start your computer in Safe Mode, you can use the Repair Console. The Repair Console can disable some services, rename device drivers, and troubleshoot the boot sector or master boot record.

4. Remove the newly installed hardware devices (RAM, adapter cards, hard drives, modems, etc.).

5. Make sure the hardware device drivers have been updated and the system has the latest BIOS.

6. Run system diagnostic tools provided by the computer manufacturer, especially memory check.

7. Check the Microsoft Compatible Hardware List (HCL) to ensure that all hardware and drivers are compatible with Windows 2000. Hcl.txt is in the \Support folder of the Windows 2000 CD-ROM.

8. Disable the memory cache function in the BIOS.

9. Restart the computer, at the startup screen, press F8 to enter "Advanced Startup Options", and then select "Last Known Good Configuration". (Note: Use the "Last Known Good Configuration" method to start the computer, and all settings of the computer will be reset to the configuration at the time of the last successful startup.)

10. If you can access the Web, please enter / ntserver/, click "Support"/"Search Knowledge Base", at "Type your keywords here", enter "stop" and the corresponding number (if the STOP message "stop:0x0000000A" appears, you can enter "stop0x0000000A" here ) and press the Enter key to find out the solution to the STOP problem that occurred. (E text)

Part of the STOP code

STOP message 0x0000000A failure (when a new device is just added)

The usual reason is that the driver uses an abnormal memory address .

1. During the installation process, when the screen prompts "The installation program is checking the computer hardware configuration", press F5 and select the appropriate computer type according to the prompts. For example, if your computer is a single processor, select "Standard PC."

2. Disable the memory cache function in the BIOS.

3. Remove all adapter cards and disconnect all hardware devices that are not necessary to start the computer, and then reinstall Windows 2000.

4. If the system is equipped with a SCSI adapter card, please obtain the latest Windows 2000 driver from the adapter card seller, disable the synchronization negotiation function, and check the termination header and the SCSI ID number of the device.

5. If the system is equipped with an IDE device, set the IDE port to Primary. Check the IDE device's Master/Slave/Only settings. Except for the hard drive, remove all other IDE devices.

6. Run system diagnostic tools provided by the computer manufacturer, especially memory check.

7. Check the Microsoft Compatible Hardware List (HCL) to ensure that all hardware and drivers are compatible with Windows 2000.

8. Restart the computer. At the startup screen, press F8 to enter "Advanced startup options" and select "Last known good configuration".

STOP message 0x0000001E failure

1. Check whether there is sufficient disk space, especially for new installations.

2. Disable the driver shown in the STOP message and all newly installed drivers.

3. If the video driver used is not provided by Microsoft, try switching to the standard VGA driver or a suitable driver supported by Win2000.

4. Make sure the system has the latest BIOS.

5. Restart the computer. At the startup screen, press F8 to enter "Advanced startup options" and select "Last known good configuration".

STOP message 0x00000023 and 0x00000024 failures

Usual causes include severe drive fragmentation, overloaded file I/O, third-party drive mirroring software, or errors in some anti-virus software.

1. Disable some anti-virus software or backup programs, and disable all defragmentation applications.

2. Run CHKDSK /f to troubleshoot the hard drive, and then restart the computer.

3. Restart the computer. At the startup screen, press F8 to enter Advanced Startup Options, then select Last Known Good Configuration.

STOP message 0x0000002E failure

Usual cause Parity error in system memory.

1. Run the system diagnostic tools provided by the computer manufacturer, especially the memory check.

2. Disable the memory cache function in the BIOS.

3. Try to start in "Safe Mode". If "Safe Mode" boots the computer, try changing to the standard VGA driver. If this doesn't solve the problem, you may need to use an additional video adapter card. Compatible video adapter cards are listed in the Compatible Hardware List.

4. Make sure the hardware device drivers have been updated and the system has the latest BIOS.

5. Remove some newly installed hardware (RAM, adapters, hard drives, modems, etc.).

6. Restart the computer. At the startup screen, press F8 to enter "Advanced startup options" and select "Last known good configuration".

STOP message 0x0000003F failure

Usual cause The driver has not been completely cleared.

Remove some newly installed software, including backup tools or disk tools such as defragmentation and antivirus software.

STOP message 0x00000058 failure

Typical cause An error occurred in the master drive of the fault-tolerance set.

1. Use the Windows 2000 boot floppy disk to start the computer from the mirrored (second) system drive.

2. Restart the computer. At the startup screen, press F8 to enter "Advanced startup options" and select "Last known good configuration".

STOP message 0x0000007B failure

Typical cause A problem occurred during the initialization of the I/O system (usually the boot drive or file system).

1. Check whether there are viruses on your computer. This STOP message usually appears when there is a virus in the boot sector.

2. Use the "Repair Console" to repair the drive.

3. Remove the newly installed hard drive or control card.

4. If the system is equipped with a SCSI adapter card, please obtain the latest Windows 2000 driver from the adapter card seller, disable the synchronization negotiation function, and check the termination header and the SCSI ID number of the device.

5. If the system is equipped with an IDE device, set the IDE port to Primary. Check the IDE device's Master/Slave/Only settings. Except for the hard drive, remove all other IDE devices.

6. Run CHKDSK. If Windows 2000 cannot start CHKDSK, you must remove the hard disk and connect it to another Windows 2000 system, and then use the CHKDSK command to check the hard disk.

7. Restart the computer. At the startup screen, press F8 to enter "Advanced startup options" and select "Last known good configuration".

STOP message 0x0000007F failure

Usual causes Hardware or software problems; the common cause is hardware failure.

1. Run the system diagnostic tools provided by the computer manufacturer, especially the memory check. This STOP message often occurs in the case of errors or misallocation of memory.

2. Disable the memory cache function in the BIOS.

3. Try removing or replacing hardware: RAM, controllers, adapters, modems and other peripherals.

4. Check the Microsoft Compatible Hardware List (HCL) to ensure that all hardware and drivers are compatible with Windows 2000. This issue may be caused by an incompatible motherboard.

5. Restart the computer. At the startup screen, press F8 to enter Advanced Startup Options, then select Last Known Good Configuration.

Tools to solve the blue screen:

"Grasp with both hands, both hands must be strong". In order to deal with the "blue screen" phenomenon, in addition to improving your system hardware environment in terms of hardware, the "soft environment" The construction cannot be ignored. We will introduce to you some of the tools we know. Of course, there may be more good tools, so you might as well pay more attention to them!

RAM Idle--make the blue screen disappear

Whether it is the long-gone DOS era or the flourishing Windows era, as the most important system resource-memory resource, It has always been the most troublesome thing for computer enthusiasts. Although there are more and more memory slots on motherboards and the price of memory is getting lower and lower, no matter what, there are still many friends who often have insufficient memory resources, so that the system performance cannot function properly. The main reason is that the Windows operating system cannot effectively manage memory resources, resulting in a large amount of memory resources being occupied in vain, which greatly reduces system performance and causes annoying problems such as program locks and system hangs. Therefore, many tool software specifically used to manage memory resources have emerged, and the RAM Idle I will introduce today is the leader in this type of software.

1. Installation

First use Winzip and other software to decompress the downloaded compressed package, then click the Setup.exe file, select Yes in the pop-up dialog box to start installing RAM Idle (Figure 1). Like most Windows applications, the installation process for RAM Idle is simple and requires just clicking Next along the way.

2. Use

The main function of RAM Idle is to automatically release and recycle a certain amount of memory according to user settings when the system is idle, thereby avoiding memory resources caused by insufficient Windows systems. eliminate the exhaustion problem and greatly improve system performance and stability.

As the saying goes: If you want to do your job well, you must first sharpen your tools. The same is true for using RAM Idle. Only with reasonable settings can it better manage memory resources. Next, please click Start-Programs-RAM Idle-Configuration to open the RAM Idle setting interface (as shown in Figure 2) and learn about the RAM Idle setting options with me

1. Main tab: It is the main part of the software The setting part includes the following contents:

·Target Free RAM: Set the amount of memory that RAM Idle will try to recover when the minimum remaining memory is reached.

·Minimum Free RAM: Set the minimum amount of remaining memory. When this value is reached, RAM Idle will automatically restore memory resources.

·Disable the CPU usage detection: After selecting this option, RAM Idle will no longer detect the CPU usage when restoring memory, but it is only needed when your CPU usage always displays 100%. Selected.

Under normal circumstances, we do not need to select this item. Recover RAM if only... can set the maximum CPU usage when recovering memory. That is to say, RAM Idle can restore memory only when the CPU usage is lower than the set value. Otherwise, Not restored.

·Free up...if free RAM below 50%: Set the amount of memory to be restored at intervals when the remaining memory is less than 50% of the total memory.

·Pop up menu free...: Set the three recovery values ????in the manual recovery memory part of the pop-up menu.

2. Options tab: It mainly includes some general settings such as always on top, starting when Windows starts, hiding the system tray icon, etc.

3. Gator tab: A brief introduction and download link to a form-filling software.

4. About tab: Displays the memory resource information of the current system (as shown in Figure 3)

RAM Idle releases memory *** There are two ways, one is to use the remaining memory When less than 50% of the total memory is used, a certain amount of memory will be automatically released at regular intervals according to the settings (see the setting method above); one is to right-click the RAM Idle icon in the system tray and use the pop-up menu (Figure 4) ) to quickly and manually release a certain amount of memory (see above for setting methods).

3. Summary

Compared with similar software, RAM Idle basically combines all the essence of this type of software and has unparalleled powerful memory management capabilities. First of all, RAM Idle can automatically release memory resources, and the optimization time is fast and efficient. Secondly, RAM Idle is easy to set up, has complete functions, takes up less system resources, and can be run when the system is relatively idle. In addition, the software also has a variety of convenient and practical small functions, such as restarting, shutting down, suspending, etc.

Although MemMAX, FREERAM, RAMFIX and other software also have their own characteristics, due to one or other shortcomings, such as not being able to automatically optimize, occupying too many system resources, low optimization efficiency, and cumbersome use, etc., they are very difficult to use. Hard to beat RAM Idle.

If you are worried about the management of your memory resources, then I suggest you try RAM Idle. With its strength, I believe you will not be disappointed!

To put it simply:

You also need a medical record when seeing a doctor...

Have you ever used XP on this computer? Have you ever had the same problem? Problem?

If so, how likely is the blue screen caused by the software to be caused by buffer overflow?

The hardware may be a driver conflict.

You can slowly read the above content to find the answer!

Thank you!