Solution to ntoskrnl.exe corruption or loss

When a colleague's computer is started, the following message is displayed: "Windows cannot start % SystemRoot % \ system32 \ ntoskrnl.exe due to file damage or loss, please install the copy of the above files again "(Windows cocould not start because the following file is missing or your upt: \ system32 \ ntoskrnl.exe. please reinstall a copy of the above file .), I found a lot of solutions on the Internet, but the results were useless. Instead, I fixed the fault through a disk scan.

If ntoskrnl.exe is damaged or lost, the system first tries to verify the security mode and the last correct configuration, but both are invalid. And then use win.

In the past, I wanted to extract the entire Windows folder from the previous ghost backup file in the PE system, but that is the same as reinstallation. It is expected that most applications will have to be installed again. Think of system32 missing, it may be a problem with the hard disk, so check whether there is a problem with the hard disk before making the next decision. Right-click drive C-properties-tools-check errors-Start Check-select "manually repair file system errors" (and select "scan and try to recover bad sectors, at that time, I just wanted to assume that there are actually bad sectors to be repaired at this step, so I chose the first option, which also saves some time) and executed the disk scan check program. The producer is also in. Restart the computer and start from the hard disk.

After the repair is completed, the repair ntoskrnl.exe is missing or damaged. Other Methods collected on the network are listed as follows:

0th. The file information related to ntoskrnl.exe is as follows:

Windows Startup logo screen is stored in windows. When you call the ntoskrnl.exe file, pass the hardware information collected by ntdetect.com to it. The Hal. dll file is also called at the same time. If the file is lost or damaged, the logo will be unavailable when Windows XP is started.

1. Method 1:

Decompress the package in "C: \ WINDOWS \ driver cache \ i386": Expand sp2.cab-F: ntoskrnl.exe c: \ windows \ system32 and start to the repair mode with the CD, go to the command line to perform the operation.

2. Method 2:
Cancel the startup screen. Open start-execute in the system, enter msconfig and click OK. Then, the System Configuration useful program is opened. Switch to the boot. ini option page, and select "/noguiboot. ini" in the "Boot options" area. This option allows you to skip this error because the startup screen is not displayed during startup. However, if your system cannot be started, msconfig cannot be used. Then you can start the computer to the command line repair mode through the CD, edit the boot. ini file, and add this option:
[Operating systems]
Multi (0) disk (0) RDISK (0) Partition (2) \ Windows = "Microsoft Windows XP Professional"/noexecute = optin/fastdetect/noguiboot

3. Method 3:

This issue may be related to the boot list corruption or hardware. Some netizens have encountered memory problems, which can be solved by cleaning, re-plugging or replacing the memory.

4. Method 4:

Press F8 before entering the Windows system. A menu list is displayed, select "Last correct configuration", and press Enter.

The above is from a website

5. Method 5: The main reasons for this problem are as follows: boot. in the [boot loader] section of the INI file, the default value is lost or the ntoskrnl.exe file is missing or damaged. the partition path in the INI file is set incorrectly. Solution: Use the Windows XP installation CD to start the computer, press the r key on the screen to enter the fault recovery console, and log on to the system using the administrator account. Enter the "bootcfg/rebuild" command at the prompt and press Enter. When the screen asks "add installation to the startup list ?" Press the "y" Key, enter "Windows XP" when "input loading identifier" appears, and press enter directly when asking "input OS loading option. After that, restart the computer to normal mode. This will fix the boot. ini file. If the file is damaged or lost, it can be repaired in the fault recovery console.

6. Method 6: Start with a Windows CD, and enter expand (drive letter) in the fault recovery console: \ i386 \ ntoskrnl. ex _ c: \ windows \ system32 \ ntoskrnl. exe

7. Method 7: Data Transmission Error. If the initial file is not read, change the hard disk data cable.

From: http://www.cnblogs.com/chinhr/archive/2009/01/27/1309525.html

8. Method 8:

In addition to ntoskrnl.exe, another file ntkrnlpa.exemust be overwritten, And the uncompressed token must be the same as ntoskrnl.exe (see the preceding figure and do not repeat it)

From: http://www.blogjava.net/linhuaimin/archive/2008/11/02/164857.html

Note: When modifying the Beibei ntoskrnl.exefix, the same version number must be used as the ntoskrnl.exe of the original system.