{"id":914,"date":"2013-08-28T00:51:27","date_gmt":"2013-08-28T05:51:27","guid":{"rendered":"http:\/\/neosmart.net\/kb\/?p=914"},"modified":"2016-05-17T19:02:05","modified_gmt":"2016-05-18T00:02:05","slug":"ntoskrnl-exe-missing-corrupt","status":"publish","type":"post","link":"https:\/\/neosmart.net\/wiki\/ntoskrnl-exe-missing-corrupt\/","title":{"rendered":"NTOSKRNL.EXE is missing or corrupt: Fix for Windows XP"},"content":{"rendered":"

Get the fix for the boot error “NTOSKRNL.EXE is missing or corrupt<\/strong>” for Windows XP<\/strong>.<\/p>\n

About “ntoskrnl.exe is missing or corrupt”<\/h2>\n

The following information on this error has been compiled by NeoSmart Technologies, based on the information gathered and reported by our global network of engineers, developers, and technicians or partner organizations.<\/p>\n

Description and Symptoms<\/h3>\n

The error messages, alerts, warnings, and symptoms below are tied to this error.<\/p>\n

Symptom 1: ntoskrnl.exe is missing or corrupt error screen on startup<\/h4>\n

The ntoskrnl.exe (short for Windows NT operating system kernel) is responsible for various system services such as hardware virtualization, process and memory management. Right after NTLDR and NTDETECT boot files are done with the basic loading subroutines and hardware detection, the control over the boot process is passed to ntoskrnl.exe so that the operating system could start loading. However, if ntoskrnl.exe is missing or corrupt, then the following error appears and the boot process is halted.<\/p>\n

\"Ntoskrnl.exe<\/p>\n

Windows could not start because the following file is missing or corrupt:\r\n<Windows root>\\system32\\ntoskrnl.exe.\r\nPlease re-install a copy of the above file.<\/pre>\n
For more information on how computers start up<\/a> and how the Windows XP boot process works<\/a>, please refer to the respective pages in our extensive wiki and knowledgebase.<\/p>\n
Causes of this Error<\/h3>\n
This error has been known to occur as a result of one or more of the following:<\/p>\n
Cause 1: Invalid boot.ini configuration<\/h4>\n
An incorrectly configured boot.ini file may result in the Windows XP bootloader attempting to load Windows from the wrong drive or partition.<\/p>\n
If NTLDR attempts to load Windows from the wrong partition, it will not find ntoskrnl.exe and this error may be occur.<\/p>\n
Boot.ini may become misconfigured as a result of incorrectly installed software, a failed Windows update, virus infection, or an incomplete Windows upgrade.<\/p>\n
Cause 2: Corrupt boot volume<\/h4>\n
Corruption of the boot partition on a Windows XP PC can cause this error to be present.<\/p>\n
The boot drive can become corrupted as a result of an unsafe shutdown, sudden power loss, unsafe removal of a local or external disk, or physical disk damage and\/or corruption.<\/p>\n
A corrupted boot partition may occur on both NTFS and FAT32 filesystems and volumes.<\/p>\n
Cause 3: Corrupted or deleted ntoskrnl.exe<\/h4>\n
As the error screen states, this error is sometimes caused by a lost or corrupted ntoskrnl.exe file on the Windows system partition. The system partition may or may not be the same as the boot partition (see above).<\/p>\n
\\Windows\\system32\\ntoskrnl.exe<\/code> may be deleted or corrupted as a result of unsafe shutdown, NTFS or FAT32 volume corruption, failed Windows updates, or virus infection.<\/p>\n
Cause 4: PS\/2 keyboard incorrect behaviour<\/h4>\n
Keyboard-related software issues are largely no longer a concern with newer USB\/internal keyboards. However, older PCs that use a keyboard attached to the PC via a serial interface, could misinterpret the device’s mapped memory as a storage volume, leading to boot problems like this one.<\/p>\n
Cause 5: Missing drivers for hard disk controller<\/h4>\n
If Windows does not have the necessary drivers to access the Windows system files on the main partition, this error message can be seen. This can happen as a result of a failed driver update, changes to the hardware configuration, or changes to the hard disk configuration in the BIOS.<\/p>\n
Fix NTOSKRNL.exe is missing or corrupt in Windows<\/h2>\n
Fix #1: Use Easy Recovery Essentials<\/h3>\n
Easy Recovery Essentials is guaranteed to fix the “NTOSKRNL.EXE is missing or corrupt” error automatically using its built-in Automated Repair option. EasyRE is currently available for Windows XP<\/strong>, Vista<\/strong>, 7<\/strong>, 8<\/strong>, Windows 10<\/strong>, and Windows 11<\/strong> and can be downloaded and created on any PC.<\/p>\n
    \n
  1. Download Easy Recovery Essentials<\/a>. Make sure to note your Windows version (XP, Vista, 7, 8, 10, or Windows 11) before you download EasyRE. This guide can help you identify what version of Windows<\/a> you have installed.<\/li>\n
  2. Burn the image. Follow these instructions on how to burn the bootable ISO image<\/a>\u00a0very carefully, as making a bootable CD can be tricky! Alternatively, these instructions explain how to create a bootable EasyRE recovery USB stick\/drive<\/a>.<\/li>\n
  3. Boot up your PC from the Easy Recovery Essentials CD<\/a> or USB you created.<\/li>\n
  4. Once EasyRE is running, choose the “Automated Repair” option and click Continue<\/kbd>.\n
    \"EasyRE<\/a><\/p>\n
    Choose “Automated Repair” in Easy Recovery Essentials<\/p>\n<\/div>\n<\/li>\n
  5. After EasyRE scans your computer’s drives, identify and select the drive letter for your Windows installation\u00a0from the list, and then click on the Automated Repair<\/kbd> button to begin.\n
  6. Easy Recovery Essentials will start analyzing the selected drive for problems. EasyRE will test for and attempt to automatically correct errors with the disk, partition, bootsector, filesystem, bootloader, and registry. No intervention is required, as EasyRE’s repair is fully automated:\n
    \"EasyRE:<\/a><\/p>\n
    Easy Recovery Essentials searches for errors and makes corrections to the selected Windows installation.<\/p>\n<\/div>\n<\/li>\n
  7. Once the process is complete, EasyRE will report its findings. Click on the Restart<\/kbd> button to reboot your PC and test the changes.<\/li>\n
  8. The “NTOSKRNL.EXE is missing or corrupt” error should now be fixed as your PC begins to load:\"EasyRE:<\/a><\/li>\n<\/ol>\n
    You can download Easy Recovery Essentials from here<\/a>.<\/p>\n
    Fix #2: Replace or recreate a corrupted\/incorrect boot.ini<\/h3>\n
    A boot.ini file\u00a0is used by Windows<\/a>\u00a0to configure and display its operating system options. Instructions on\u00a0manually recreating the boot.ini file<\/a>\u00a0are also available, but require a moderate level of computer expertise. The instructions below will guide you on recreating boot.ini automatically from the Windows XP setup CD.<\/p>\n
    Unable to boot into the Windows setup CD?<\/strong>
    See our guide on     setting up a PC to boot from the CD or DVD<\/a> for troubleshooting and more detailed instructions.<\/p>\n
      \n
    1. Insert your Windows XP CD and restart your computer.<\/li>\n
    2. Press a key to boot into the CD when you see the “Press any key to boot from CD” message.<\/li>\n
    3. When you arrive at the “Welcome to Setup” message, press\u00a0R<\/kbd>\u00a0to start the Recovery Console.<\/strong><\/li>\n
    4. Type in your Administrator password; hit\u00a0Enter<\/kbd><\/li>\n
    5. The next command you need to write is below; hit\u00a0Enter<\/kbd>\u00a0afterwards:\n
      bootcfg \/rebuild<\/pre>\n<\/li>\n<\/ol>\n
      The above command,\u00a0bootcfg \/rebuild<\/code>, will scan your computer for installed Windows copies. If you have Windows XP, here are the next steps:<\/p>\n
        \n
      1. Press\u00a0Y<\/kbd>\u00a0if the command prompt shows a message similar to the one below:\n
        Total Identified Windows Installs: 1\r\n\r\n[1] C:\\Windows\r\nAdd installation to boot list? (Yes\/No\/All)<\/pre>\n<\/li>\n
      2. When you receive a message like this:\n
        Enter Load Identifier<\/pre>\n
        You are being asked to provide a name to be assigned and shown in the boot menu for the installation you picked in the previous step. Examples:<\/p>\n
        Enter Load Identifier: Windows XP Professional (Recovered)<\/pre>\n<\/li>\n
      3. (Optional) When you receive a message like this:\n
        Enter OS Load options<\/pre>\n
        Type in\u00a0\/fastdetect<\/code>\u00a0followed by\u00a0Enter<\/kbd><\/li>\n
      4. Restart your computer.<\/li>\n<\/ol>\n
        Here is an example of what the PC’s console output should look like once the boot.ini file is restored:<\/p>\n
        \"Restoring<\/a><\/p>\n
        Restoring Boot.ini file<\/p>\n<\/div>\n
        Fix #3: Boot into Last Known Good Configuration<\/h3>\n
        Windows Setup CD\/DVD Required!<\/strong>
        Some of the solutions below require the use of the Microsoft Windows setup CD or DVD. If your PC did not come with a Windows installation disc or if you no longer have your Windows setup media, you can use         Easy Recovery Essentials for Windows<\/a> instead. EasyRE will automatically find and fix many problems, and can also be used to solve this problem with the directions below.<\/p>\n
        Rebooting your PC into “Last Known Good Configuration” mode forces your computer to use a saved version of the Windows registry that was in place the last time your computer successfully booted. If this error is being caused as a result of incorrect, misconfigured, or uninstalled drivers, booting your PC in “last known good configuration” mode may resolve the problem. This option is available from the Advanced Boot Options menu<\/a> at system start.<\/p>\n
        Here are the steps to start your PC up using the Last Known Good Configuration option. More detailed instructions on\u00a0starting up your PC using the last known good configuration<\/a>\u00a0are also available.<\/p>\n
          \n
        1. Restart your computer<\/li>\n
        2. Wait for your BIOS to complete POST (the screen with your manufacturer logo and\/or system information)<\/li>\n
        3. Quickly<\/em>\u00a0begin tapping\u00a0F8<\/kbd>\u00a0repeatedly, until you see the list of boot options<\/li>\n
        4. Choose “Last Known Good Configuration (Advanced)”<\/li>\n
        5. Press\u00a0Enter<\/kbd>\u00a0and wait for your PC to boot.<\/li>\n<\/ol>\n
          Fix #4: Disconnect PS\/2 or serial keyboard<\/h3>\n
          If the fix above doesn’t work and the PC is using an old PS\/2 keyboard, it’s recommended to attempt disconnecting it and then restarting the computer to see if anything changes. Here are the steps to do it:<\/p>\n
            \n
          1. Shutdown the computer<\/li>\n
          2. Disconnect the keyboard<\/li>\n
          3. Power up the computer<\/li>\n<\/ol>\n
            Some users have reported that that the NTOSKRNL.exe error disappears after disconnecting the keyboard and then reconnecting it after a restart.<\/p>\n
            Fix #5: Restore the ntoskrnl.exe file<\/h3>\n
            If ntoskrnl.exe is in fact missing or corrupt, you can restore the original ntoskrnl.exe file back from your Windows XP installation disc.<\/p>\n
            Unable to boot into the Windows setup CD?<\/strong>
            See our guide on             setting up a PC to boot from the CD or DVD<\/a> for troubleshooting and more detailed instructions.<\/p>\n
              \n
            1. Insert your XP CD into the computer.<\/li>\n
            2. Restart your computer.<\/li>\n
            3. Press any key to boot into the CD when you see the “Press any key to boot from CD” message.<\/li>\n
            4. Press\u00a0R<\/kbd>\u00a0to start\u00a0Recovery Console<\/strong>\u00a0when the Options screen appears.<\/li>\n
            5. Type in your Administrator password followed by the\u00a0Enter<\/kbd>\u00a0key to submit it.<\/li>\n
            6. You’ll reach the Command Prompt now, type the following command, where\u00a0D:\\<\/code>\u00a0is your CD’s drive letter and\u00a0C:\\<\/code>\u00a0is the letter of the drive you installed Windows to:\n
              expand D:\\i386\\ntoskrnl.ex_ C:\\Windows\\system32\\<\/pre>\n<\/li>\n
            7. Press\u00a0Y<\/kbd>\u00a0when you are asked if you want to overwrite this file and then hit\u00a0Enter<\/kbd>\u00a0to submit the command.<\/li>\n
            8. Restart your computer.<\/li>\n<\/ol>\n
              Here is an example of what the PC’s console output should look like once the ntoskrnl.exe file is restored:<\/p>\n
              \"Restoring<\/a><\/p>\n
              Restoring the ntoskrnl.exe file<\/p>\n<\/div>\n
              Fix #6: Run chkdsk<\/h3>\n
              If this problem is being caused by a corrupt boot or system partition, it may be repaired by scanning the NTFS or FAT32 partition for errors or corruption.\u00a0chkdsk<\/code>\u00a0will verify files and data on the disk.<\/p>\n
              Here are the steps:<\/p>\n
                \n
              1. Insert your Windows CD; restart your computer.<\/li>\n
              2. Boot into the CD by pressing any key when the “Press any key to boot from CD” message appears on your computer.<\/li>\n
              3. Press\u00a0R<\/code>\u00a0to open the\u00a0Recovery Console once at the Options menu.<\/li>\n
              4. Type in your Administrator password; hit\u00a0Enter<\/kbd><\/li>\n
              5. At the command prompt, type in the following command and press\u00a0Enter<\/kbd>\n
                chkdsk \/r<\/pre>\n<\/li>\n
              6. After the\u00a0chkdsk<\/code>\u00a0process is completed, restart your computer. Make note of any warnings or alerts that\u00a0chkdsk<\/code>\u00a0prints.<\/li>\n<\/ol>\n
                Here is an example of what the PC’s console output should look like once the chkdsk.exe is complete:<\/p>\n
                \"Windows<\/a><\/p>\n
                Windows XP chkdsk result screen<\/p>\n<\/div>\n
                More Information<\/h2>\n
                Linked Entries<\/h3>\n
                The errors below have been verified as being associated with or related to this problem:<\/p>\n