Win7 system can not start the solution that prompts Hal.dll to be damaged or lost

When we were using the Win7 system, the computer could not be booted. The prompt "Windows root"\\system32\\hal.dll was damaged or lost, and Windows could not be started. Then there is such a problem, how can we solve it? Let's take a look at the solution that Win7 system can't start to prompt the damage or loss of Hal.dll with Xiaobian.

First, the Windows can not start prompt hal.dll damaged or lost reasons:

1, GHOST system caused, GHOST original package system file and brand host partition type is not caused together ( Most of the brand computers have hidden partitions;

2, after the accidental system is abnormally shut down, the boot can not be started, use the system repair disk repair prompt system32\\\\hal.dll this file is damaged or lost; >

3, overclocking may also cause system file corruption, indicating system32\\\\hal.dll is damaged or lost;

4, is a memory failure, pull the memory strip to wipe off the dirt on the gold finger Check if you plug it in and try again, or find a way to ensure that the normal memory module is installed before testing, to eliminate the problem of the memory stick!

Second, the solution is as follows:

1, can not start the prompt Hal.dll is damaged or lost, in fact, the file may not necessarily say that it does not exist in the system, and according to the system prompts Copying a Hal.dll file to System32 is simply not solvable.

2, the reason for this error is the Boot.ini file error, which can not boot the computer 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 this error will be prompted.

3, for example, the system is installed to the C drive, if the Boot.ini file format in the root directory of the C drive is incomplete, the system defaults from C:\\Windows, but because of Boot. The ini file format is incomplete and illegal. The system will determine that your WinXP is not installed on the C drive, so the system prompts that the Hal.dll file cannot be found. Causes the startup to fail. The solution is to re-edit the Boot.ini file.

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

5. Use the bootcfg command in the Recovery Console. Use the Windows Recovery Console to fix Boot.ini with the fixboot command. If it fails, use bootcfg /add to rebuild Boot.ini.

6, if you do not catch a DOS command interface, you can also create a correct Boot.ini on other computers, and then copy the source file to the root directory of the faulty computer C drive.

7. How is COPY? Still use DOS. You can't remove the hard drive of the faulty computer. COPY when hanging on another computer. The best way is to edit the Boot.ini from another computer, copy it with a USB flash drive, and copy one. Hal.dll file.

8, then plugged into the faulty computer, use the boot disk and load the U disk drive support, enter the DOS interface. Go to the U disk directory and see the Hal.dll and Boot.ini files, then use the DOS command

copy hal.dll c:\\windows\\system32\\hal.dll

copy boot. Ini c:\\

The above is also the Win7 system can not start the solution to the damage or loss of Hal.dll. If you have any problems with this type of problem, you may wish to try the above methods. After the above steps, you can basically solve the startup failure and prompt the damage or loss of Hal.dll!