Computer FAQs and solutions page 1/2

When the computer is started and running, if there is a fault, the corresponding error message will appear. We can follow the prompts to solve the current fault. However, most of these prompts are in English or machine code, which is confusing. This article collects and sorts out the error messages that often occur during computer startup and running, and provides a complete solution, hoping to help you in troubleshooting.
1. troubleshoot system startup errors
A complete system startup process requires the close cooperation of the system BIOS and the operating system. If an error occurs in a link, the system startup will fail.
1. Explanation of BIOS self-check prompt
When an error is reported during BIOS detection, prompts of varying lengths are usually sent. Different prompts indicate different error messages. Based on the meaning of these messages, it is not difficult to make a diagnosis. The following describes the meanings of the self-check alarm code by taking the two common BIOS (Award BIOS and ami bios) as an example:
(1) Award BIOS self-check prompt explanation:
1 short: the system starts normally. This is what we can hear every day. It also indicates that the computer has no problems.
2 short: A general error occurs. Enter CMOS Setup and reset the incorrect options.
1 long and 1 short: an error occurs in RAM or the motherboard. Try another memory. If it still doesn't work, you have to replace the motherboard.
1 long 2 short: Incorrect display or video card.
1 long 3 short: Incorrect keyboard controller. Check the motherboard.
1 long 9 short: The Flash RAM or EPROM on the motherboard is incorrect, and the BIOS is damaged. Try changing block Flash RAM.
Keep ringing: the power supply and display are not connected to the video card. Check all the plugs.
Duplicate short response: power supply problems.
No sound, no display: power supply problems.
(2) Description of the ami bios self-check prompt:
1 short: failed to refresh the memory. Replace the memory stick.
2 short: Memory ECC verification error. In CMOS Setup, setting the ECC check option to Disabled can solve the problem. The most fundamental solution is to change the memory.
3 short: the system basic memory (1st 64 MB) Check failed. Change memory.
4 short: system clock error.
5 short: the CPU is incorrect.
6. Short: the keyboard controller is incorrect.
7. Short: The system real-time mode is incorrect and cannot be switched to the protection mode.
8: memory error is displayed. The Display memory is faulty. Try changing the video card.
9 short: rom bios check and error.
1 long 3 short: memory error. Memory Corruption. Change the memory.
1 long, 8 short: The test error is displayed. The display data cable is not plugged in or the video card is not plugged in.
2. Detailed description of Award BIOS startup information
When the computer starts BIOS self-check, the error message is generally followed by a similar prompt:
"Press F1 to Continue or Press DEL to Enter Setup"
Press F1 to continue or DEL to enter the CMOS settings ".
The following is a common error message about Award BIOS during system self-check:
Message: bios rom checksum error-System halted
Common Cause: BIOS verification error-system shutdown. This indicates that the code in the BIOS chip of the Computer Board is incorrect during verification, or the BIOS chip itself or its content is damaged.
Solution: You need to rewrite your BIOS or replace a new BIOS chip.
Message: CMOS battery failed, CMOS battery is no longer functional
Common Cause: After the CMOS battery is exhausted, all settings in CMOS will be lost.
Solution: replace a new battery.
Message: CMOS checksum error-Defaults loaded
Common Cause: if an error is found when the BIOS verifies the CMOS settings, the system will load the default device configuration information. The CMOS calibration error often indicates that there is an error in the CMOS settings. This error may also be caused by insufficient power of the motherboard battery.
Solution: Check your battery and replace one if necessary.
Prompt message: Display switch is set incorrectly
Common cause: the display switch settings on the motherboard do not match the display type actually used.
Solution: some computer boards are equipped with a display switch, you can choose to use a monochrome or color display. In this case, first confirm the display type, then shut down the system, and set the corresponding display jumper. If there is no display switch on the motherboard, we should enter the system CMOS settings to change the display type.
Message: Press ESC to skip memory test
Common Cause: Press ESC to skip the memory check.
Solution: The machine must detect the memory every time it is cold-started. If you do not want the system to detect the memory, Press Esc to skip this step.
Message: Floppy disk (s) fail
Common Cause: an error occurs in the drive.
Solution: when the computer is started, if the drive controller or drive is not found or cannot be correctly initialized, the system will prompt this. In this case, check whether the software drive controller is properly installed. If the software drive controller is integrated on the motherboard, check whether the options of the software Drive Controller in CMOS are "Enabled.
If the drive is not installed on the machine, check whether the drive item is set to "None" in the CMOS settings ".
Message: HARD DISK INSTALL FAILURE
Common Cause: hard disk installation fails. When the computer is started, if the hard disk controller or hard disk itself is not found or cannot be correctly initialized, the computer will give the above prompt.
Solution: Check whether the hard disk controller is correctly installed or whether the hard disk controller option in CMOS is "Enabled ".
If the hard disk is not installed on your computer, make sure that the hard disk type is "None" or "Auto" in the system settings ".
Message: Keyboard error or no keyboard present
Common cause: the keyboard is incorrect or the keyboard is not installed. If the system cannot initialize the keyboard when the computer starts, this information is displayed.
Solution: Check whether the keyboard is connected to the computer correctly and whether a key is pressed when the computer starts.
If you want to set your computer to work without a Keyboard, you can set the "Halt On" option to "Halt On All, But Keyboard" in CMOS, when the computer starts, the keyboard errors are ignored.
Prompt message: Keyboard is locked out-Unlock the key
Common Cause: This message usually appears when one or more keys are held down when the computer is started.
Solution: Check whether something is on the keyboard.
Message: Memory test fail
Common cause: the memory test fails. When the computer is started, if an error is detected in the memory test step, the above message is displayed, indicating that an error is encountered during internal self-check.
Solution: you may need to change the memory.
Message: Override enabled-Defaults loaded
Common Cause: if the computer cannot start normally under the Current CMOS configuration, the BIOS of the computer will automatically call the default CMOS settings for work.
Solution: the default CMOS setting is the most stable but conservative CMOS configuration parameter.
Message:. Primary master hard disk fail
Common cause: the primary disk on the first IDE interface has an error.
Solution: when the computer is started, if an error occurs on the primary hard disk on the first IDE hard disk interface of the machine, the above prompt is displayed.
3. troubleshoot system startup errors
After the BIOS self-check is completed, the system boot work is handed over to the operating system. If the system encounters an error, the normal startup of the system will also be affected. Common error messages are as follows:
Message: Cache Memory Bad, Do not enable Cache!
Common cause: the BIOS finds that the high-speed buffer memory on the motherboard is damaged.
Solution: contact the vendor or seller for solutions.
Message: Memorx paritx error detected
Common Cause: Memorx paritx error detected, that is, the memory parity error indicates that the memory system is faulty.
Solution: follow these steps to check and handle the problem:
Whether different types of memory are mixed in the system, such as memory with parity check and no parity check. In this case, try using only one memory ;. in the Advanced BIOS Features (Advanced BIOS Features) option in BIOS settings, set the "Quick Power On Self Test" setting to Disabled ), when the system starts, the system will perform three tests on the system memory bit by bit to preliminarily determine whether the system memory is faulty. If the fault persists, in the Advanced Chipset Features (Advanced Chipset Features) option in BIOS settings, set the speed of memory (SDRAM) related options to a little slower, this method can eliminate the failure of memory speed not keeping up with the system bus speed; poor CPU internal Cache performance will also lead to such a failure, which can be in the Advanced BIOS Features (Advanced BIOS Features) option, disable the Cache-related options. If the fault is caused by the Cache, perform cooling for the CPU, If not, you have to downgrade the CPU usage.
Message: Error: Unable to ControLA20 Line
Common Cause: poor contact between the memory stick and the motherboard slot, and memory controller failure.
Solution: Check whether the memory stick is in good contact with the slot or replace the memory stick.
Message: Memory Allocation Error
Common Cause: Xms is not used in the config.sysfile for memory management files such as himem.sys1_emm386.exe. due to the EMS Memory or improper settings, the system can only use the 640KB basic Memory, and the system prompts "Out of Memory" (insufficient Memory) when running the program.
Solution: these phenomena are soft faults. Compile the system configuration file Config. sys and restart the system.
Message: C: drive failure run setup utility, press (f1) to resume
Common cause: the hard disk parameter settings are incorrect.
Solution: You can use a floppy disk to boot the hard disk, but you need to reset the hard disk parameters.
Prompt message: HDD Controller Failure
Common Cause: Hard Drive Interface contact is poor or wiring error.
Solution: first check the connection between the hard drive power cord and the hard drive, and then check the connection between the hard drive data cable and the multi-function card or hard drive.
Message: Invalid partition table
The common cause is that the partition table in the Boot Record of the hard disk is incorrect. When multiple auto-lifted partitions are specified (only one auto-lifted partition is allowed) or the virus occupies the partition table, the above prompt will be displayed. When the Boot Record (MBR) is located at 0 head/0 cylinder/1 sector, it is generated when FDISK partitions hard disk. MBR consists of three parts: the Main Boot Program, the partition table, and the ending sign 55 AAH, which occupy a single sector. The main boot program contains the program code, error information, and error handling for checking the hard disk partition table. When the hard disk is started, the main Bootstrap will check the auto-lifting flag in the partition table. If a partition is a user-defined partition, it indicates 80 H. Otherwise, the system requires that only one partition is a user-defined partition. If a partition table contains multiple user-defined indicators, the main Bootstrap will give an error message "Invalid partion table.
Solution: Use KV3000 to check whether the active partition mark and partition end mark (55 AA of 1FE and FF) of the hard disk partition record are lost. The simplest solution is to use NDD to fix errors in the partition table. If an error is found, you will be asked if you are willing to modify the error. You only need to continuously answer YES to correct the error, you can also use the partitioned table that has been backed up to overwrite it (the RESCUE in KV300 and NU8.0 all have the function of backing up and restoring the partitioned table ). If the partition table is infected with virus, the problem cannot be solved by formatting. You can use anti-virus software and NDD to fix the problem.
If none of the above methods can be solved, another method is to use FDISK to re-partition, but the partition size must be the same as the original partition. do not perform advanced formatting after the partition, then use NDD to fix the problem. The recovered hard disk can be started, and the information on the hard disk will not be lost. In fact, the FDISK partition is used to overwrite the original partition table with the correct partition table.
Message: No Rom Basic, System Halted
Common cause: the boot program is damaged or infected with virus, or the partition table does not have a self-lifting flag, or the ending flag 55 AA is rewritten.
Solution: start from a floppy disk and run "FDISK/MBR. FDISK contains the primary boot program code and the ending sign 55 AA. Use the above command to overwrite the primary boot program on the hard disk with the correct primary boot program and ending sign in FDISK. NDD can be used to restore a partitioned table that does not have a self-lifting flag.
Prompt message: HDD Controller Failure
Common Cause: there are roughly three possible causes of this error, which may be due to poor contact with the IDE data line or reverse connection of the data line interface ;. the worst case is periodic noise such as "Da, da, da" on the hard disk during self-check, which indicates that the mechanical control part or the drive arm is faulty; hard Disk disks have serious damage.
Solution: reconnect to the disk correctly or replace the hard disk.
Tip: Primary IDE channel no 80 conductor cable installed
Common cause: the above situation indicates that the hard disk does not use a hard disk line of the 80-pin type.
Solution: due to the large increase in transmission speed, in order to reduce interference, in ATA100 hard disk specifications, 80-pin hard disk lines are required, and 40 ground wires are added.
Message: Disk Boot Failure, insert system disk and press enter
Common Cause: The above error is caused by a connection problem between the hard disk and the motherboard.
Solution: First, open the chassis and connect the hard disk data line to the power source to confirm that the contact is normal. If it still fails to be detected, remove the hard disk and try another hard disk to see if it is normal. If it is still abnormal, it is likely to be a problem with the motherboard. If it is normal, it is a problem with the hard disk.
Message: Bad of Missing Command
Common Cause: This indicates that the Command.com file is damaged or lost. It may be overwritten or changed when other software is installed.
Solution: simply copy the Command.com file on the same boot floppy disk to the root directory of the hard drive boot area and restart it.
Message: No System Disk or Disk Error
Common cause: the boot disk is not a system disk, or the system file of the original boot disk is damaged.
Solution: first, make sure that the floppy disk in the soft drive is the system disk. Second, you should pay attention to whether the system files on the system hard disk are damaged. If the files have been damaged, you can start the boot disk of the same version, and use the sys c: Command to upload the correct system files to the boot hard disk.
Message: Error Loading Operating System or Missing Operating System
Common Cause: DOS Boot Record errors, or partition ending signs 55 AA are damaged. This may be due to the system file Io under the hard disk. sys and Msdos. sys is damaged, or the hard disk dos boot Record (BOOT) is damaged, or the end mark of the dos boot Record (55 AA of 01 FE and FF) is lost, it may also be that the Master Boot data of the hard disk is damaged, or the master boot end mark (55 AA of 080 And 081) is lost.
Solution: first, use the sys c: Command to restore the system file. If not, use Diskedit to modify the end mark of the hard drive Master Boot (55 AA of 080 And 081 ); if it still doesn't work, it will only start with a floppy disk, use Fdisk to re-partition, format and re-install the operating system.
Tip: you can close the computer safely now.
Common cause: the most likely cause is that the Windows system file VMM32.VXD is damaged or cannot be found.
Solution: Enter the DOS environment, copy the file from another computer to your computer's Windows System directory, and then reboot to enter. If you cannot copy this file from another computer, reinstall the operating system.
Prompt message: Invalid system disk
The common cause is that the device that can start the computer cannot be found at startup.
Solution: If you set the boot sequence to A and C, check whether A disk is not the boot disk in the soft drive.
If not, check your hard disk to see if the BIOS can correctly detect this hard disk. If you have not blocked this hard disk or moved this hard disk, check whether the data cable is damaged.
If the problem persists, it is probably because some files are not installed during Windows 98 upgrade, or because of virus, some anti-virus software may conflict with hard disk management software. If an error occurs because an antivirus software is running, start the computer with the boot disk generated during Windows 98 installation and run the following command at the DOS prompt:
CD \ Windows \ command
Attrib c: \ msdos. sys-s-h-r
Copy c: \ msdos. xxx
A:
Sys c:
C:
Attrib c: \ msdos. sys-s-h-r
Del c: \ msdos. sys
Copy c: \ msdos. sys
Attrib c: \ msdos. sys + s + h + r
After you reinstall the system file, remove the boot disk and restart the computer.
If hard disk management software is used, and Windows 98 does not detect it, it will overwrite the Boot Record (MBR). For the fault caused, refer to the manual of the software to recover MBR.
Another cause can also lead to this fault. Check whether the two numbers in the FSLog row in setuplog.txt are the same, for example, FSLog: BIOS Heads =: 255:, BootPart Heads =: 255 :. The two numbers must be the same. If they are different, reinstall the system file as described above. If it is caused by a virus, completely clear the virus and reinstall Windows 98.
Message: Disk I/O Erro1; Replace disk and press ENTER
Common Cause: Your machine loses the Startup File.
Solution: Create a boot disk on another machine, put it in your drive, and copy the lost file to the hard disk. If not, reload the system again.
However, if your machine is infected with the CIH virus, it may also happen because the CIH virus has rewritten your hard disk partition table, leading to the loss of active partitions, you only need to use the Fdisk command to reactivate the hard disk.
Message: * The. vxd file is invalid.
Common Cause: incorrect operation on disk files causes VXD file loss.
Solution: first check whether the Vnetsup. vxd file is lost. If the Vnetsup. vxd file is lost, install it and then delete the network component to avoid this problem:
Click Start> set> Control Panel> network, click Add, select the adapter option, and click Add. In the vendor box, click "Network Driver detected ". In "network adapter", click "existing Ndis2 driver", and then click "OK.
When the system prompts you to enter the workgroup name and computer name, enter the corresponding box on the "identification" tab and click "OK" or "close" until "Control Panel" is returned ".
When the system prompts you to restart the computer, click "OK", restart the computer, and click "Start> set> Control Panel> network" in turn ", click "existing Ndis2 driver", click "delete", click "OK", and then click "OK" to restart the computer.
If the problem persists, check whether the StaticVxD value in the registry is correct. If the error message does not specify a device driver, correct the StaticVxD value in the Registry: use Registry Editor to find and delete StaticVxD values that contain only invalid data, empty data, or spaces. The StaticVxD value is located under HKEYLOCALMACHINE \ System \ CurrentControlSet \ Services \ VxD.
Note: Back up the Registry file before the operation.
If the preceding method does not work, check 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 corresponding uninstall tool.
Message: * 386 the file is invalid.
Common cause: the system device driver is lost.
Solution: Disable the settings driver in the System. ini file. The method is as follows:
Click Start> Run. In the open box, type Msconfig. On the System. ini tab in the displayed dialog box, double-click [ENH. Locate the line that involves the device driver, click the clear check box next to the line, and then click "OK" to restart the computer.
Message: kavkrnl. vxd is missing.
Common Cause: incorrect operation on disk files causes VXD file loss.
Solution: You can copy the file to another computer (note that the file name must be consistent with the Windows version) and put it under the corresponding directory.
You can also use the extract.exe command in Windows 98to recover from the installation file *. cab of Windows 98. When we know the location of the system file to be restored in the installation disc, we can use "EXTRACT/Y Windows 9827.cab kavkrnl. vxd command (from Windows 98 installation disc named Windows 9827. restore Kavkrnl in the cab package. vxd file ).
However, if you do not know the exact location of the file, use "Extract/D Windows 98 *. CAB "(at this time * represents the number of the CAB file package) for each CAB file to view Cdfs. vxde.
Message: *. dll cannot be started.
Common Cause: there are multiple types of information, such as "the file Comtcl32.dll cannot be started, please check the file identification problem" and "the file Condlg32.dll cannot be started, check the file identification problem, and the file Shell32.dll cannot be started. Check the file identification problem. After you click "OK", "EXPLORER caused an exception 6d007eH inmodule EXPLORER. EXEatxxx: xxxxxxxx" appears ". This is because of the following files: Commctrl. dll, Commdlg. dll Shell. dll, ver. dll, Mmsystem. all dll files (or files in one of them) have errors or are replaced by some program files.
Solution: use the correct file to overwrite \ Windows \ System.
These files can be found in C: \ Windows \ Sysbckup. After finding these files, copy them directly to C: \ Windows \ System. If C: \ Windows \ Sysbckup does not exist, the source file in the Extract installation disk is required (the extension method is the same as above ).
Message: Watning: Windows has detected registry/configuration error. Choose Safe mode to start Windows with a minimal set of drivers ."
Common Cause: The registry or important files are lost.
Solution: first, enter security mode. The Registry Program dialog box is displayed, and then select "Restore and restart from backup". It does not matter even if you have not backed up the registry, every time the registry is modified, Windows 98 will automatically generate a registry backup. If the registry can be restored successfully, Windows 98 will prompt you to restart the computer and the system will be normal after the restart. If the registry cannot be restored, we recommend that you disable the computer and reinstall Windows 98. In this case, if you have backed up the registry, use your backup to restore it. Otherwise, reinstall Windows 98.
Tip: Cannot find a device file that may be needed to run Windows or a Windows application. The Windows Registry or System. ini refers to this ......
Common Cause: mainly in System. the Virtual Device Driver (VXD) involved in the INI file or volume note table does not exist or is damaged, or a Static VXD value in the registry contains incorrect data.
Solution: first, follow the suggestions in the error message. If only some applications to be deleted are deleted, uninstall them all. The best solution is to reinstall the application and run the anti-installation program, if there is no anti-installation program, you should refer to the methods provided in the application reference manual to uninstall all. If the file indicated in the error message is an application to be retained, reinstall the application. If not, edit the registry and delete all the error messages in the registry. The Registry is an important file of Windows 98. If it is damaged, Windows 98 will not work, backup should be performed before any modification.
Message: Not enough MEmory to convert the drive to FAT32 to free up MEmory, REM all state MEnts in the AUTOEXEC. BAT and the CONFIG. SYS files.
Common Cause: in general, this information appears when the hard disk is converted to the FAT32 format, when the structure of the directory on the hard disk to be converted is too large, this error is triggered when there is not enough regular memory for storage.
Solution: We recommend that you optimize the memory and load the memory resident program in the Config. sys and Autoexec. bat files to the high end to obtain more general memory.
Message: This program has saved med an illegal operation and will be shutdown. If the problem persists, contact the program vendor.
Common Cause: If you press the "Details" button, Windows 98 will display the error message "MSINFO32 caused an invalid page fault in module KERNEL32.DLL at015f: bff8XXXX. ", this is caused by a file calling MSINFO32. Running the "System Information" tool on Windows 98 may trigger this error.
Solution: use the new msinfo32.exe file to replace the file with the original error. You can use the System File Check tool to extract the file from the Windows 98 installation CD. This program will intelligently check the system file: click "start from" run ", input" “sfc.exe ", and click" OK. In the system file check window, select "extract a file from the installation software disk", enter "msinfo32.exe" in the input box, click "start", follow the prompts for installation, and restart the machine until the prompt is restarted.
2. troubleshoot system blue screen errors
During computer use, blue screens are often used. It seems like a computer disaster for beginners. If we follow the solution information provided on the screen, it is not difficult to deal with the blue screen.
(1) troubleshooting of Windows 2000 blue screen crash
1. Why does Blue Screen crash?
Theoretically, 32-bit Windows 2000 won't crash, but this is just theory. A Windows 2000 crash may occur due to viruses or hardware and hardware driver mismatch. When Windows 2000 crashes, the screen turns blue and a Stop fault message appears.
In Windows 2000, blue screen information is generally divided into stop messages and hardware messages. The stop message is an error message generated when the Windows 2000 kernel discovers a software error that cannot be recovered. A hardware message is an error message generated when a severe hardware conflict is detected in Windows 2000.
Generally, the displayed blue screen information can be divided into several independent parts, each part contains valuable error handling information. These parts include:
Bug check: this is the location where the blue screen information contains the actual error message. In this section, you should note the error code (that is, the hexadecimal number after "Stop") and the error symbol (that is, the word following the error code ).
Recommended actions: This part often contains messages that guide you in how to correct errors.
Debug port information: This part contains information about how to set your kernel debugger. The kernel debugger is a tool that allows you to manually connect to a computer and debug processes.
2. General Solution
(1) first, use the new anti-virus software to check whether Viruses exist on the computer.
(2) If Windows 2000 can be started, check the information in Event Viewer to identify the device or driver that caused the fault. To start the Event Viewer, choose Start> Settings> Control Panel> Administrative Tools> Event Viewer> system logs ".
(3) If the computer cannot be started, try to start the computer in "safe mode" or "Last correct configuration" and then delete or disable newly installed additional programs or drivers. If the computer cannot be started in "safe mode", you can use "repair console ". The repair console allows you to disable services, rename device drivers, repair boot sectors, or Master Boot records.
(4) Remove the newly installed hardware devices (such as memory, adapter, hard disk, and modem ).
(5) ensure that the driver of the hardware device has been updated and the system has the latest BIOS. Disable the memory cache 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. HCL.txt is in the Windows 2000 installation CD \ Support folder.
(If you cannot log on, restart your computer. After the list of available operating systems is displayed, press F8. On the "advanced options" screen, select the "Last correct configuration" option to start the computer.
Note: When the last correct configuration is used, the system settings changes made since the last successful start will be lost.
3. Special blue screen information
Stop message: 0x0000000A fault (device installed)
Description: IRQLNOTLESSOREQUAL
Common cause: the driver uses an abnormal memory address.
Solution: If Windows 2000 can also be started, check the information displayed in the event viewer to identify the device or driver that caused the problem; turn off or disable some newly installed drivers, and delete newly installed additional programs; remove some newly installed hardware; ensure that the driver of the hardware device has been updated, and the system has the latest BIOS to disable the memory Cache function in the BIOS, such as Cache or Shadow; run the system diagnostic tools provided by the computer manufacturer, especially the memory check; 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 is added)
Description: IRQLNOTLESSOREQUAL
Common cause: 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 F5 and select the appropriate computer type as prompted. For example, when the computer is a single processor, select "standard PC"; disable the memory cache function in BIOS, remove all adapter cards, and disconnect all hardware devices that are not necessary to start the computer, reinstall Windows 2000. if the system is equipped with a SCSI adapter, ask the adapter vendor for the latest Windows 2000 driver, disable the synchronization negotiation function, and check the terminal header and the scsi id of the 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. Remove all other IDE devices except hard disks; run system diagnostic tools provided by computer manufacturers, especially Memory checks; check the Microsoft compatible hardware list (HCL ), make sure all hardware and drivers are compatible with Windows 2000. Select "Last correct configuration" to start the computer.
Stop message: 0x0000001E fault
Description: KMODEEXPTIONNOTHANDLED
Common Cause: disk fault.
Solution: Check whether there is sufficient disk space, especially new installation. Disable the drivers and all newly installed drivers displayed in the Stop message; if the video driver is not provided by Microsoft, try to switch to the standard VGA driver or the appropriate driver supported by Windows 2000; ensure that the system has the latest BIOS; select "Last correct configuration" to start the computer.