ntoskrnl.exe problem

  • Thread starter Thread starter Pegasus \(MVP\)
  • Start date Start date
P

Pegasus \(MVP\)

Adam Smith said:
Hello,

Win 2K Professional, Pentium, 223MHz platform
Frequent crashes, "blue screens", reboot messages ==>

"Windows could not start because the following file is missing or corrupt:
<WINDOWS2000 ROOT>\system32\ntoskrnl.exe. Please re-install a copy of
the above named file."

However, A F8 mode reboot, with "Last Known Good Configuration" skirts
the re-installation issue.

What is causing this, and what corrective procedures can I follow (I
have the latest updates installed.)

Thanks!


-- Adam --
Click to expand...


This message usually comes up when the boot process is unable
to locate ntoskrnl.exe, either because it is not where it should be
(according to c:\boot.ini), or because it is unreadable.

Since you can start the machine under LKGC, the file must be
in the right place. The casts a suspicion on your hard disk. It
could be on its way out. Your frequent crashes might be
caused by it too. Time to run chkdsk, or perhaps to download
and run your disk manufacturer's diagnostic diskette (free!)
from his home page.
 
Hello,

Win 2K Professional, Pentium, 223MHz platform
Frequent crashes, "blue screens", reboot messages ==>

"Windows could not start because the following file is missing or corrupt:
<WINDOWS2000 ROOT>\system32\ntoskrnl.exe. Please re-install a copy of
the above named file."

However, A F8 mode reboot, with "Last Known Good Configuration" skirts
the re-installation issue.

What is causing this, and what corrective procedures can I follow (I
have the latest updates installed.)

Thanks!


-- Adam --
 
Hi,
Adam/Pegasus
can anyone help. I can get no further than the missing or corrupt
ntoskrnl.exe file message.I have no "Last Known Good Configuration" option on
F8,any suggestions on how can I re-install a copy of the file, can I download
a self executing version to floppy?I'm rather green at this, any help would
be really appreciated
 
Phil - bad idea, piggybacking on a post that's likely a different
problem than yours. Many things can cause that "ntoskrnl missing"
message, and you provide no background at all.

Start a new thread, similar title, and provide more info about what
you've done, observed, and so on. The way Adam did.
 
Dan et All
sorry -new at this. Did as you suggested (see ntoskrnl.exe 11/2/05) good
suggestions from John John
 
Back
Top