Suddenly one day, your Windows 2000 cannot start normally, or black screen, or constantly restart, or display a blue screen and a lot of error prompts, what should I do? Let's listen to the experience of the experience of experts from the experience of experts. Is there any change? This is the first question to ask customers or your own problems, such as: Whether to install new drivers, system patches, or new hardware, usually I will get some very useful information, because the above operations often cause the system that cannot start the system . Through the phenomenon, the inherent WINDOWS 2000 cannot be activated. Different performances 1. Black screen: It is usually due to damage or incorrect display drivers (or set the error display resolution). 2. Continuous restart: usually means that the PCI interface card is loose, open the chassis to remove the PCI interface card and then insert. If there is still a problem, then it may be that the PCI interface card is loose, resulting in a mess, it is confusing, so you have to enter the security mode, then open the "Device Manager", remove all the information related to the PCI interface card, After restart, let the system re-detect and install. If you have two anti-virus software in the system, it is likely that the computer is automatically restarted after logging in. It is best to enter the security mode to uninstall it, then enter the device manager. ", Select" View → Show Hidden Device ", click Expand" Unsettled Driver "in the list, will see if there is a driver that has been unloaded anti-virus software, if there is, right click to unload it . 3. Blue screen: Mainly wrong drivers or hardware conflicts, fortunately, there will be some error messages in the blue screen, you can find information related to this information (such as: http: //support.microsoft. COM /) in order to solve the problem. 4. Lock during the startup: The most difficult thing to solve is to lock when the system starts, this is generally related to the system file, such as: a DLL file is accidentally replaced with an incorrect version, this problem, you You should use the System File Checker to fix an error. I will explain it in detail below.
Several roads to solve problems
1. The last correct configuration
Restart the system, pressing the F8 key when the startup menu appears, the advanced option menu will appear. Here "The last correct configuration" should be you first try.
It is to be noted that "the last correct configuration" is a way to recover from the problem (such as the newly added driver and hardware. But it cannot solve problems caused by drivers or files being corrupted or lost.
Because when "the last correct configuration" is selected, Windows 2000 restores information on the registry key [hklm\system\currentControlSet]. Any changes made in other registry keys remain unchanged.
2. Safety mode
Safety mode is our good friend, in which only the most basic hardware drivers and services are loaded.
If Windows 2000 can enter safe mode, you can breathe, because the problem is not so serious. If the system can enter secure mode, it is often caused by damaged device drivers or hardware conflicts due to corrupted devices.
(1) First, you can enter the Start → Settings → Control Panel → Administration Tools → Event Viewer, and see if there is available information in the System Log.
(2) Click "Start → Run", enter: msinfo32, turn on the System Information window after entering the bus, first click on "Components" in the console tree, then select "Problemful device", then view the right side The device listed in the pane; then click "Hardware Resources" in the console tree, then click Conflict / Sharing, and write down the resource conflicts listed on the right pane. (3) Enter "Device Manager", deactivate those suspicious devices, then restart, if this can enter the normal mode, then a device that has been deactivated in security mode is enabled, and restarted, repeat the above operation until Discover problems with problems. If the problem is not caused by the hardware device after the above efforts, you can enter the "command prompt" window, enter: SFC / ScanNow, scan and recover important system files.
3. Fault Recovery Console
If you didn't load the fault recovery console to load the system, use the Windows 2000 installation of the CD boot system, and press the R key to enter the repair option when "Welcome to the Installer" screen, then press the C button to start the failure recovery Console.
Load the fault recovery console to load the system
Put the Windows 2000 installation CD, press the WIN R key button, type: d: \i386@winnt32.exe / cmdcons (D is the driven drive number).
(1) Scanning and correction disks
Use the Chkdsk / F / R command to check and fix most disk errors, where / r can repair problems that cannot be started due to disk errors. For example, unmountable_boot_volume error messages in the blue screen, and even security mode. The advanced start menu may appear after repairing and restarting, select "Normal start".
If it is repaired, even if everything is operated in normal way, this phenomenon still occurs, it is recommended to back up important data on the hard disk as soon as possible, which may be a precursor to the hard disk damage.
In addition, it is also recommended to check if the hard disk cable is poor contact, or no connection line with the hard disk transfer specification, such as the ATA-100 hard drive still uses the ATA-33 cable, which does not matter, but high-speed hard drive (support ATA -66 or more requirements are stricter, and the cables that are not correct may sometimes cause this type of failure to boot.
(2) You can try the command
You can also try the fixmbr command to modify the main boot partition record, and FixBoot is used to fix the disk boot sector.
Sometimes the virtual memory file (PageFile.sys) can also cause an error, it is recommended to delete it, but you can't delete the file directly, you need to do your way:
CD \
Copy C: \Boot.ini Pagefile.sys (over) Existing PageFile.sys files with Boot.ini)
Del PageFile.sys (After boot.ini override pagefile.sys, PageFile.sys will be displayed in the directory list)
(3) Saving damaged documents
Windows 2000 cannot start, where driver file is corrupted, the important system file is relatively common, first restart the system, press the F8 key to enter the Advanced Options menu when the startup menu, select Enable Start Log, so the system will automatically be in C: \ Generate ntbtlog.txt files in the winnt directory, then enter the fault recovery console, enter: type ntbtlog.txt, this will display the contents of the file, pay attention to the last statement, if the statement contains "fail" characters, then The next file name is recorded and then recovered. In addition, sometimes the system will also prompt or damage some files at startup. Example 1: Tip C: \winnt \system32 \ in the kbdal.dll file is lost, find the same name file in the CD, then Copy G: \i386\kbdal.dll C: \winnt \System32 \ can recover lost or damaged Kbdal.dll file. (G is a light drive letter)
Example 2: Some files may be copy commands that cannot be copied, or a series of driver lost causes the system to start normally, and the expand command can be used to extract missing files.
For example: system prompts missing MSR2c.dll files in C: \winnt \System32 \, locating the MSR2C file in the i386 directory of the disc installation CD and then expand g: \i386\msr2c c: \winnt \ system32 \ msr2c.dll.
For example,: System Tips C: \winnt \System32\Driver \ TDI.sys file is lost, because the driver file is usually in the i386\driver compression package, so use: expand g: \i386\driver.cab \f: TDI. SYS C: \winnt\system\drivers.
(4) Close the wrong service or device
After a hardware or software is installed, they are not compatible with the current Windows installed, causing the current Windows, resulting in shutting down.
Enter C: \winnt\system32 directory, enter: Listsvc, will list the service or devices installed by the current system after entering the bus, find and note the service or device name related to the new hardware or software, then enter: disable service or Equipment name, will be deactivated.
(5) NTLDR lost
When startup, the following error message appears:
NTLDR IS MISSING
Press Any Key to Restart
The solution is: enter the fault recovery console, enter: Copy G: \i386\ntldr C: \ (Enter), Copy G: \i386\ntdetect.com C: \ (Enter) If the system prompts if the file is overwritten Type Y, then press Enter.
Then type C: \Boot.ini, if the content in Boot.ini is displayed normally, the problem should be able to resolve. If you are displayed as "The specified file or directory is not found.", Then the boot.ini file is damaged or lost, you can copy the file in other installation of Windows 2000, copy it to C: Under, then restart I.e. (6) Save your crane with system.Alt
One day system prompts the illegal operation and restarting, the system prompts to scan the disk, pressing any key to cancel this operation, and there is no different after entering Windows 2000. However, when it is restarted again, there is no error prompt, but it is only stopped before the startup screen, when choosing to enter the security mode, the screen display system stops running after loading several important files, take a closer look It turns out that the system file under the C: \winnt \System32\config folder (no extension) error causes the system to be loaded.
Enter the fault recovery console, then enter the C: \winnt \System32 \ Config folder, use the rename command to name System.old, then use the rename command to use the system.alt file (which is actually a registry file A copy) is renamed to System and successfully enters the system after reboot.
