During the startup and operation of the computer, if there is a fault, the corresponding error message will appear. We can follow the prompt message to solve the current fault. However, most of these prompt information are in English prompts or machine codes, which is deeply confusing. This article collects and organizes the error message that often occurs during startup and operation of the computer, and provides a complete solution, hoping that it will be helpful to you when troubleshooting problems.
1. Troubleshoot system startup errors
A complete system startup process requires a close cooperation between the system BIOS and the operating system. If an error occurs in a certain link, it will cause the system to fail to start.
Self-test prompt sound explanation
In case of errors in BIOS detection, a prompt sound of varying lengths will be emitted. Different prompt sounds represent different error messages. According to the meaning of these information, it is not difficult to make corresponding diagnosis. Let’s take two more common BIOS (Award BIOS and AMI BIOS) as an example to introduce the specific meaning of the POST ring code:
(1) The BIOS self-test prompt sound of the Award:
1 Short: The system starts normally. This is what we hear every day, and it also shows that there is no problem with the computer.
2 Short: General error, please enter CMOS Setup and reset the incorrect options.
1 long 1 short: There was an error in RAM or motherboard. Try changing a memory, if it still doesn't work, you have to change the motherboard.
1 long 2 short: monitor or graphics card error.
1 long 3 short: keyboard controller error. Check the motherboard.
1 long 9 short: Motherboard Flash RAM or EPROM error, BIOS is damaged. Try changing the Flash RAM block.
Keep ringing: The power supply and monitor are not connected to the graphics card. Check all plugs.
Repeat short sound: power supply problem.
No sound or display: power problem.
(2) AMI's BIOS self-test prompt sound definition:
1 Short: Memory refresh failed. Replace the memory stick.
2 Short: Memory ECC verification error. Setting the memory option for ECC verification in CMOS Setup to Disabled can solve the problem. The most fundamental solution is to replace the memory.
3 Short: System basic memory (1st 64MB) check failed. Change memory.
4 Short: System clock error.
5 Short: Central Processing (CPU) error.
6 short: keyboard controller error.
7 Short: The system's real mode is incorrect and cannot switch to protected mode.
8 Short: Display memory error. If there is any memory problem, try replacing the graphics card.
9 short: ROM BIOS checksum error.
1 long 3 short: memory error. If the memory is damaged, just replace it.
1 long 8 short: Show test errors. The monitor data cable is not plugged in properly or the graphics card is not plugged in tight.
BIOS startup information detailed explanation
When the computer starts up the BIOS self-test, there are generally similar prompts after the error message prompted:
“Press F1 to Continue or Press DEL to Enter Setup”
It means "press F1 key to continue or press DEL key to enter CMOS settings".
The following are the common Award BIOS error information that may be given if it encounters a fault during the system self-test:
Prompt message: BIOS ROM checksum error - System halted
Normal reason: BIOS verification error - system shutdown. This shows that the code in the BIOS chip of the computer motherboard found an error during verification, or that the BIOS chip itself or the contents in it were damaged.
Solution: You need to rewrite your BIOS content, or replace a new BIOS chip.
Prompt information: CMOS battery failed, CMOS battery is no longer functional
Usually reason: After the CMOS battery is exhausted, all the contents set in CMOS will be lost.
Solution: Replace a new battery.
Prompt message: CMOS checksum error - Defaults loaded
Normal reason: If an error is found when the BIOS checks the CMOS settings, the system will load the default device configuration information. CMOS calibration errors often mean that there are errors in the CMOS settings, and this error may also be caused by insufficient power of the motherboard battery.
Solution: Please check your battery and replace it if necessary.
Prompt message: Display switch is set incorrectly
Common reasons: The settings of the display switch on the motherboard do not match the type of monitor actually used.
Solution: Some computers have display switches on their motherboards, and you can choose to use a monochrome or color monitor. At this time, please first confirm the type of the monitor, then turn off the system, and set the corresponding display jumper. If there is no display switch on the motherboard, then we should go to the system CMOS settings to change the display type.
Prompt message: Press ESC to skip memory test
Normal reason: Pressing the ESC key can skip memory detection.
Solution: The machine needs to detect memory every time it is cold-started; at this time, if we do not want the system to detect memory, we can press the Esc key to skip this step.
Prompt message: Floppy disk(s) fail
Common reason: Floppy drive error.
Solution: When the computer starts, if the floppy drive controller or floppy drive is not found or cannot be initialized correctly, the system will see such a prompt. At this time, please check whether the floppy drive controller is installed well. If the floppy drive controller is integrated on the motherboard, then we also need to check whether the options for floppy drive controller in CMOS are in the "Enabled" state.
If the floppy drive is not installed on the machine, please check whether the floppy drive item is set to "None" in the CMOS settings.
Prompt message: HARD DISK INSTALL FAILURE
Usually reason: The hard disk installation is unsuccessful. When the computer starts, if the hard disk controller or hard disk itself is not found or cannot be initialized correctly, the computer will give the above prompt.
Solution: Please determine whether the hard disk controller is installed correctly or whether the option for the hard disk controller in CMOS is "Enabled".
If you do not have a hard drive installed on your computer, please make sure that the hard drive type is "None" or "Auto" in the system settings.
Prompt message: Keyboard error or no keyboard present
Common reasons: keyboard error or keyboard not installed. When the computer starts, if the system cannot initialize the keyboard, such information will be given.
Solution: Please check whether the keyboard and computer are connected correctly and whether there are keys when the computer starts up.
If you want to set the computer to work without a keyboard, then we can set the "Halt On" option to "Halt On All, But Keyboard" in CMOS; in this way, the computer will ignore the keyboard errors when it starts.
Prompt message: Keyboard is locked out- Unlock the key
Usually reason: This message usually occurs when one or more keys are pressed and held down when the computer is started.
Solution: Please check if there is something on top of the keyboard.
Prompt message: Memory test fail
Common reason: Memory test failed. When the computer starts, if an error is detected in the memory test step, the above message will be given, indicating that an error was encountered during the self-test of the memory.
Workaround: You may need to replace the memory.
Prompt message: Override enabled-Defaults loaded
Normal reason: If the computer cannot start normally under the current CMOS configuration, the computer's BIOS will automatically call the default CMOS settings to work.
Solution: The system's default CMOS settings are a set of CMOS configuration parameters that work the most stable but most conservative.
Prompt message: .Primary master hard disk fail
Normally, the main hard disk error occurred on the first IDE interface.
Solution: When the computer starts up, if an error occurs on the main hard disk on the first IDE hard disk interface of the machine, the above prompt will be given.
3. Troubleshoot the system startup error information
The BIOS self-test is completed and the system boots work is handed over to the operating system. If the system encounters some error at this time, it will also affect the normal startup of the system. Common error messages are as follows:
Prompt message: Cache Memory Bad, Do not enable Cache!
Common reason: BIOS finds that the cache memory on the motherboard is corrupted.
Solution: Please contact the manufacturer or seller to solve the problem.
Prompt message: Memorx paritx error detected
The usual reason: Memorx paritx error detected, that is, memory parity error, indicating that there is a fault in the memory system.
Solution: Please follow the steps below to check and process:
Whether different types of memory sticks are mixed in the system, such as memory sticks with parity and without parity, if this happens, please try only one memory stick;. In the Advanced BIOS Features option in the BIOS settings, set the "Quick Power On Self Test" setting item to Disabled. The system memory will be tested bit by bit three times when the system starts up, which can initially determine whether there are problems with the system memory; if the fault still cannot be solved, please set it in the BIOS The advanced chipset features option is set to slow down the memory (SDRAM) related options. This method can eliminate the failure of the memory speed that cannot keep up with the system bus speed; poor performance of the internal cache of the CPU can also lead to such failures. You can turn off the Cache-related options in the Advanced BIOS Features option. If it is a failure caused by Cache, please do a good job of cooling for the CPU. If it does not work, you have to lower the CPU frequency.
Prompt message: Error: Unable to ControLA20 Line
Common reasons: poor contact between the memory stick and the motherboard slot, and failure of the memory controller.
Solution: Check carefully whether the memory stick has good contact with the slot or replace the memory stick.
Prompt message: Memory Allocation Error
Usually reason: This is because the memory settings or improper settings of the memory management file are not used in the file, so that the system can only use 640KB of basic memory. When the program is slightly depressed, the prompt "Out of Memory" (excess memory) appears, and it is impossible to operate.
Solution: These phenomena are soft faults. Just write the system configuration file and restart the system.
Prompt message: C:drive failure run setup utility,press(f1)to resume
Usually cause: caused by incorrect hard disk parameter settings.
Solution: You can boot the hard disk with a floppy disk, but you need to reset the hard disk parameters.
Prompt message: HDD Controller Failure
The usual reason: It is generally poor contact or wrong wiring of the hard disk cable interface.
Solution: First check the connection between the hard disk power cord and the hard disk, and then check the connection between the hard disk data cord and the multi-function card or hard disk.
Prompt message: Invalid partition table
The usual reason: Generally, there is an error in the partition table in the main boot record of the hard disk. When multiple boot partitions are specified (only one boot partition can be used) or a virus occupies this partition table, the above prompt will be given. When the boot record (MBR) is located in the 0 head/0 cylinder/1 sector, it is generated when the hard disk is partitioned by FDISK. MBR includes three parts: the main boot program, the partition table and the end flag 55 AAH, which occupies a sector in total. The main boot program includes program code, error information, error handling, etc. for checking the hard disk partition table. When the hard disk boots up, the main boot program checks for bootstrap flags in the partition table. If a partition is a bootable partition, there is a partition flag 80H. Otherwise, the system stipulates that only one partition is a bootable partition. If the partition table contains multiple bootable flags, the main boot program will give an error message "Invalid partition table".
Solution: Use KV3000 to view whether the active partition flag and partition end flag (1FE, FF's 55 AA) of the hard disk partition record are lost. The easiest solution is to use NDD to fix it. It will check the errors in the partition table. If you find the error, you will ask if you are willing to modify it. You just need to answer YES to correct the error, or you can overwrite it with the backed-up partition table (RESCUE in KV300 and NU8.0, all have the functions of backing up and restoring partition tables). If the virus is infected with the partition table, formatting cannot solve the problem. You can first use antivirus software to prevent viruses, and then use NDD to repair it.
If none of the above methods can be solved, there is another way, which is to repartition with FDISK first, but the partition size must be the same as the original partition. Do not perform advanced formatting after partitioning, and then use NDD for repair. The repaired hard disk will not only boot, but the information on the hard disk will not be lost. In fact, using FDISK partitioning is compared to overwriting the original partition table with the correct partition table.
Prompt message: No Rom Basic, System Halted
The usual reason: Generally, the boot program is damaged or infected by a virus, or there is no bootstrap flag in the partition table, or the end flag 55 AA is rewritten.
Solution: Start from the floppy disk and execute the command "FDISK/MBR". FDISK contains the main boot program code and the end flag 55 AA. The above commands can make the correct main boot program and end flag in FDISK overwrite the main boot program on the hard disk. For the phenomenon of no bootstrap flag in the partition table, NDD can be restored.
Prompt message: HDD Controller Failure
Usually causes: There are roughly three situations that may cause such error prompts, which may be due to poor contact with the IDE data cable, or the data cable interface is inverted; The worst case is that during self-test, periodic noise such as "Ka, Ka, Ka" appears in the hard disk, which indicates that there is a problem with the mechanical control part or the transmission arm; the disk of the hard disk is seriously damaged.
Solution: Reconnect correctly, or replace the hard drive.
Prompt message: Primary IDE channel no 80 conductor cable installed
Usually reason: The above situation indicates that the hard disk does not use the 80-pin hard disk cable.
Solution: Due to the large increase in transmission speed, in order to reduce interference, in the ATA100 hard disk specification, an 80-pin type hard disk cable is required, which is relatively more 40 ground cables.
Prompt information: Disk Boot Failure,insert system disk and press enter
Usually cause: The connection problem between the hard disk and the motherboard will cause the above error.
Solution: First, please open the chassis, take it out and connect the hard disk data cable and power head to confirm that the contact is normal. If it still cannot be detected, remove the hard drive and try it again to see if it is normal. If it is still abnormal, it is very likely that it is a problem with the motherboard. If it is normal, it is a problem with the hard drive.
Prompt message: Bad of Missing Command
Usually reason: This means that the file has been corrupted or lost. It may be overwritten or changed when installing other software.
Solution: Just copy the files on the boot disk of the same version to the root directory of the hard disk boot area and restart.
Prompt message: No System Disk or Disk Error
Usually the reason: It means that the boot disk is a non-system disk, or the system files of the original boot disk are corrupted.
Solution: First make sure that the floppy disk in the floppy drive is the system disk. Secondly, you should pay attention to whether the system files of the system hard disk have been corrupted. If they have been corrupted, you can use the same version of the boot disk to boot with the SYS C: command to transfer the correct system files to the boot disk.
Prompt message: Error Loading Operating System or Missing Operating System
Usually the reason: Generally, there is an error in the DOS boot record, or the partition end flag 55 AA is damaged. This may be due to the damage to the system files and the hard disk, or the damage to the DOS boot record (BOOT) of the hard disk, or the loss of the end flag of the DOS boot record (01 FE, FF’s 55 AA), or the loss of the main boot data of the hard disk, or the loss of the main boot end flag (080, 081’s 55 AA).
Solution: First try to restore the system file using the SYS C: command; if it doesn't work, you can use Diskedit to modify the end flag of the main boot of the hard disk (55 AA of 080 and 081); if it doesn't work, only the floppy disk boot is booted, use Fdisk to repartition, and then format it and reinstall the operating system.
Tip: You can now safely turn off your computer
Usually reason: The most likely reason is that the system files used by Windows are corrupted or not found.
Solution: Enter the DOS environment, copy this file from other computers to your computer's Windows system directory, and then restart the computer before entering. If you cannot copy this file from another computer, please reinstall the operating system.
Prompt message: Invalid system disk
The usual reason: that is, the device that can start the computer cannot be found when the computer is turned on.
Solution: If the boot sequence you set is A and C, then check if there is a disk that is not a boot disk in the floppy drive.
If not, check your hard drive to see if the BIOS can correctly detect the hard drive. If you do not block the hard drive or move the hard drive, check whether the data cable is damaged.
If the problem cannot be solved, it is most likely because you are upgrading and installing Windows 98, some files are not installed, perhaps because of viruses, or some antivirus software and hard disk management software have conflicts. If the error is caused by running antivirus software, after starting the computer with the boot disk generated during installation of Windows 98, execute the following command at the DOS prompt:
CD\Windows\command
attrib c:\-s-h-r
copy c:\msdos c:\
a:
sys c:
c:
attrib c:\-s-h-r
del c:\
copy c:\
attrib c:\+s+h+r
After reinstalling the system files, remove the boot disk and restart the computer.
If it is because of using hard disk management software and Windows 98 does not detect it, the boot record (MBR) will be overwritten. If the fault is caused, you should refer to the software's manual to restore the MBR.
There are other reasons that may also cause this failure, check whether the two numbers in the FSLog line in it are the same, such as FSLog: BIOS Heads=:255:, BootPart Heads=:255:. These two numbers must be the same, if different, reinstall the system file as above. If it is caused by a virus, you should completely remove the virus and reinstall Windows 98.
Prompt message: Disk I/O Error1; Replace disk and press ENTER
Usually the reason: because your machine loses the startup file.
Solution: Make a boot disk on someone else's machine, put it into your floppy drive, and copy the lost files to the hard drive; if not, reinstall the system again.
However, if your machine is infected with CIH virus, this phenomenon may also occur. It is because the CIH virus rewrites your hard disk partition table, resulting in the loss of the active partition. You just need to use the Fdisk command to reactivate the hard disk.
Prompt message: *.vxd file is invalid
Usually the reason: Incorrect operation of disk files, resulting in the loss of VXD files.
Solution: First check whether the file is lost. If the file is lost, install it first and then delete the network components to avoid this problem:
Click "Start → Settings → Control Panel → Network", click the "Add" button, select the "Adapter" option, and then click the "Add" button. In the "Manufacturer" box, click "Detected Network Driver". In Network Adapter, click on "Existing Ndis2 Drivers" and then click on the "OK" button.
When the system prompts to enter the workgroup name and computer name, please fill in the corresponding box on the "Identification" tab and click the "OK" or "Close" buttons continuously until you return to the "Control Panel".
When the system prompts to restart the computer, please click the "OK" button. After restarting the computer, click "Start → Settings → Control Panel → Network", click "Existing Ndis2 Driver", click the "Delete" button, then click the "OK" button, and click the "OK" button to restart the computer.
If the problem is not solved, try to see if the StaticVxD value in the registry is correct. If the error message does not specify the device driver, correct the StaticVxD value in the registry by using the Registry Editor to find and delete the StaticVxD value in the registry that contains only invalid data, empty data, or spaces. The StaticVxD value is located below HKEYLOCALMACHINE\System\CurrentControlSet\Services\VxD.
Note: Back up the registry file before operation.
If the above method is not possible, please confirm whether the program has been deleted from the computer recently. If you have recently deleted a program or component from your computer, reinstall it and run the appropriate uninstall tool.
Prompt message: *386 file is invalid
Common reason: System device driver is lost.
Solution: Just disable the file to set the driver, the method is:
Click "Start → Run", in the "Open" box, type "Msconfig", and in the "" tab of the open dialog box, double-click the [386Enh]" item. Position the row involving the device driver, click to clear the check box next to this line, and then click the "OK" button to restart the computer.
Prompt message: Lost
Usually the reason: Incorrect operation of disk files, resulting in the loss of VXD files.
Solution: You can copy this file to another computer (note that the file name should be the same as the Windows version) and put it in the corresponding directory.
You can also use the commands in Windows 98 to recover from the installation file *.cab of Windows 98. We know that when the system files you want to recover are located in the installation CD, you can use the "EXTRACT/Y Windows command (recover files from the zipped package named Windows 98 installation CD).
However, if you don't know the exact location of this file, you should use "Extract/D Windows 98*.CAB" (this time * represents the number of the CAB file package) to view each CAB file.
Prompt message: *.dll cannot be started
Usually reasons: There are many kinds of information, such as "The file cannot be started, please check the problem of file identification", "The file cannot be started, please check the problem of file identification", "The file cannot be started, please check the problem of file identification", etc. After clicking "OK", it will appear: "EXPLORER caused an exception 6d007eH inmodule :xxxxxxxx”. This is because all (or one of the files) of your following: or some program files have been replaced.
Solution: Overwrite the correct file under \Windows\System.
These files can be found in C:\Windows\Sysbckup first, and then copied directly to C:\Windows\System. If C:\Windows\Sysbckup does not have it, you need to install the source files in the disk (the extension method is the same as above).
Prompt message: Watning: Windows has detected registry/configuration Safe mode to start Windows with a minimal set of drivers. ”
Usually the reason: the registry or important files are lost.
Solution: First enter safe mode, the system will display the registry program dialog box, and then select "Restore from backup and restart". It doesn't matter even if you have not backed up the registry, because whenever the registry is modified, Windows 98 will automatically generate a backup of the registry. If the registry can be restored successfully, Windows 98 will prompt you to restart the computer, and the system will be normal after restarting. If the registry cannot be restored, Windows 98 will recommend that you turn off your computer and reinstall Windows 98. In this case, if you have backed up the registry, use your backup to restore, otherwise reinstall Windows 98.
Prompt message: Cannot find a device file that may be needed to run Windows or a Windows Windows Registry or refers to this…
The usual reason is that the virtual device driver (VXD) involved in the file or registry does not exist or is damaged, or that an incorrect data is contained in a static VXD value in the registry.
Solution: First, follow the suggestions in the error message to solve it. If only partially delete the application you want to delete, you must uninstall all the application. The best way is to reinstall and run the anti-installation program. If there is no anti-installation program, you should refer to the methods provided in the application's reference manual to uninstall them all. If the file prompted in the error message belongs to the application that needs to be retained, reinstall the application. If it is not normal, you need to edit the registry and delete all error messages in the registry. The registry is an important file for Windows 98. If it is damaged, Windows 98 will not work and should be backed up before any modifications are made.
Prompt message: Not enough MEmory to convert the drive to FAT32 to free up MEmory,REM all state MEnts in the and the files.
Normal reason: Generally speaking, this information occurs when converting the hard disk to FAT32 format. This error will be triggered when the directory structure on the hard disk to be converted is too large and there is not enough regular memory to store.
Solution: It is recommended to optimize memory and try to load memory resident programs in and files into the high-end to get more regular memory.
Prompt message: This program has perforMEd an illegal operation and will be the problem persists,contact the program vendor.
Normal reason: For the above error message, if the "Details" button is pressed, Windows 98 will display the error message: "MSINFO32 caused an invalid page fault in module at015f:bff8XXXX." This is caused by a file calling MSINFO32. Running the "System Information" tool under Windows 98 may trigger this error.
Solution: Use a new file to replace the original error file. You can use the system file checking tool to extract this file from the Windows 98 installation CD. This program will intelligently check the system file: click "Start → Run", enter "" and click the "OK" button. In the system file check window, select "Extract a file from the installation floppy disk", enter "" in the input box, click the "Start" button, and follow the prompts to install until the prompts to restart the machine, and then restart.
2. Troubleshoot system blue screen errors
During the use of computers, you often encounter blue screens. For beginners, it seems like a computer disaster and they are at a loss. If we follow the solution information provided by the screen and prescribe the right medicine, it is not difficult to deal with the blue screen.
(I) Troubleshooting the Windows 2000 Blue Screen of Death
1. Why does the blue screen of death appear?
Theoretically, pure 32-bit Windows 2000 will not crash, but this is only theoretical. Viruses or hardware and hardware driver mismatch will cause Windows 2000 to crash. When Windows 2000 crashes, the monitor screen will turn blue, and then a Stop fault message will appear.
In Windows 2000, blue screen information is usually divided into stop messages and hardware messages. The stop message refers to an error message generated when the Windows 2000 kernel discovers a software error that it cannot recover. Hardware messages refer to error messages that occur when Windows 2000 discovers a serious hardware conflict.
Usually, the blue screen information that appears can be divided into separate parts, each containing valuable error handling information. These parts include:
Bug checking part: This is where the actual error message is included in the blue screen information. In this part, you should pay attention to the error code (i.e. the hexadecimal number after "Stop") and the error symbol (i.e. the word immediately after the error code).
Recommended User Action Section: This section often contains some general messages that guide you on how to correct errors.
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 your computer and debug processes.
2. General solutions
(1) First use the new version of antivirus software to check whether there are viruses on the computer.
(2) If Windows 2000 can be started, please check the information in the "Event Viewer" to determine the device or driver that caused the failure. The method to start "Event Viewer" is: click "Start → Settings → Control Panel → Administrative Tools → Event Viewer → System Log".
(3) If the computer cannot be started, try to start the computer in "Safe Mode" or "Last Correct Configuration", and then delete or disable the newly installed additional programs or drivers. If the computer cannot be started in Safe Mode, you can use Repair Console. "Repair Console" can disable some services, rename device drivers, repair boot sectors, or master boot records.
(4) Remove the newly installed hardware devices (memory, adapter card, hard disk, modem, etc.).
(5) Make sure that the drivers of the hardware device have been updated and the system has the latest BIOS, and disable the memory caching function in the BIOS.
(6) Run system diagnostic tools provided by computer manufacturers, especially memory checks.
(7) Check the Microsoft compatible hardware list (HCL) to ensure that all hardware and drivers are compatible with Windows 2000. In the Windows 2000 installation CD\Support folder.
(If you cannot log in, restart the computer. After the list of available operating systems is displayed, press the F8 key. On the Advanced Options screen, select the "Latest Correct Configuration" option to start the computer.
Note: When using the most recent correct configuration, the system settings changes made since the last successful startup will be lost.
3. Special blue screen information
Stop message: 0x0000000A fault (the device has been installed)
Explanation text: IRQLNOTLESSOREQUAL
Normal reason: The driver uses an abnormal memory address.
Solution: If Windows 2000 can still be started, check the relevant information displayed in the Event Viewer to determine the device or driver that causes the problem; turn off or disable some newly installed drivers and delete newly installed additional programs; remove some newly installed hardware; make sure that the drivers of the hardware device have been updated, and the system has the latest BIOS, and disable memory caching functions in the BIOS, such as Cache or Shadow; run the system diagnostic tools provided by the computer manufacturer, especially memory checks; check the Microsoft compatible hardware list (HCL) to ensure that all hardware and drivers are compatible with Windows 2000; restart the computer and select "Last correct configuration" to start the computer.
Stop message: 0x0000000A fault (when a new device was just added)
Explanation text: IRQLNOTLESSOREQUAL
Normal reason: The driver uses an abnormal memory address.
Solution: During the installation process, when the screen prompts "The installer is checking the computer hardware configuration", press the F5 key and select the appropriate computer type according to the prompt. For example, when the computer is a single processor, please select "Standard PC"; disable the memory cache function in the BIOS, remove all adapter cards, and disconnect all hardware devices that are not necessary to start the computer, and then reinstall Windows 2000; if the system is equipped with a SCSI adapter card, please request the latest Windows 2000 driver from the adapter card vendor, disable the synchronization negotiation function, and check the SCSI ID number of the terminal head and device; if the system is equipped with an IDE device, set the IDE port to Primary. Check the Master/Slave/Only settings of the IDE device. Except for the hard drive, remove all other IDE devices; run system diagnostic tools provided by the computer manufacturer, especially memory checks; check the Microsoft compatible hardware list (HCL) to ensure that all hardware and drivers are compatible with Windows 2000; select "Last correct configuration" to start the computer.
Stop message: 0x0000001E fault
Explanation text: KMODEEXPTIONNOTHANDLED
Common cause: Disk failure.
Solution: Check for sufficient disk space, especially new installations; disable the drivers displayed in the Stop message and all newly installed drivers; if the video driver used is not provided by Microsoft, try switching to the standard VGA driver or the appropriate driver supported by Windows 2000; make sure the system has the latest BIOS; select "Last correct configuration" to start the computer.
1. Troubleshoot system startup errors
A complete system startup process requires a close cooperation between the system BIOS and the operating system. If an error occurs in a certain link, it will cause the system to fail to start.
Self-test prompt sound explanation
In case of errors in BIOS detection, a prompt sound of varying lengths will be emitted. Different prompt sounds represent different error messages. According to the meaning of these information, it is not difficult to make corresponding diagnosis. Let’s take two more common BIOS (Award BIOS and AMI BIOS) as an example to introduce the specific meaning of the POST ring code:
(1) The BIOS self-test prompt sound of the Award:
1 Short: The system starts normally. This is what we hear every day, and it also shows that there is no problem with the computer.
2 Short: General error, please enter CMOS Setup and reset the incorrect options.
1 long 1 short: There was an error in RAM or motherboard. Try changing a memory, if it still doesn't work, you have to change the motherboard.
1 long 2 short: monitor or graphics card error.
1 long 3 short: keyboard controller error. Check the motherboard.
1 long 9 short: Motherboard Flash RAM or EPROM error, BIOS is damaged. Try changing the Flash RAM block.
Keep ringing: The power supply and monitor are not connected to the graphics card. Check all plugs.
Repeat short sound: power supply problem.
No sound or display: power problem.
(2) AMI's BIOS self-test prompt sound definition:
1 Short: Memory refresh failed. Replace the memory stick.
2 Short: Memory ECC verification error. Setting the memory option for ECC verification in CMOS Setup to Disabled can solve the problem. The most fundamental solution is to replace the memory.
3 Short: System basic memory (1st 64MB) check failed. Change memory.
4 Short: System clock error.
5 Short: Central Processing (CPU) error.
6 short: keyboard controller error.
7 Short: The system's real mode is incorrect and cannot switch to protected mode.
8 Short: Display memory error. If there is any memory problem, try replacing the graphics card.
9 short: ROM BIOS checksum error.
1 long 3 short: memory error. If the memory is damaged, just replace it.
1 long 8 short: Show test errors. The monitor data cable is not plugged in properly or the graphics card is not plugged in tight.
BIOS startup information detailed explanation
When the computer starts up the BIOS self-test, there are generally similar prompts after the error message prompted:
“Press F1 to Continue or Press DEL to Enter Setup”
It means "press F1 key to continue or press DEL key to enter CMOS settings".
The following are the common Award BIOS error information that may be given if it encounters a fault during the system self-test:
Prompt message: BIOS ROM checksum error - System halted
Normal reason: BIOS verification error - system shutdown. This shows that the code in the BIOS chip of the computer motherboard found an error during verification, or that the BIOS chip itself or the contents in it were damaged.
Solution: You need to rewrite your BIOS content, or replace a new BIOS chip.
Prompt information: CMOS battery failed, CMOS battery is no longer functional
Usually reason: After the CMOS battery is exhausted, all the contents set in CMOS will be lost.
Solution: Replace a new battery.
Prompt message: CMOS checksum error - Defaults loaded
Normal reason: If an error is found when the BIOS checks the CMOS settings, the system will load the default device configuration information. CMOS calibration errors often mean that there are errors in the CMOS settings, and this error may also be caused by insufficient power of the motherboard battery.
Solution: Please check your battery and replace it if necessary.
Prompt message: Display switch is set incorrectly
Common reasons: The settings of the display switch on the motherboard do not match the type of monitor actually used.
Solution: Some computers have display switches on their motherboards, and you can choose to use a monochrome or color monitor. At this time, please first confirm the type of the monitor, then turn off the system, and set the corresponding display jumper. If there is no display switch on the motherboard, then we should go to the system CMOS settings to change the display type.
Prompt message: Press ESC to skip memory test
Normal reason: Pressing the ESC key can skip memory detection.
Solution: The machine needs to detect memory every time it is cold-started; at this time, if we do not want the system to detect memory, we can press the Esc key to skip this step.
Prompt message: Floppy disk(s) fail
Common reason: Floppy drive error.
Solution: When the computer starts, if the floppy drive controller or floppy drive is not found or cannot be initialized correctly, the system will see such a prompt. At this time, please check whether the floppy drive controller is installed well. If the floppy drive controller is integrated on the motherboard, then we also need to check whether the options for floppy drive controller in CMOS are in the "Enabled" state.
If the floppy drive is not installed on the machine, please check whether the floppy drive item is set to "None" in the CMOS settings.
Prompt message: HARD DISK INSTALL FAILURE
Usually reason: The hard disk installation is unsuccessful. When the computer starts, if the hard disk controller or hard disk itself is not found or cannot be initialized correctly, the computer will give the above prompt.
Solution: Please determine whether the hard disk controller is installed correctly or whether the option for the hard disk controller in CMOS is "Enabled".
If you do not have a hard drive installed on your computer, please make sure that the hard drive type is "None" or "Auto" in the system settings.
Prompt message: Keyboard error or no keyboard present
Common reasons: keyboard error or keyboard not installed. When the computer starts, if the system cannot initialize the keyboard, such information will be given.
Solution: Please check whether the keyboard and computer are connected correctly and whether there are keys when the computer starts up.
If you want to set the computer to work without a keyboard, then we can set the "Halt On" option to "Halt On All, But Keyboard" in CMOS; in this way, the computer will ignore the keyboard errors when it starts.
Prompt message: Keyboard is locked out- Unlock the key
Usually reason: This message usually occurs when one or more keys are pressed and held down when the computer is started.
Solution: Please check if there is something on top of the keyboard.
Prompt message: Memory test fail
Common reason: Memory test failed. When the computer starts, if an error is detected in the memory test step, the above message will be given, indicating that an error was encountered during the self-test of the memory.
Workaround: You may need to replace the memory.
Prompt message: Override enabled-Defaults loaded
Normal reason: If the computer cannot start normally under the current CMOS configuration, the computer's BIOS will automatically call the default CMOS settings to work.
Solution: The system's default CMOS settings are a set of CMOS configuration parameters that work the most stable but most conservative.
Prompt message: .Primary master hard disk fail
Normally, the main hard disk error occurred on the first IDE interface.
Solution: When the computer starts up, if an error occurs on the main hard disk on the first IDE hard disk interface of the machine, the above prompt will be given.
3. Troubleshoot the system startup error information
The BIOS self-test is completed and the system boots work is handed over to the operating system. If the system encounters some error at this time, it will also affect the normal startup of the system. Common error messages are as follows:
Prompt message: Cache Memory Bad, Do not enable Cache!
Common reason: BIOS finds that the cache memory on the motherboard is corrupted.
Solution: Please contact the manufacturer or seller to solve the problem.
Prompt message: Memorx paritx error detected
The usual reason: Memorx paritx error detected, that is, memory parity error, indicating that there is a fault in the memory system.
Solution: Please follow the steps below to check and process:
Whether different types of memory sticks are mixed in the system, such as memory sticks with parity and without parity, if this happens, please try only one memory stick;. In the Advanced BIOS Features option in the BIOS settings, set the "Quick Power On Self Test" setting item to Disabled. The system memory will be tested bit by bit three times when the system starts up, which can initially determine whether there are problems with the system memory; if the fault still cannot be solved, please set it in the BIOS The advanced chipset features option is set to slow down the memory (SDRAM) related options. This method can eliminate the failure of the memory speed that cannot keep up with the system bus speed; poor performance of the internal cache of the CPU can also lead to such failures. You can turn off the Cache-related options in the Advanced BIOS Features option. If it is a failure caused by Cache, please do a good job of cooling for the CPU. If it does not work, you have to lower the CPU frequency.
Prompt message: Error: Unable to ControLA20 Line
Common reasons: poor contact between the memory stick and the motherboard slot, and failure of the memory controller.
Solution: Check carefully whether the memory stick has good contact with the slot or replace the memory stick.
Prompt message: Memory Allocation Error
Usually reason: This is because the memory settings or improper settings of the memory management file are not used in the file, so that the system can only use 640KB of basic memory. When the program is slightly depressed, the prompt "Out of Memory" (excess memory) appears, and it is impossible to operate.
Solution: These phenomena are soft faults. Just write the system configuration file and restart the system.
Prompt message: C:drive failure run setup utility,press(f1)to resume
Usually cause: caused by incorrect hard disk parameter settings.
Solution: You can boot the hard disk with a floppy disk, but you need to reset the hard disk parameters.
Prompt message: HDD Controller Failure
The usual reason: It is generally poor contact or wrong wiring of the hard disk cable interface.
Solution: First check the connection between the hard disk power cord and the hard disk, and then check the connection between the hard disk data cord and the multi-function card or hard disk.
Prompt message: Invalid partition table
The usual reason: Generally, there is an error in the partition table in the main boot record of the hard disk. When multiple boot partitions are specified (only one boot partition can be used) or a virus occupies this partition table, the above prompt will be given. When the boot record (MBR) is located in the 0 head/0 cylinder/1 sector, it is generated when the hard disk is partitioned by FDISK. MBR includes three parts: the main boot program, the partition table and the end flag 55 AAH, which occupies a sector in total. The main boot program includes program code, error information, error handling, etc. for checking the hard disk partition table. When the hard disk boots up, the main boot program checks for bootstrap flags in the partition table. If a partition is a bootable partition, there is a partition flag 80H. Otherwise, the system stipulates that only one partition is a bootable partition. If the partition table contains multiple bootable flags, the main boot program will give an error message "Invalid partition table".
Solution: Use KV3000 to view whether the active partition flag and partition end flag (1FE, FF's 55 AA) of the hard disk partition record are lost. The easiest solution is to use NDD to fix it. It will check the errors in the partition table. If you find the error, you will ask if you are willing to modify it. You just need to answer YES to correct the error, or you can overwrite it with the backed-up partition table (RESCUE in KV300 and NU8.0, all have the functions of backing up and restoring partition tables). If the virus is infected with the partition table, formatting cannot solve the problem. You can first use antivirus software to prevent viruses, and then use NDD to repair it.
If none of the above methods can be solved, there is another way, which is to repartition with FDISK first, but the partition size must be the same as the original partition. Do not perform advanced formatting after partitioning, and then use NDD for repair. The repaired hard disk will not only boot, but the information on the hard disk will not be lost. In fact, using FDISK partitioning is compared to overwriting the original partition table with the correct partition table.
Prompt message: No Rom Basic, System Halted
The usual reason: Generally, the boot program is damaged or infected by a virus, or there is no bootstrap flag in the partition table, or the end flag 55 AA is rewritten.
Solution: Start from the floppy disk and execute the command "FDISK/MBR". FDISK contains the main boot program code and the end flag 55 AA. The above commands can make the correct main boot program and end flag in FDISK overwrite the main boot program on the hard disk. For the phenomenon of no bootstrap flag in the partition table, NDD can be restored.
Prompt message: HDD Controller Failure
Usually causes: There are roughly three situations that may cause such error prompts, which may be due to poor contact with the IDE data cable, or the data cable interface is inverted; The worst case is that during self-test, periodic noise such as "Ka, Ka, Ka" appears in the hard disk, which indicates that there is a problem with the mechanical control part or the transmission arm; the disk of the hard disk is seriously damaged.
Solution: Reconnect correctly, or replace the hard drive.
Prompt message: Primary IDE channel no 80 conductor cable installed
Usually reason: The above situation indicates that the hard disk does not use the 80-pin hard disk cable.
Solution: Due to the large increase in transmission speed, in order to reduce interference, in the ATA100 hard disk specification, an 80-pin type hard disk cable is required, which is relatively more 40 ground cables.
Prompt information: Disk Boot Failure,insert system disk and press enter
Usually cause: The connection problem between the hard disk and the motherboard will cause the above error.
Solution: First, please open the chassis, take it out and connect the hard disk data cable and power head to confirm that the contact is normal. If it still cannot be detected, remove the hard drive and try it again to see if it is normal. If it is still abnormal, it is very likely that it is a problem with the motherboard. If it is normal, it is a problem with the hard drive.
Prompt message: Bad of Missing Command
Usually reason: This means that the file has been corrupted or lost. It may be overwritten or changed when installing other software.
Solution: Just copy the files on the boot disk of the same version to the root directory of the hard disk boot area and restart.
Prompt message: No System Disk or Disk Error
Usually the reason: It means that the boot disk is a non-system disk, or the system files of the original boot disk are corrupted.
Solution: First make sure that the floppy disk in the floppy drive is the system disk. Secondly, you should pay attention to whether the system files of the system hard disk have been corrupted. If they have been corrupted, you can use the same version of the boot disk to boot with the SYS C: command to transfer the correct system files to the boot disk.
Prompt message: Error Loading Operating System or Missing Operating System
Usually the reason: Generally, there is an error in the DOS boot record, or the partition end flag 55 AA is damaged. This may be due to the damage to the system files and the hard disk, or the damage to the DOS boot record (BOOT) of the hard disk, or the loss of the end flag of the DOS boot record (01 FE, FF’s 55 AA), or the loss of the main boot data of the hard disk, or the loss of the main boot end flag (080, 081’s 55 AA).
Solution: First try to restore the system file using the SYS C: command; if it doesn't work, you can use Diskedit to modify the end flag of the main boot of the hard disk (55 AA of 080 and 081); if it doesn't work, only the floppy disk boot is booted, use Fdisk to repartition, and then format it and reinstall the operating system.
Tip: You can now safely turn off your computer
Usually reason: The most likely reason is that the system files used by Windows are corrupted or not found.
Solution: Enter the DOS environment, copy this file from other computers to your computer's Windows system directory, and then restart the computer before entering. If you cannot copy this file from another computer, please reinstall the operating system.
Prompt message: Invalid system disk
The usual reason: that is, the device that can start the computer cannot be found when the computer is turned on.
Solution: If the boot sequence you set is A and C, then check if there is a disk that is not a boot disk in the floppy drive.
If not, check your hard drive to see if the BIOS can correctly detect the hard drive. If you do not block the hard drive or move the hard drive, check whether the data cable is damaged.
If the problem cannot be solved, it is most likely because you are upgrading and installing Windows 98, some files are not installed, perhaps because of viruses, or some antivirus software and hard disk management software have conflicts. If the error is caused by running antivirus software, after starting the computer with the boot disk generated during installation of Windows 98, execute the following command at the DOS prompt:
CD\Windows\command
attrib c:\-s-h-r
copy c:\msdos c:\
a:
sys c:
c:
attrib c:\-s-h-r
del c:\
copy c:\
attrib c:\+s+h+r
After reinstalling the system files, remove the boot disk and restart the computer.
If it is because of using hard disk management software and Windows 98 does not detect it, the boot record (MBR) will be overwritten. If the fault is caused, you should refer to the software's manual to restore the MBR.
There are other reasons that may also cause this failure, check whether the two numbers in the FSLog line in it are the same, such as FSLog: BIOS Heads=:255:, BootPart Heads=:255:. These two numbers must be the same, if different, reinstall the system file as above. If it is caused by a virus, you should completely remove the virus and reinstall Windows 98.
Prompt message: Disk I/O Error1; Replace disk and press ENTER
Usually the reason: because your machine loses the startup file.
Solution: Make a boot disk on someone else's machine, put it into your floppy drive, and copy the lost files to the hard drive; if not, reinstall the system again.
However, if your machine is infected with CIH virus, this phenomenon may also occur. It is because the CIH virus rewrites your hard disk partition table, resulting in the loss of the active partition. You just need to use the Fdisk command to reactivate the hard disk.
Prompt message: *.vxd file is invalid
Usually the reason: Incorrect operation of disk files, resulting in the loss of VXD files.
Solution: First check whether the file is lost. If the file is lost, install it first and then delete the network components to avoid this problem:
Click "Start → Settings → Control Panel → Network", click the "Add" button, select the "Adapter" option, and then click the "Add" button. In the "Manufacturer" box, click "Detected Network Driver". In Network Adapter, click on "Existing Ndis2 Drivers" and then click on the "OK" button.
When the system prompts to enter the workgroup name and computer name, please fill in the corresponding box on the "Identification" tab and click the "OK" or "Close" buttons continuously until you return to the "Control Panel".
When the system prompts to restart the computer, please click the "OK" button. After restarting the computer, click "Start → Settings → Control Panel → Network", click "Existing Ndis2 Driver", click the "Delete" button, then click the "OK" button, and click the "OK" button to restart the computer.
If the problem is not solved, try to see if the StaticVxD value in the registry is correct. If the error message does not specify the device driver, correct the StaticVxD value in the registry by using the Registry Editor to find and delete the StaticVxD value in the registry that contains only invalid data, empty data, or spaces. The StaticVxD value is located below HKEYLOCALMACHINE\System\CurrentControlSet\Services\VxD.
Note: Back up the registry file before operation.
If the above method is not possible, please confirm whether the program has been deleted from the computer recently. If you have recently deleted a program or component from your computer, reinstall it and run the appropriate uninstall tool.
Prompt message: *386 file is invalid
Common reason: System device driver is lost.
Solution: Just disable the file to set the driver, the method is:
Click "Start → Run", in the "Open" box, type "Msconfig", and in the "" tab of the open dialog box, double-click the [386Enh]" item. Position the row involving the device driver, click to clear the check box next to this line, and then click the "OK" button to restart the computer.
Prompt message: Lost
Usually the reason: Incorrect operation of disk files, resulting in the loss of VXD files.
Solution: You can copy this file to another computer (note that the file name should be the same as the Windows version) and put it in the corresponding directory.
You can also use the commands in Windows 98 to recover from the installation file *.cab of Windows 98. We know that when the system files you want to recover are located in the installation CD, you can use the "EXTRACT/Y Windows command (recover files from the zipped package named Windows 98 installation CD).
However, if you don't know the exact location of this file, you should use "Extract/D Windows 98*.CAB" (this time * represents the number of the CAB file package) to view each CAB file.
Prompt message: *.dll cannot be started
Usually reasons: There are many kinds of information, such as "The file cannot be started, please check the problem of file identification", "The file cannot be started, please check the problem of file identification", "The file cannot be started, please check the problem of file identification", etc. After clicking "OK", it will appear: "EXPLORER caused an exception 6d007eH inmodule :xxxxxxxx”. This is because all (or one of the files) of your following: or some program files have been replaced.
Solution: Overwrite the correct file under \Windows\System.
These files can be found in C:\Windows\Sysbckup first, and then copied directly to C:\Windows\System. If C:\Windows\Sysbckup does not have it, you need to install the source files in the disk (the extension method is the same as above).
Prompt message: Watning: Windows has detected registry/configuration Safe mode to start Windows with a minimal set of drivers. ”
Usually the reason: the registry or important files are lost.
Solution: First enter safe mode, the system will display the registry program dialog box, and then select "Restore from backup and restart". It doesn't matter even if you have not backed up the registry, because whenever the registry is modified, Windows 98 will automatically generate a backup of the registry. If the registry can be restored successfully, Windows 98 will prompt you to restart the computer, and the system will be normal after restarting. If the registry cannot be restored, Windows 98 will recommend that you turn off your computer and reinstall Windows 98. In this case, if you have backed up the registry, use your backup to restore, otherwise reinstall Windows 98.
Prompt message: Cannot find a device file that may be needed to run Windows or a Windows Windows Registry or refers to this…
The usual reason is that the virtual device driver (VXD) involved in the file or registry does not exist or is damaged, or that an incorrect data is contained in a static VXD value in the registry.
Solution: First, follow the suggestions in the error message to solve it. If only partially delete the application you want to delete, you must uninstall all the application. The best way is to reinstall and run the anti-installation program. If there is no anti-installation program, you should refer to the methods provided in the application's reference manual to uninstall them all. If the file prompted in the error message belongs to the application that needs to be retained, reinstall the application. If it is not normal, you need to edit the registry and delete all error messages in the registry. The registry is an important file for Windows 98. If it is damaged, Windows 98 will not work and should be backed up before any modifications are made.
Prompt message: Not enough MEmory to convert the drive to FAT32 to free up MEmory,REM all state MEnts in the and the files.
Normal reason: Generally speaking, this information occurs when converting the hard disk to FAT32 format. This error will be triggered when the directory structure on the hard disk to be converted is too large and there is not enough regular memory to store.
Solution: It is recommended to optimize memory and try to load memory resident programs in and files into the high-end to get more regular memory.
Prompt message: This program has perforMEd an illegal operation and will be the problem persists,contact the program vendor.
Normal reason: For the above error message, if the "Details" button is pressed, Windows 98 will display the error message: "MSINFO32 caused an invalid page fault in module at015f:bff8XXXX." This is caused by a file calling MSINFO32. Running the "System Information" tool under Windows 98 may trigger this error.
Solution: Use a new file to replace the original error file. You can use the system file checking tool to extract this file from the Windows 98 installation CD. This program will intelligently check the system file: click "Start → Run", enter "" and click the "OK" button. In the system file check window, select "Extract a file from the installation floppy disk", enter "" in the input box, click the "Start" button, and follow the prompts to install until the prompts to restart the machine, and then restart.
2. Troubleshoot system blue screen errors
During the use of computers, you often encounter blue screens. For beginners, it seems like a computer disaster and they are at a loss. If we follow the solution information provided by the screen and prescribe the right medicine, it is not difficult to deal with the blue screen.
(I) Troubleshooting the Windows 2000 Blue Screen of Death
1. Why does the blue screen of death appear?
Theoretically, pure 32-bit Windows 2000 will not crash, but this is only theoretical. Viruses or hardware and hardware driver mismatch will cause Windows 2000 to crash. When Windows 2000 crashes, the monitor screen will turn blue, and then a Stop fault message will appear.
In Windows 2000, blue screen information is usually divided into stop messages and hardware messages. The stop message refers to an error message generated when the Windows 2000 kernel discovers a software error that it cannot recover. Hardware messages refer to error messages that occur when Windows 2000 discovers a serious hardware conflict.
Usually, the blue screen information that appears can be divided into separate parts, each containing valuable error handling information. These parts include:
Bug checking part: This is where the actual error message is included in the blue screen information. In this part, you should pay attention to the error code (i.e. the hexadecimal number after "Stop") and the error symbol (i.e. the word immediately after the error code).
Recommended User Action Section: This section often contains some general messages that guide you on how to correct errors.
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 your computer and debug processes.
2. General solutions
(1) First use the new version of antivirus software to check whether there are viruses on the computer.
(2) If Windows 2000 can be started, please check the information in the "Event Viewer" to determine the device or driver that caused the failure. The method to start "Event Viewer" is: click "Start → Settings → Control Panel → Administrative Tools → Event Viewer → System Log".
(3) If the computer cannot be started, try to start the computer in "Safe Mode" or "Last Correct Configuration", and then delete or disable the newly installed additional programs or drivers. If the computer cannot be started in Safe Mode, you can use Repair Console. "Repair Console" can disable some services, rename device drivers, repair boot sectors, or master boot records.
(4) Remove the newly installed hardware devices (memory, adapter card, hard disk, modem, etc.).
(5) Make sure that the drivers of the hardware device have been updated and the system has the latest BIOS, and disable the memory caching function in the BIOS.
(6) Run system diagnostic tools provided by computer manufacturers, especially memory checks.
(7) Check the Microsoft compatible hardware list (HCL) to ensure that all hardware and drivers are compatible with Windows 2000. In the Windows 2000 installation CD\Support folder.
(If you cannot log in, restart the computer. After the list of available operating systems is displayed, press the F8 key. On the Advanced Options screen, select the "Latest Correct Configuration" option to start the computer.
Note: When using the most recent correct configuration, the system settings changes made since the last successful startup will be lost.
3. Special blue screen information
Stop message: 0x0000000A fault (the device has been installed)
Explanation text: IRQLNOTLESSOREQUAL
Normal reason: The driver uses an abnormal memory address.
Solution: If Windows 2000 can still be started, check the relevant information displayed in the Event Viewer to determine the device or driver that causes the problem; turn off or disable some newly installed drivers and delete newly installed additional programs; remove some newly installed hardware; make sure that the drivers of the hardware device have been updated, and the system has the latest BIOS, and disable memory caching functions in the BIOS, such as Cache or Shadow; run the system diagnostic tools provided by the computer manufacturer, especially memory checks; check the Microsoft compatible hardware list (HCL) to ensure that all hardware and drivers are compatible with Windows 2000; restart the computer and select "Last correct configuration" to start the computer.
Stop message: 0x0000000A fault (when a new device was just added)
Explanation text: IRQLNOTLESSOREQUAL
Normal reason: The driver uses an abnormal memory address.
Solution: During the installation process, when the screen prompts "The installer is checking the computer hardware configuration", press the F5 key and select the appropriate computer type according to the prompt. For example, when the computer is a single processor, please select "Standard PC"; disable the memory cache function in the BIOS, remove all adapter cards, and disconnect all hardware devices that are not necessary to start the computer, and then reinstall Windows 2000; if the system is equipped with a SCSI adapter card, please request the latest Windows 2000 driver from the adapter card vendor, disable the synchronization negotiation function, and check the SCSI ID number of the terminal head and device; if the system is equipped with an IDE device, set the IDE port to Primary. Check the Master/Slave/Only settings of the IDE device. Except for the hard drive, remove all other IDE devices; run system diagnostic tools provided by the computer manufacturer, especially memory checks; check the Microsoft compatible hardware list (HCL) to ensure that all hardware and drivers are compatible with Windows 2000; select "Last correct configuration" to start the computer.
Stop message: 0x0000001E fault
Explanation text: KMODEEXPTIONNOTHANDLED
Common cause: Disk failure.
Solution: Check for sufficient disk space, especially new installations; disable the drivers displayed in the Stop message and all newly installed drivers; if the video driver used is not provided by Microsoft, try switching to the standard VGA driver or the appropriate driver supported by Windows 2000; make sure the system has the latest BIOS; select "Last correct configuration" to start the computer.
12Next pageRead the full text