Issue:

NTOSKRNL.EXE is missing or corrupt.

Related errors:

Below is a listing of the full error message that may be related to this error.

Windows could not start because the below file is missing or corrupt:

C:\Windows\System32\Ntoskrnl.exe

Cause:

1. Keyboard issue
2. Miscellaneous corruption
3. Corrupt boot.ini file.
4. Missing boot.ini file.
5. Missing or corrupt ntoskrnl.exe file.
6. Windows installed on a partition bigger then 7.8GB
7. Corrupted hard disk drive or severely corrupted Windows.

Solution:
Keyboard issue

This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.

Miscellaneous corruption

Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.

Corrupt boot.ini file

This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.

Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.

Missing boot.ini file

Microsoft Windows XP users:

If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648.

Missing or corrupt ntoskrnl.exe file

If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.

1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
4. Select the operating system you wish to fix, and then enter the administrator password.
5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
7. Type exit to reboot the computer.

Corrupted hard disk drive or severely corrupted Windows

Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.

1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
4. Select the operating system you wish to fix, and then enter the administrator password.
5. Once at the recovery console type chkdsk /r
6. Once completed type exit and see if issue is resolved.

If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186.

Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.

well, depending on what brand hdd u have, what i wld do is download software to check the condition of the hdd. (which you have already done) i assume you have also done a chkdsk to check the integrity of the file system? if the hdd checks out ok, i wld then run a complete anti virus/spyware scan on the hdd.

This post has been edited by alfie: Feb 20 2008, 11:58 AM

it sounds to me like the drive is def faulty