NTOSKRNL.EXE missing or corrupt?

  • Thread starter Per Morten og Susanne
  • Start date
P

Per Morten og Susanne

I get the error "NTOSKRNL.EXE missing or corrupt" on bootup.

in windows 2000 server I receive this error on boot up:

Windows could not start because the following file is missing or corrupt.

<Root>\system32\ntoskrnl.exe

Please reinstall a copy of the above file.



After several failed attempts to correct this with the emergency repair
disk, I tried reinstalling from scratch, which solved the problem for a few
months. The problem has now re-occurred with the same symptoms. Windows was
installed on a different drive so that aspect can be out ruled. I do have
USB connections for camera scanner and external DVD burner on this computer.
AnY advice experts?
Per Morten
 
D

Doug Sherman [MVP]

Unfortunately, this error can result from a wide range of problems. If you
are lucky, the file really is simply missing or corrupt; however, the normal
repair functions you have tried should replace it.

Probably the second most common cause for this error is disk or MBR errors.
If you have not installed the Recovery Console, boot to the Win2k CD ROM and
run Recovery Console from there. If you are able to log onto the WINNT
installation, run chkdsk, fixboot, and fixmbr.

The following is for XP, but Win2k is basically the same:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314058

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
P

Per Morten Josefson

I am able to reach winnt, since the program appears to work now. Everything
seems perfect, but if I restart, the trouble is back again.
Is it possible to run fixboot and fixmbr witout restarting the pc and
booting from the cd rom?
The recovery console is installed.
PM
 
D

Doug Sherman [MVP]

If the Recovery Console is installed, you no longer need to boot from the
CD - it will appear as a Startup option which you can select when you boot
the computer from the hard drive. However, you will still have reboot after
running the Recovery Console.

One thing you may not have tried is a full repair install: Boot to the CD.
After the drivers finish loading, do NOT select Repair - select to install
Windows. If setup can find the existing installation, it will give you the
option to Repair it. Selecting this option results in a complete reinstall
which preserves your applications, desktop, etc. If this solves the
problem, you will need to reinstall service packs, updates, and possibly
some drivers.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
P

Per Morten og Susanne

Ill try this. Thank you for the interest in my problem.

pr morten
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top