Results 1 to 4 of 4

Thread: Error : ntoskrnl.exe missing or corrupted !

  1. #1

    Question Error : ntoskrnl.exe missing or corrupted !

    Sab teh majedar problem jo mein face kar raha hoon recently from 2 weeks !
    System Configuration : P IV, 256 MB DDR RAM, 40 GB HDD, Intel 845 GVSR M/B, normal K/b & mouse with Win 2k Prof. installed ! Problem yeh hey bhai logo ke jab bhi yeh system start hota hai yeh ntoskrnl.exe ka error deta hain aur agar aap isko restart kar do toh koi problem nahi restart ho jayega aur maje ki baat koi error nahi deta aur phir yeh raat tak sahi kaam karta hai, isko agar hum dubara shutdown karke 5-7 min baad phir restart kare tab bhi koi problem nahi, lekin tadkein-tadak isney ek bey yoh natak jaror karna !Mujhe toh lagta hai jaise bike mein starting problem hoti hain na wasi hi kuch problem hain, eb bhai logo man ney teh iski RAM badal k dekh li, Harddisk format kar ke reinstall kar ke dekh liya aur bhai logo batao k R & D kari ja sake se iski galya, ish Chote se Balak ki help karo bhai ! Acha ek aur baat dusre sahi chalan aale system teh ntoskrnl.exe ki copy bhi maar k dekh li !
    To err is human, to forgive is Not Company Policy !

  2. #2

    Thumbs up NTOSKRNL.EXE is missing or corrupt.

    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 NT could not start because the following file is missing or corrupt:

    C:\Winnt\System32\Ntoskrnl.exe

    Cause:

    Miscellaneous corruption
    Corrupt boot.ini file.
    Missing boot.ini file.
    Missing or corrupt ntoskrnl.exe file.
    Windows NT installed on a partition bigger then 7.8GB
    Corrupted hard disk drive or severely corrupted Windows.
    Solution:

    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.

    Microsoft Windows NT and Windows 2000 users:

    To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need a ERD and follow the below steps. If you do not have a ERD you will be unable to follow these steps.

    Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
    In the setup menu, type R to start the repair.
    When prompted for the ERD diskette insert the diskette and inspect the startup environment.
    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.

    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.
    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.
    In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
    Select the operating system you wish to fix, and then enter the administrator password.
    Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
    You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
    Type exit to reboot the computer.
    Windows NT installed on a partition bigger then 7.8GB

    If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the error message as shown below.

    OS Loader v4.01
    Disk I/O error status=00000001
    Windows NT could not start because the following file is missing or corrupt: winnt\system32\Ntoskrnl.exe
    Please reinstall a copy of the above file.

    If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.

    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.

    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.
    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.
    In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
    Select the operating system you wish to fix, and then enter the administrator password.
    Once at the recovery console type chkdsk /r
    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.
    Deepak Sejwal
    ---------------------------------------------------------------------------

  3. #3

    try this option

    Hi ankur

    Try to copy ntoskrnl.exe file from another system which is not giving the similar problem.if u r not able to copy through LAN,make this HDD slave & copy the same file.reboot the system after copying.

  4. #4

    check your RAM

    Did you install new RAM recently? Please check If it is compatible with your pc.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •