marlyn said:Hi! My computer si win xp prof. When I start it just give me a message that
says.."Windows could not start because the following file is missing or
corrupt (Windows root>system32>\ntoskrnl.exe) HOw to reinstall these
missing and corrupted files? Please help me...thanks a lot
wyocowboy said:When I see these kind of problems I usually use chkdsk /r from recovery
console first (as described in
http://www.computerhope.com/issues/ch000646.htm)...
repeating until chkdsk no
longer reports that it has found and fixed problems. In between each run, you
have to exit recovery console, reboot and repeat.
Steve N. said:Ok, but some of the other things to try in that article may take less
time than chkdsk /r and possibly directly address the OPs specific issue.
I have done likewise but in my experience a reboot between has not
necessary.
wyocowboy said::
The reasons I run chkdsk first is that I can fire it up and work on other
machines in the meantime, and that there may be file system corruption in
other areas besides the area that is keeping the system from booting. If
chkdsk says it is clean (or non-recoverable), then I can proceed with some
level of confidence.
In one case, the boot.ini was corrupted and I fixed that from the RC command
line, but it still wouldn't boot. Although I could see the \windows directory
and most of its contents, there was some corruption within that kept it from
booting (got a new error message). Chkdsk /r fixed this system, but it may
have fixed the boot.ini problem as well, had I run it first.
I used to think so too, until I experimented with it on several system with
disk corruption. I've run chkdsk /r from RC on somewhere between 20-30
machines. On one, the first time I ran chkdsk, it came back with "there
appears to be one or more unrecoverable errors" and chkdsk would not run. I
tried running it another time or two in the same RC session and got the same
results. Since the customer had not backed up their data and my mission was
to try to retrieve it, I exited RC, rebooted and tried again, and this time
chkdsk ran and fixed things.
On other systems, chkdsk /r would find and fix errors, so I would run it
again from the same RC session and it would not find further errors, but the
system still would not boot. Figuring that I had nothing to lose but a little
time, exited, rebooted and again ran chkdsk /r from RC and lo and behold, it
found more errors.
Based on what I've run across in various postings, it seems like there is
something that gets flushed with a reboot that causes chkdsk to find and fix
things that it can't when there is no reboot in the interim. It also seems
that multiple passes fix things that single passes won't.
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.