FAQs about classic XP system faults

Classic XP system faults

I. Typical XP fault Case Analysis

There are too many XP faults. To learn the opposite, we should look at what classic faults we usually encounter starting from the installation of XP. How should we solve them?

Installation start and Failure

Fault 1. Unknown hardware error prompted during installation

[Fault description] After Windows XP SP3 is installed, restart the computer and prompt "c0000135 unknown hard error". The Windows Installer cannot continue.

[Fault Analysis] According to the English prompt, the system cannot be properly installed due to an unknown hardware error. Under normal circumstances, we generally consider that a hardware device is incompatible with Windows XP SP3, but in fact, if some hardware drivers or software in the original windows system conflict with SP3, it may also cause the installation program to fail or the blue screen.

[Troubleshooting] format the system disk C and install Windows XP SP2 first. Note that no hardware driver is installed at this time. After SP2 is installed, install the SP3 program to upgrade Windows XP from SP2 to SP3.

Before upgrading SP3, it is best to back up the current system with ghost.

Fault 2. boot. ini file Error

[Fault description] when Windows XP is started upon startup, the pop-up dialog box prompts "invalid boot. ini file" and the system cannot be accessed.

[Fault Analysis] the reason for the invalid boot. ini file is that the boot. ini file is lost or the file format is incorrect. You only need to restore a boot. ini file or re-compile the correct boot. ini file to solve the problem.

[Troubleshooting] First, on another computer with Windows XP installed, click the "Start> Run" command and enter "C:/boot. INI "and press enter to open boot. INI file, boot. the INI file is saved as a file with the same name and copied to boot. the damaged INI file is overwritten on the computer. INI file. If you cannot find another computer with Windows XP installed at one time, open notepad and enter the following content ():

[Boot loader]
Timeout = 3
Default = multi (0) disk (0) RDISK (0) Partition (1)/Windows
[Operating systems]
Multi (0) disk (0) RDISK (0) Partition (1)/Windows = "Microsoft Windows XP Professional"/noexecute = optin/fastdetect

After the input is complete, save the file as "boot. ini" () and save it to drive C, overwrite the original boot. ini file, and then restart the computer.

If you cannot enter the system, you can use Windows PE to start and modify the boot. ini file of drive C in Windows PE. Or use the boot disk to start the DoS or fault recovery console and enter "Copy con C:/boot. INI "press enter and press boot above. enter the content and format of the INI file line by line. Enter a line and press enter once. After all input is complete, press the shortcut key Ctrl + Z. Then, the prompt ^ Z appears, and press enter again, the prompt "1 file (s) copied", boot. after the INI file is successfully created, the system automatically enters normally after it is restarted.

If the system prompts that the Hal. dll file cannot be found at startup and cannot enter the desktop and security mode, this fault is mainly caused by an error in the boot. ini file. Follow these steps to overwrite the problematic boot. ini file or re-compile the boot. ini file.

Fault 3. The system logon user password is missing

[Fault phenomenon] Some people often change the logon password of Windows XP yesterday when using their computers. Today they forget the password and lock themselves out of the door ".

[Troubleshooting] restart the computer and press F8 to bring up the Advanced startup options menu. Select "safe mode with command line" and click "Administrator" to enter the command line mode. Enter the "Net user system logon username 123456/Add" command to force the system logon username to "123456 ". Alternatively, run the "Net user AAAA 123456/Add" command to create a user named AAAA (password: 123456), and then run the "net localgroup administrators abcdef/Add" command to promote the user named AAAA as the system administrator. After restarting the computer, you can use the changed password "123456" to log on to the system.

You can only change the password. If the hard disk is encrypted with EFS, the EFS encryption will be damaged, resulting in data loss.

Fault 4. Windows XP restarts when it enters the system

[Fault description] Windows XP restarts half of its startup because the kernel32.dll file is lost or damaged.

[Fault Analysis] in such cases, you only need to replace or restore the normal files to solve the problem.

[Troubleshooting] Put the Windows XP installation CD into the CD, start the fault recovery console, enter CD system32 in the command prompt, and press ENTER; then enter Ren kernel32.dll kernel32.old and press ENTER; enter map and press Enter. Finally, enter expand X: i386/kernel32.dl _ and press enter ("X:" is the drive letter ), decompress the kernel32.dl _ file from the disc to the hard disk to replace the damaged kernel32.dll file. Enter "Exit" and press enter to restart the computer to start Windows XP.

Fault 5. The Registry is damaged and the system cannot start properly.

[Fault phenomenon] Windows XP cannot be started properly due to various reasons, resulting in damage to the Windows XP registry. [Fault Analysis] registry damage is very common. Start the fault recovery console, run the DELETE command to delete the original registry file, and copy the Registry file from the Windows XP installation CD/Windows/Repair Directory to the system32/config folder. After this process is completed, a new registry will be created, and Windows XP will start using this new registry. The disadvantage is that the new registry is created and saved during the initial installation of Windows XP. Therefore, any changes and settings made after the installation of Windows XP will be lost.

[Troubleshooting] Go to the fault recovery console, put the Windows XP installation CD into the optical drive (x :), type the following commands, and press enter after each line:

Delete C:/Windows/system32/config/System
Delete C:/Windows/system32/config/software
Delete C:/Windows/system32/config/SAM
Delete C:/Windows/system32/config/security
Delete C:/Windows/system32/config/Default
Copy X:/Windows/repair/system C:/Windows/system32/config/System
Copy X:/Windows/repair/software C:/Windows/system32/config/software
Copy X:/Windows/repair/sam c:/Windows/system32/config/SAM
Copy X:/Windows/repair/Security C:/Windows/system32/config/security
Copy X:/Windows/repair/default C:/Windows/system32/config/Default

Fault 6. "Last correct configuration" error

[Fault symptom and Analysis] Some Windows XP faults, such as the blue screen, restart the computer and press F8 to bring up the Advanced Startup option menu, selecting the "Last correct configuration" can solve many problems. However, if the "Last correct configuration" cannot be used, the following error message is displayed: "Windows NT cocould not start because the following file is missing or fail upt: /Windows/system32/config/system/hardware profile/last known good menu ", which is troublesome. This problem is generally caused by damage to the Registry.

[Troubleshooting] Go to the fault recovery console, run the CD command to enter the C:/Windows/repair directory, and run "Copy *. * c:/Windows/system32/config "command to overwrite the damaged registry file when Windows XP is installed. This registry is created and saved during the initial installation of Windows XP. Therefore, any changes and settings made after the installation is complete will be lost.

Fault 7. Windows XP cannot be started in Windows 2000/XP

[Fault description] Windows 2000 to D are installed on Windows XP on drive C. After Windows 2000 is installed, Windows XP cannot be found after Windows 2000 is restarted, Windows XP cannot be entered, and Windows is supported.

[Fault Analysis] Windows XP cannot be started because after Windows 2000 is installed, its windows 2000 boot program loads Windows XP in the original running mode, and Windows XP has been modified during boot, the modification cannot be found during Windows 2000 boot. Windows XP cannot be started.

[Troubleshooting] copy the file modified by Windows XP to the hard disk. Procedure: Start your computer with Windows 2000, and then install ntldr and bootfont in the i386 folder on the Windows XP installation disc. copy the bin and ntdetect.com files to the root directory of the system disk C, and restart Windows XP.

Fault 8. Windows XP cannot be started after Vista is installed

[Fault description] Windows XP is installed on a computer, and Windows Vista is installed to form a dual system. As a result, Windows XP cannot be started.

[Fault Analysis] Windows XP cannot be started because Windows Vista overwrites the Windows XP Startup file in the root directory of the system startup partition after installation. Of course, Windows XP cannot be started.

[Troubleshooting] use the Windows XP installation CD to start the computer. When the screen prompts "welcome to use installer", press the "r" key to start the fault recovery console, enter the "bootcfg/Add" command and press Enter. All operating systems installed on the computer are automatically scanned and displayed. After scanning, enter the "bootcfg/rebuild" command and press Enter, press Y after the prompt is completed. Finally, enter the missing boot menu item after "input loading identifier", enter "fastdetect" after "input OS loading options", and press enter to find the multi-system menu.

Fault 9. when updating the patch, the system prompts "iexplore error"

[Fault description] When the patch is updated using Windows XP Windows Update, Windows XP prompts "i0000e error ".

[Fault Analysis] the Windows Update file wuv3is. dll may fail.

[Troubleshooting] Click Start> Run and enter "regsvr32/u wuv3is. DLL "() uninstall wuv3is. DLL, and then go to the C:/program files/Windows Update directory to delete wuv3is. DLL file. Run the Windows Update operation again. Do not worry. Windows XP will regenerate the wuv3is. dll file, and the error prompt will not pop up again.

Windows blue screen and black screen

Although the computer has brought many benefits to our lives, it often has a bad temper, such as giving us a blue face or a black face, of course, we also have a way to turn its blue face and black face into a Windows XP interface that we are familiar with. The general idea of solving the problem is as follows: First hardware and then software. Check Existing items in the following sequence