Troubleshoot Windows failure to start prompt hal.dll for damage or loss

1, Ghost system caused by the original package ghost system files and brand host partition type is not caused together (most of the brand computer has hidden partitions);

2, accidental system shutdown after the normal, boot can not start, using the system repair Disk repair Tips System32//hal.dll This file is damaged or missing;

3, overclocking may also cause system file damage, suggesting system32//hal.dll damaged or lost;

4, is the memory of the fault, the memory strip down to wipe the dirt on the gold finger, check whether to plug and try again, or find a good memory to ensure the installation of the first Test, to remove the problem is not the memory bar!

Here's how to tell you the usual solution to hal.dll damage or loss

1, unable to start the hint Hal.dll damaged or lost, in fact, the file may not necessarily say in the system does not exist, and according to the system prompts the request, copy a Hal.dll file into the System32, it is not possible to solve.

2, the reason for this error is Boot.ini file error, leading to the computer can not boot from the specified path, so the system will search for other paths, and other paths do not exist or there is no Hal.dll file, so you will be prompted this error.

3, for example, the system is installed to a disk C, if the C-packing directory of Boot.ini file format is not complete illegal, the system defaults to start from the c:windows, but also because Boot.ini file format is not complete illegal, the system will determine that your Windows XP is not installed in the C disk, Therefore, the system prompts that the HAL.DLL file cannot be found. Causes the startup to fail. The workaround is to edit the Boot.ini file again.

4, use the DOS boot disk to start, into the DOS interface, using the DOS tool EDIT.EXE command to edit this file. After starting the EDIT.EXE, open the Boot.ini, edit the contents of the Boot.ini file in the correct format, and save it as a Boot.ini file.

5. Use the bootcfg command inside the Recovery Console. Using the Windows Recovery Console, repair the boot.ini with the Fixboot command, and Bootcfg/add to rebuild the boot.ini if it fails.

6, if the DOS command interface is not cold, can also be in other computers to create a good boot.ini, and then copy to the failure of the computer's C-packing directory to cover the source file.

7, how to copy it? still use DOS. You can not take down the hard drive of the faulty computer, hang on another computer to copy it, the best way is to edit the boot.ini from other computers, with a U disk boot.ini copy, and then copy a Hal.dll file.

8, then plug in the fault computer, using the boot disk and load USB drive support, into the DOS interface. Access to the U disk directory see Hal.dll and Boot.ini file it, and then use the DOS command

Copy Hal.dll C:/windows/system32/hal.dll

Copy Boot.ini c:/