[Computer troubleshooting] Windows 2000 cannot start

When Windows 2000 cannot be started

Suddenly one day, your Windows 2000 cannot be started normally, or a black screen, or constantly restarted, or displayed a blue screen with a bunch of error prompts, what should you do?
Is there any change? = All Rights Reserved. Download from school All Rights Reserved. This is the first question to ask customers or themselves, for example, whether a new driver or system patch is installed.
Or new hardware, I usually get some very useful information, because the above operations are often the culprit that causes the system to fail to start.

Essence through Phenomena

Windows 2000 does not support startup.

1. Black screen: it is usually caused by damage or incorrect display driver (or incorrect display resolution is set ). 2. Constant restart: it usually means that the PCI interface card is loose. Open the chassis and unplug the PCI interface card and plug it in again.
If there is still a problem, it may be that after the PCI interface card is loose, the system plug-and-play information is messy, so you need to enter the safe mode and then open the "Device Manager ", delete all information related to the PCI interface card.
Re-check and install the system.

Disaster caused by anti-virus software

If you have installed two anti-virus software in the system, it is likely that the computer will automatically restart after logon. It is best to uninstall one of them in safe mode, then go to "Device Manager" and select "View> display ".
"Show Hidden devices". In the list, click expand "non-plug-and-play drivers" to check whether any anti-virus software driver has been uninstalled. If any, right-click to unmount it.

3. blue Screen: This is mainly caused by incorrect drivers or hardware conflicts. Fortunately, the blue screen provides some error information. You can search for information related to this information on the Internet (for example: http://support.microsoft.com /),
To solve the problem.

4. locking during startup: the most difficult solution is locking the system at startup, which is generally related to system files. For example, a DLL file is accidentally replaced with an incorrect version, in this case, you should use the "System
"To correct the error. I will explain it in detail below.

Several ways to solve the problem

1. The last correct configuration

Restart the system. When the boot menu appears, press the F8 key to display the advanced option menu. Here, "the last correct configuration" should be the first attempt.

Note that selecting "Last correct configuration" is a way to recover from a problem (such as a new driver that does not match the hardware. But it cannot solve the problem caused by the driver or file being damaged or lost.

When "Last correct configuration" is selected, Windows 2000 only restores information in the registry entry [HKLM \ System \ CurrentControlSet. Any changes made in other registry entries remain unchanged.

2. Security Mode

Security mode is a good friend of ours. In this mode, only the most basic hardware drivers and services are loaded.

If Windows 2000 can enter safe mode, but cannot enter normal mode, it is often caused by a corrupt device driver or hardware conflict.

(1) first, you can go to "start → settings → Control Panel → management tools → Event Viewer" to check whether there is available information in "system logs.

(2) Click Start> Run. Enter msinfo32. Press enter to open the system information window. In the console tree, click expand component ", select "problematic devices" and view the settings listed in the right pane.
In the console tree, click expand hardware resources, and then click conflict/share to write down the resource conflicts listed in the right pane.

(3) log on to the Device Manager, stop the suspicious devices, and restart the device. If the device enters normal mode, enable a device that has just been disabled in safe mode, restart and repeat the preceding operations until you find any
The faulty device. If the problem is not caused by hardware devices after the above efforts, you can enter the "command prompt" window and enter: sfc/scannow to scan and recover important system files.

3. Fault Recovery Console

If you have not mounted the fault recovery console to the system before, use the Windows 2000 installation CD to start the system, and press the R key to go to the repair option when the "Welcome installer" Screen appears, then press the C key to start
Fault recovery console.

Mount the fault recovery console to the System

On the Windows 2000 installation disc, press Win + R and enter D: \ i386 \ winnt32.exe/cdcons (D is the drive letter of the optical drive ).

(1) scan and modify Disks

Run the chkdsk/f/r command to check and correct most disk errors. The/r can fix the issue that cannot be started due to disk error export. For example, the UNMOUNTABLE_BOOT_VOLUME error message appears on the blue screen.
This is also true for full mode. After restoration and restart, the Advanced Startup Menu may appear. Select "normal startup.

If the repair, even if all follow the normal operation, UNMOUN-TABLE_BOOT_VOLUME this phenomenon still often appears, it is recommended to back up important data on the hard disk as soon as possible, this may be a precursor to hard disk damage.

In addition, it is recommended to check the hard drive connection line is not good contact, or do not use the connection line that meets the hard drive transmission specifications, such as ATA-100 hard drive still use ATA-33 connection line, does not matter to the low speed hard drive, however, high-speed hard disks (Supporting
Hold ATA-66 above) more stringent requirements, wrong specifications of the connection line sometimes will cause this kind of failure can not boot.

(2) commands that can be tried

You can also try the fixmbr command to modify the primary boot partition record, and fixboot is used to fix the disk Boot Sector.

Sometimes the virtual memory file (pagefile. sys) is damaged and may cause an error. We recommend that you delete it. However, you cannot directly delete the file. You need to perform the following operations:

Cd \ copy c: \ boot. ini pagefile. sys (using Boot. ini overwrites the existing Pagefile. sys File) del pagefile. sys (using Boot. ini overwrites Pagefile. after sys, Pagefile. sys will be displayed in the Directory List)

(3) saving damaged files

Windows 2000 cannot be started. driver files are damaged and important system files are lost. First, restart the system and press F8 to enter the advanced options menu, select enable startup log.
The system automatically generates the ntbtlog.txt file under the C: \ winntdirectory, and then enters the fault recovery console. Enter: type ntbtlog.txt, which will display the content of the file. Pay attention to the last statement, if the statement contains "Fail"
Then, record the subsequent file names and restore them. In addition, sometimes the system prompts that some files are lost or damaged at startup.

Instance 1: KBDAL in C: \ WINNT \ system32 \ is displayed. the DLL file is lost. Find the file with the same name in the CD and copy g: \ I386 \ KBDAL. dll c: \ WINNT \ system32 \ To recover loss or loss
Bad KBDAL. DLL file. (G is the drive letter)
Instance 2: some files may not be copied by the COPY command, or the system may fail to start properly due to the loss of a series of drivers. In this case, the expand command can be used to extract the missing files.

For example, the system prompts that msr2c in C: \ WINNT \ system32 \ is missing. dll file loss. Locate the msr2c file in the i386 directory of the installation disc and then expand G: \ i386 \ msr2c C: \ WINNT \ system32 \ msr
2c. dll.

For example, the system prompts C: \ WINNT \ system32 \ driver \ middle tdi. sys File is lost, because the driver file is generally in the i386 \ driver compressed package, so use: expand G: \ i386 \ driver. cab \ f: tdi. sys
C: \ WINNT \ system \ drivers.

(4) disable the wrong service or device

After a hardware or software is installed, the devices or services installed on the system are incompatible with the current Windows system, resulting in startup failure.

Enter the C: \ WINNT \ system32 directory, enter: listsvc, and press enter to list the services or devices installed in the current system, find and write down the service or device name related to the newly installed hardware or software, and then enter: disable Server
Service or device name. Press enter to stop the device.

(5) NTLDR loss

The following error message is displayed at startup:

NTLDR is missing

Press any key to restart

Solution: Go to the fault recovery console, enter copy G: \ i386 \ ntldr c: \ (Press ENTER), copy G: \ i386 \ ntdetect.com c: \ (Press ENTER ), if the system prompts whether to overwrite the file, type y,
Then press Enter.

Type c: \ Boot. ini. If the content in Boot. ini is displayed normally, restart the system. The problem can be solved. If "the system cannot find the specified file or directory .", This means that the Boot. ini file is damaged.
If the file is damaged or lost, you can copy it to another computer that has installed Windows 2000, copy it to C:, and then restart it.

(6) Saving the computer with SYSTEM. ALT

One day, the system prompts that the operation is illegal and crashes and then restarts. The system prompts to scan the disk. Press any key to cancel the operation. After Entering Windows 2000, there is no exception. However, the system cannot be accessed after the restart, and there is no error.
The error message is that the system does not stop until the startup screen appears. When you choose to enter safe mode, the screen shows that the system stops running after loading several important files: \ WINNT \ system32 \ config file
The SYSTEM file under the folder (without the extension) fails to be loaded.

Log on to the recovery console, go to the C: \ WINNT \ system32 \ config folder, rename the SYSTEM file to SYSTEM. OLD, and rename the SYSTEM. ALT file (
It is actually a copy of the registry file.) It is renamed as SYSTEM, and the SYSTEM is successfully restarted.