Computer in the start-up and operation process, if there is a fault will appear corresponding error message, we can follow the prompts to resolve the current problem. But most of these tips are in English prompts or machine code, which makes people deeply puzzled. This article collects the computer in the startup, the operation process often appears the error message information, and gives the complete solution, hoped can be helpful to you in the elimination breakdown.
First, troubleshooting system startup errors
A complete system boot process requires a close collaboration between the system BIOS and the operating system. If a link goes wrong, it causes the system to fail to start.
1.BIOS self-test hint sound interpretation
BIOS detection of errors in general will be issued in the length of the prompts, different prompts to represent different error messages, according to the meaning of this information, and then do the corresponding diagnosis is not difficult. The following is an example of two common BIOS (award BIOS and AMI BIOS) to describe the specific meaning of the post Bell code:
(1) Award BIOS self-Test prompt interpretation:
1 short: The system starts normally. This is what we hear every day, and it shows that there are no problems with the computer.
2 Short: General error, please go to CMOS setup and reset the incorrect option.
1 long 1 short: RAM or motherboard error. Try another memory, if not, have to replace the motherboard.
1 long 2 short: monitor or video card error.
1 Long 3 short: Keyboard controller error. Check the motherboard.
1 Long 9 short: motherboard Flash RAM or EPROM error, bios damage. Try the flash RAM for another piece.
Keep ringing: The power supply, monitor does not connect with the video card well. Check all the plugs.
Repeat short sound: power problem.
No sound no display: power problem.
(2) BIOS self-Test tips for Ami:
1 Short: Memory refresh failed. Replace the memory strips.
2 short: Memory ECC checksum error. In the CMOS setup, the memory about ECC checksum option is set to disabled, the most fundamental solution is to replace the memory.
3 Short: System basic Memory (1th 64MB) check failed. Swap memory.
4 Short: System clock error.
5 Short: Central processing unit (CPU) error.
6 Short: Keyboard controller error.
7 short: System Real mode error, can not switch to protection mode.
8 Short: Memory error displayed. There is a problem with memory, try replacing the video card.
9 Short: ROM BIOS check and error.
1 Long 3 short: Memory error. Memory is damaged and can be replaced.
1 Long 8 short: Display test error. The monitor data cable is not plugged in or the video card is not plugged in.
2.Award BIOS Startup Information detailed
When the computer boots the BIOS self-test, there are generally similar prompts following the error message:
"Press F1 to Continue" or presses DEL to Enter Setup
"Press F1 to continue or press the DEL key to enter the CMOS settings".
The following is a common award BIOS error message that may be given if a failure occurs during system self-test:
Hint: BIOS ROM checksum Error-system halted
Common Cause: BIOS checksum error-system downtime. This indicates that the code in the BIOS chip of the computer's motherboard found an error in the checksum, or that the BIOS chip itself or its contents were damaged.
WORKAROUND: You need to rewrite your BIOS content, or replace a new BIOS chip.
Hint: CMOS battery failed,cmos battery is no longer functional
Usually the reason: After the CMOS battery is depleted, all content set in CMOS will be lost.
Solution: Replace a new battery.
Hint information: CMOS checksum error-defaults loaded
Usually the reason: the BIOS will load the default device configuration information if it finds an error while verifying the contents of the CMOS settings. CMOS calibration errors often imply errors in the contents of the CMOS settings, which may also be due to insufficient battery power on the motherboard.
WORKAROUND: Please check your battery and replace it if necessary.
Hint: Display switch is set incorrectly
Usually the reason: the settings for the display switch on the motherboard do not match the display type that is actually used.
Workaround: Some computers have a display switch on the motherboard, and you can choose to use a monochrome or color display. At this point, first confirm the display type, then turn off the system and set the appropriate 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.
Message: Press ESC to skip memory test
Usually the reason: press the ESC key to skip memory detection.
Solution: The machine in every cold start, to detect memory; At this point, if we do not want the system to detect memory, you can press the ESC key to skip this step.
Tip: Floppy disk (s) fail
Common Cause: Floppy drive error.
Solution: When the computer starts up, if the floppy drive controller or floppy drive is not found or can not be properly initialized, then the system will appear such a hint. At this point please check the floppy drive controller installation is good, if the floppy drive controller is integrated on the motherboard, then we also need to check the CMOS the floppy disk controller option is in the "Enabled" state.
If the floppy drive is not installed on the machine, check to see if the floppy drive entry is set to None in the CMOS settings.
Hint message: HARD DISK INSTALL failure
Usually the reason: the hard drive is not installed successfully. When the computer starts up, if the hard disk controller or hard disk itself is not found or incorrectly initialized, the computer will give the above hints.
WORKAROUND: Please determine if the hard disk controller is properly installed or if the option for the hard disk controller in the CMOS is "Enabled."
If you do not have a hard drive installed on your computer, verify that the hard disk type is "None" or "Auto" in the system setup.
Prompt message: Keyboard error or no keyboard present
Usually the reason: keyboard error or no keyboard installed. When the computer starts, if the system cannot initialize the keyboard, this information is given.
Workaround: Please check the keyboard and the computer connection is correct, the computer starts whether has the key to press.
If you want to deliberately set up your computer to work without a keyboard, then we can set the Halt on option to "Halt on All,but keyboard" in the CMOS so that the keyboard error is ignored when the computer starts.
Hint: Keyboard is locked out-unlock the key
Usually the reason: This message typically occurs when a computer is started with one or more keys being held down.
Workaround: Check to see if anything is on top of the keyboard.
Prompt message: Memory test fail
Usually the reason: the memory test failed. When the computer starts, if an error is detected in the steps of the memory test, the above message is given, indicating that there is an error in the self-test.
WORKAROUND: You may need to replace the memory.
Prompt information: Override enabled-defaults loaded
Usually the reason: if the computer does not start properly under the current CMOS configuration, the computer's BIOS will automatically invoke the default CMOS settings to work.
WORKAROUND: The system's default CMOS settings are a set of most stable, but most conservative, CMOS configuration parameters.
Hint message:. Primary Master hard disk fail
Usually the reason: the primary hard drive on the first IDE interface fails.
WORKAROUND: When the computer is started, if the primary hard drive on the first IDE hard disk interface of the machine is detected to be wrong, the above prompts will be given.
3. Troubleshooting System startup Error Information
The BIOS self-test completes, the system boot work to the operating system, this time if the system encountered some kind of error, also can affect the normal boot of the system. The common error messages are as follows:
Hint message: Cache Memory bad,do not enable cache!
Usually the reason: the BIOS found that the cache memory on the motherboard is corrupted.
Solution: Please contact the vendor or vendor to resolve.
Hint message: Memorx PARITX error detected
Usually the reason: Memorx PARITX error detected, that is, memory parity error, indicating memory system failure.
WORKAROUND: Follow the steps below to check for processing:
Whether different types of memory strips are mixed in the system, for example, with parity and no parity of the memory, if this case, please use only one memory bar to try; In the BIOS setup, in the Advanced BIOS Features (Advanced BIOS feature) option, the "Quick power On self test (Fast power self-test) setting is set to prohibit (Disabled), system memory will be three test-by-bit, you can initially determine whether the system memory problems, if you still cannot resolve the failure, in the BIOS settings in the advanced The chipset Features (Advanced chipset Features) option sets the speed of memory (SDRAM)-related options to be slower, which eliminates the memory speed of the system bus speed failure, the CPU internal cache poor performance can also cause such a failure, can be in the advanced BIOS Features (Advanced BIOS features) option, turn off the cache-related options, if it is due to the cache caused by the fault, please for the CPU cooling work, if not, had to use the CPU frequency reduction.
Prompt message: error:unable to ControLA20 Line
Usually the reason: the memory stripe and the motherboard slot bad contact, memory controller failure performance.
Workaround: Carefully check the memory bar for good contact with the slot or replace the memory bar.
Hint message: Memory allocation Error
Usually the reason: this is because the Config.sys file does not use Himem.sys, Emm386.exe, such as memory management files set Xms.ems memory or improper settings caused, so that the system can only use 640KB basic memory, running the program a little stool appears "out of Memory "(out of memory) prompt, unable to operate.
Solution: These phenomena are soft fault, the system configuration file Config.sys after the system can be restarted.
Tip: c:drive Failure Run Setup utility,press (F1) to resume
Usually the reason: the hard drive parameter settings are incorrect.
Workaround: You can boot the hard disk with a floppy disk, but reset the hard drive parameters.
Tip: HDD Controller failure
Usually the reason: hard drive line interface is bad or wiring error.
Solution: First check the hard drive power cable and hard disk connection, and then check the hard drive data cable and multi-function card or hard disk connection.
Prompt information: Invalid partition table
Usually the reason: there are errors in the partition table in the master boot record of the hard disk, which is indicated when multiple bootstrap partitions are specified (only one bootstrap partition) or the virus occupies the partition table. When the boot record (MBR) is located in 0 heads/0 cylinders/1 sectors, it is generated when the hard disk is partitioned by FDISK. MBR includes the main bootstrapper, partition table and end sign AAH three parts, a total of one sector, the main boot program to check the hard disk partition table program code and error information, error handling and so on. When the hard disk is started, the master bootstrapper checks the bootstrap flag in the partition table. If a partition is a removable partition, then there is a partition mark 80H, otherwise 00 system rules can only have one partition for the bootstrap partition, if the partition table contains multiple bootstrap flags, the main bootstrapper will give "Invalid partion table" error prompts.
Workaround: Use KV3000 to view whether the active partition flag and partition end sign (1FE, FF) of the hard disk partition record are lost. The simplest solution is to fix it with NDD, which will check the error in the partition table, and if you find an error, you will be asked if you want to modify it, and you can fix the error by constantly answering yes, or by overwriting it with a backed-up partition table (KV300, NU8.0 Rescue, Has the ability to back up and restore partitioned tables). If the virus infected the partition table, format is not solve the problem, you can use anti-virus software antivirus, and then use NDD to repair.
If none of the above methods are resolved, there is another way to repartition with Fdisk, but the partition size must be the same as the original partition, do not make advanced formatting after partitioning, and then fix it with NDD. The repaired hard drive will not only boot, but also the information on the hard drive will not be lost. Instead, use the Fdisk partition to overwrite the original partition table with the correct partition table.
Prompt information: No Rom Basic,system halted
Usually the reason: The boot program is typically corrupted or infected by a virus, or there is no bootstrap flag in the partition table, or the end sign is rewritten.
Workaround: Boot from floppy disk and execute command "FDISK/MBR". Fdisk contains the master bootstrapper code and an end sign of AA, which enables the correct master bootstrapper and end flags in Fdisk to overwrite the master bootstrapper on the hard disk. There is no bootstrap flag in the partition table, NDD recovery is available.
Tip: HDD Controller failure
The usual reason: there are roughly three situations that can lead to this kind of error. This may be because the IDE data cable is bad, or the data line interface is reversed; at worst, when the hard drive appears "Da, Da, DA," The periodic noise, it indicates that the mechanical control part or the transmission arm has problems The disc of the hard disk has serious damage.
Workaround: Reconnect correctly, or replace the hard drive.
Tip: Primary IDE channel no conductor cable installed
Usually the reason: The above situation indicates that the hard drive is not using the 80-pin type of hard drive cable.
Solution: Due to the large increase in transmission speed, in order to reduce interference, in the ATA100 hard disk specification, it is required to use the 80-pin type of hard drive line, relatively speaking, the increase of 40 ground wire.
Tip: Disk Boot failure,insert system disk and press ENTER
Usually the reason: the connection problem between the hard disk and the motherboard will cause the above error.
Solution: First, please open the chassis, remove and then connect the hard drive data cable and power head, confirm contact with normal. If it is still not detected, it will be hard to remove, a hard drive to try to see if it is normal, if it is not normal is likely to be the problem of the motherboard, if the normal is the problem of hard disk.
Tip: Bad of Missing Command
Usually the reason: this means that the Command.com file is corrupted or missing. may be overwritten or altered while installing additional software.
Workaround: Simply copy the Command.com file on the same version of the boot floppy to the root of the hard disk boot area and reboot.
Tip: No System disk or disk Error
Usually the reason: indicates that the boot disk is not a system disk, or that the system files of the original boot disk have been compromised.
Workaround: First make sure the floppy disk in the floppy drive is the system disk. Second, notice if the system files on the system's hard disk are compromised, and if they are corrupted, they can be started with the same version of the boot disk, and the correct system files can be uploaded to the boot hard drive using the SYS C: command.
Tip: Error Loading operating system or missing operating system
Usually the cause is a DOS boot record error, or the partition's end sign is damaged. This may be because the system files Io.sys and Msdos.sys under the hard drive are compromised, or the hard drive DOS boot record (boot) is damaged, or the end sign of the DOS boot record (FE, FF, AA) is lost, or the master boot data for the hard disk is corrupted. or the main boot end flag (080, 081 AA) is lost.
Workaround: First try to restore the system files using the SYS C: command; If not, you can modify the end sign (080, 081 AA) of the hard drive main boot with Diskedit. If it's not going to work, then just floppy boot, repartition with Fdisk, and reinstall the operating system after formatting.
Tip: You can safely turn off your computer now.
Usually the reason: the most likely cause is that Windows uses a system file that is Vmm32.vxd corrupted or cannot be found.
Workaround: Enter the DOS environment, copy this file from another computer to your computer's Windows directory, and then reboot the system before you can enter it. If you cannot copy this file from another computer, please reload the operating system.
Prompt message: Invalid system disk
Usually the reason: the device that can start the computer cannot be found on the power-on.
Solution: If you set the boot sequence is a, C, then check the floppy drive is not put a disk is not the boot disks.
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, then check the data cable for damage.
If the problem is not resolved, it is likely that some files were not installed during the upgrade of Windows 98, perhaps because of a virus or some anti-virus software and hard disk management software. If the error is caused by running antivirus software, start the computer with the startup disk that was generated during the installation of Windows 98, and then execute the following command at a DOS prompt:
Cd\windows\command
attrib c:\msdos.sys-s-h-r
Copy C:\msdos 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
Remove the boot disk after reinstalling the system files and restart the computer.
If you are using the hard drive management software and Windows 98 does not detect it, the boot record (MBR) is overwritten, and the resulting failure should refer to the manual of the software to restore the MBR.
There are other reasons that can also cause this failure to check whether two digits in the Fslog row in Setuplog.txt are the same, such as Fslog:bios Heads=:255:,bootpart heads=:255:. These two numbers must be the same, and if they are different, reinstall the system files in the way above. If this is caused by a virus, you should reinstall Windows 98 after the virus has been completely cleaned up.
Tip: Disk I/O erro1;replace disk and press ENTER
The usual reason: because your machine lost the boot file.
Solution: Make a Startup disk on someone else's machine, put it in your floppy drive, copy the missing files to the hard drive, and then reload the system again.
However, if your machine is infected with the CIH virus, it is also possible that this phenomenon occurs because the CIH virus rewrites your hard disk partition table, resulting in the loss of the active partition, you can only use the FDISK command to reactivate the hard drive.
Hint: invalid *.vxd file
Common Cause: Incorrect operation of disk files, resulting in the loss of VxD files.
Workaround: First check if the Vnetsup.vxd file is missing, and if the Vnetsup.vxd file is missing, install and then remove the network components to avoid this problem:
Click "Start → set → control Panel → network", click "Add" button, select "Adapter" option, then click "Add" button, click "Detected Network Driver" in "Manufacturer" box. In network adapters, click Existing Ndis2 driver, and then click the OK button.
When prompted for a workgroup name and computer name, fill in the corresponding box on the Identification tab and click the OK or Close button continuously until you return to Control Panel.
When you are prompted to restart your computer, click "OK" button, restart the computer, click "start → settings → control Panel → network", click "Existing Ndis2 Driver", click the "Delete" button, then click "OK" button, click "OK" button to restart the computer.
If the problem is not resolved, check to see if the StaticVxD value is correct in the registry. If the error message does not specify a device driver, correct the StaticVxD value in the registry by using Registry Editor to find and delete StaticVxD values in the registry that contain only invalid data, empty data, or only spaces. The StaticVxD value is located under Hkeylocalmachine\system\currentcontrolset\services\vxd.
Note: Back up the registry files before you operate.
If this is not the case, please make sure you have recently removed the program from your computer. If you have recently removed a program or component from your computer, reinstall it, and then run the appropriate uninstall tool.
Hint: invalid *386 file
Usually the reason: the system device driver is missing.
WORKAROUND: Disabling the System.ini file involves setting up the driver in the following ways:
Click start → run, and in the Open box, type Msconfig, and in the Open dialog box, in the System.ini tab, double-click the [386ENH] item. Locate the line that involves the device driver, click to clear the check box next to the row, and then click OK to restart the computer.
Hint Message: Kavkrnl.vxd lost
Common Cause: Incorrect operation of disk files, resulting in the loss of VxD files.
Workaround: You can copy the file to another computer (note that the file name is consistent with the version of Windows) and put it under the appropriate directory.
You can also use the Extract.exe command in Windows 98 to recover from the Windows 98 installation file *.cab. We know that the system files you want to restore are located in the installation CD, you can use the extract/y Windows 9827.cab Kavkrnl.vxd command (named Windows 9827 from the Windows 98 installation CD). Recover the Kavkrnl.vxd file in the CAB compression package.
However, if you don't know the exact location of the file, use the extract/d Windows 98*. Cab "(At this point * represents the number of cab packages) to view cdfs.vxde for each CAB file.
Hint: *.dll cannot start
Usually the reason: this information has a variety of, such as "file Comtcl32.dll can not start, please check the problem of file discrimination", "file Condlg32.dll can not start, please check the file to determine the problem", "file Shell32.dll can not start, please check the file discrimination" and so on. Click "OK" and it will appear: "Explorer caused an exception 6d007eh Inmodule Explorer." Exeatxxx:xxxxxxxx ". This is because you have the following files: Commctrl.dll, Commdlg.dll Shell.dll, Ver.dll, Mmsystem.dll all (or one of the files) has been wrong or was replaced by some program files.
Workaround: Use the correct file to cover 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, you will need to extract the source file (extension method Ibid.) on the installation disk.
Hint message: Watning:windows has detected registry/configuration error. Choose Safe mode to start Windows with a minimal set of drivers. ”
Usually the reason: the registry or important files are missing.
Solution: First into Safe mode, the Registry Program dialog box is displayed, and then select Restore and restart from backup, even if you have not backed up the registry, because every time the registry is modified, Windows 98 automatically generates a backup of the registry, and if you can successfully recover the registry, Windows 98 prompts you to reboot the computer and the system is normal after reboot. If you cannot recover the registry, Windows 98 recommends that you shut down your computer and reinstall Windows 98. In this case, if you have backed up the registry, use your backup to restore it, or reinstall Windows 98.
Hint: Cannot find a device file, May is needed to run Windows or a Windows application. The Windows Registry or System.ini refers to this ...
Usually the reason: the virtual device driver (VXD) that is involved in the System.ini file or volume list is not present or corrupted, or contains incorrect data in a static VXD value in the registry.
Workaround: First of all, follow the advice in the error message, if you only partially delete the application to be removed, all uninstall the program, the best way is to reinstall and then run the anti-Setup program, if there is no reverse installation program, you should refer to the application of the reference manual to uninstall all. Reinstall the application if the file that is prompted in the error message belongs to the application that you want to keep. If it is not, edit the registry, delete all the error messages in the registry, the registry is an important file for Windows 98, and if damaged, Windows 98 will not work and should be backed up before any modifications are made to it.
Hint info: 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.
Usually the reason: this information generally occurs when the hard drive is converted to the FAT32 format, and this error is triggered when the directory on the hard disk being converted is too large to have enough regular memory to store.
WORKAROUND: It is recommended that you optimize the memory, and try to load the memory-resident program in the Config.sys and Autoexec.bat files into the high-end to get more regular memory.
Tip: This is has performed an illegal operation and would be shutdown. If the problem persists,contact the program vendor.
General Reason: The above error message, if the "Details" button is pressed, Windows 98 displays an error message: "MSINFO32 caused an invalid page fault in module KERNEL32. DLL at015f:bff8xxxx. ", which is caused by a file calling MSINFO32. This error can be triggered by running the System Information tool under Windows 98.
Workaround: Use Msinfo32.exe new file to replace the original error file, you can use System File Checker to extract this file from the Windows 98 installation CD, this program will intelligently check system files: Click "start → run", enter "Sfc.exe" and click "OK" button. In the System File Check window, select "Extract a file from the installation floppy", enter "Msinfo32.exe" in the input box, click the "Start" button, and follow the prompts to install until you are prompted to restart the machine, restart it.
Second, troubleshoot the system blue screen error
When you use a computer, you often encounter a blue screen. For beginners, it seems to be a computer disaster, overwhelmed. If we follow the solution provided by the screen, it is not difficult to deal with the blue screen.
(i) Excluding Windows 2000 blue screen Panic failure
1. Why is there a blue screen crash
In theory, pure 32-bit Windows 2000 does not panic, but that's only theoretically. A virus or hardware and hardware driver mismatch causes Windows 2000 to crash, and when Windows 2000 crashes, the monitor screen turns blue and the Stop failure message appears.
In Windows 2000, blue screen information is usually divided into stop messages and hardware messages. Where a STOP message is an error message that occurs when the Windows 2000 kernel discovers a software error that it cannot recover. Hardware messages are error messages that occur when Windows 2000 discovers a serious hardware conflict.
Typically, the blue screen information that appears can be divided into separate parts, each containing valuable error-handling information. These sections include:
Bug Check section: This is where the blue screen information contains the actual error message. In this section, you should be aware of the error code (that is, the hexadecimal digits after "Stop") and the error symbol (the word immediately following the error code).
Recommended users take action: This section often contains some general information that will guide you through the steps to correct the error.
Debug Port Information section: This section contains information about how you should set up your kernel debugger. The kernel debugger is a tool that allows you to manually connect to the computer and debug the process.
2. General Solution
(1) First use a new version of anti-virus software to check the computer for viruses.
(2) If Windows 2000 can be started, check the information in the Event Viewer to determine which device or driver is causing the failure. The way to start Event Viewer is to click "start → settings → control panel → admin tools → Event Viewer → system log".
(3) If you cannot start your computer, try to start your computer with Safe mode or Last Known Good configuration, and then remove or disable the newly installed add-in or driver. If you cannot start your computer in Safe mode, you can use the repair console. The repair console can disable some services, rename device drivers, overhaul the boot sector, or master boot records.
(4) Remove the newly installed hardware device (memory, adapter card, hard disk, modem, etc.).
(5) Ensure that the driver for the hardware device has been updated, and that the system has the latest BIOS to disable the memory caching feature in the BIOS.
(6) Run the system diagnostics provided by the computer manufacturer, especially the memory check.
(7) Check the Microsoft compatible hardware list (HCL) to ensure that all hardware and drivers are compatible with Windows 2000. HCL.txt is in the Windows 2000 installation CD \support folder.
(If you cannot log in, restart your computer.) After displaying the list of available operating systems, press the F8 key. On the Advanced Options screen, select the Last Known Good Configuration option to start the computer.
Note: When you use the last Known Good Configuration, you lose the system settings changes that you made since the last successful startup.
3. Special Blue screen Information
Stop message: 0x0000000a failure (device already installed)
Explanatory text: irqlnotlessorequal
Usually the reason: The driver uses an abnormal memory address.
Workaround: If Windows 2000 can also be started, check the information displayed in Event Viewer to determine which device or driver is causing the problem, turn off or disable some newly installed drivers, and remove the newly installed add-on; Ensure that drivers for the hardware device are updated, and that the system has the latest BIOS, disabling memory caching in the BIOS, such as cache or shadow, running system diagnostics tools provided by the computer manufacturer, especially memory checking; checking the Microsoft compatible hardware list (HCL) To ensure that all hardware and drivers are compatible with Windows 2000, restart your computer, and select Last Known Good Configuration to start your computer.
Stop message: 0x0000000a failure (just when new device is added)
Explanatory text: irqlnotlessorequal
Usually the reason: The driver uses an abnormal memory address.
WORKAROUND: When you are prompted during Setup to "Setup is checking computer hardware Configuration", press the F5 key to select the appropriate computer type as prompted. For example, when a computer is a single processor, select Standard PC, disable the memory caching feature 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, Request the Shang vendor to obtain the latest Windows 2000 driver, disable the Sync negotiation feature, check the SCSI ID number of the Terminator and device, and set the IDE port to primary if the system is equipped with an IDE device. Check the master/slave/only settings for the IDE device. In addition to the hard drive, remove all other IDE devices, run the system diagnostics tools provided by the computer manufacturer, especially the memory check, check the Microsoft compatible hardware list (HCL), ensure that all hardware and drivers are compatible with Windows 2000, and select Last Known Good Configuration Start the computer.
Stop message: 0x0000001e failure
Explanatory text: kmodeexptionnothandled
Common Cause: Disk failure.
Workaround: Check for adequate disk space, especially for new installations, disable the drivers displayed in the Stop message and all newly installed drivers, and if the video driver you are using is not provided by Microsoft, try switching to a standard VGA driver or by Windows 2000 appropriate drivers supported, ensure that the system has the latest BIOS, and select "Last Known Good Configuration" to start the computer.
Current 1/2 page
12 Next read the full text
