Win7 can not start prompting Hal.dll corruption or loss solution

When we use Win7 system, the computer can not boot, prompting "Windows root"\\system32\\hal.dll is damaged or missing, causing Windows to fail to start. There is such a problem, how do we solve it? Let's take a look at the Win7 system can't start the solution that the Hal.dll is damaged or lost.
First, the Windows fails to start prompting hal.dll is damaged or The reasons for the loss are:
1, GHOST system caused, GHOST original package system file and brand host partition type are not caused together (most of the brand computers have hidden partitions);
2, accidental system after abnormal shutdown , boot can not start, use the system repair disk repair prompt system32\\\\hal.dll this file is damaged or lost;
3, overclocking may also cause system file corruption, suggesting system32\\\\hal.dll is damaged or lost; > 4, is the memory failure, pull out the memory strip to wipe off the dirt on the gold finger, check if it is tight and try again, or find a true Normal memory module installation test first, to eliminate the problem is not the memory stick!
Second, the solution is as follows:
1, can not start prompting Hal.dll damaged or lost, in fact, the file may not some say does not exist in the system, and follow the system prompts request a copy a file to the System32 Hal.dll years, simply can not be solved.

2, this error occurs is the key reason Boot.ini The file is wrong, which prevents the computer from booting from the specified path, so the system will search for other paths, and the other paths do not exist or there is no Hal.dll file at all, 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 starts from C:\\Windows by default, but because the Boot.ini file format is incomplete, the system will determine you. WinXP is not installed on the C drive, so the system prompts that the Hal.dll file cannot be found. The startup fails. The solution is to re-edit the Boot.ini file.
4. Start using the DOS boot disk and enter the DOS interface. Use DOS tool EDIT.EXE command to edit the file. After the start EDIT.EXE, open Boot.ini, in the right format to edit the contents of the Boot.ini file, and then save it as a file to Boot.ini.