ntoskrnl.exe is corrupted. windows wont open

May 24th, 2004, 2:16 am

//moderator removed - Garth -I'm sorry but we do not permit assistance with problems caused by unlawfully obtained software. You'll have to go off of what's been provided for information already, or what may be provided here in the future, but please don't ask for further assistance in regards to the pirated software. -- ATNO

May 24th, 2004, 8:45 am

Unfortunately, I do not have a fix for this problem beyond reinstalling windows. Perhaps someone else may.

A copied version?

May 27th, 2004, 5:21 pm

What was that recovery installation that you mentioned? Does that require a recovery disk or simply the Windows 2000 cd? Any help is greatly appreciated.

Thanx in advance,
Cerberus 561
P.S.
the above post was mine

May 27th, 2004, 5:22 pm

Hey,

I have had the exact same problem on my computer. I tried a million different things like copying ntoskrnl.exe from a different computer running the exact same operating system (probably except the service pack #) and I tried copying the file from the "C:\winnt\system32\dllcache" and "C:\winnt\system32\i386\driver cache"
I think in my attempt to copy from the file I had from another computer I might have copied over the existing files you suggested for recover. Am I up a creek?

thanx,
Cerberus 561

May 27th, 2004, 6:17 pm

Not knowing exactly what you have done, I can't be sure. I don't know all of the differences between XP and 2000. I only have direct experience with XP.

Copying the ntoskrnl file from another system may not work if one is updated with service packs and another is not. Copying the ntoskrnl file from the original CD presents problems as well. Sevice packs and other updates in the past have replaced this file with newer versions. Trying to use an older version of the ntoskrnl.exe usually results in the system not booting.

In response to your first post, the recovery console is a part of the Windows 2000 installation disk. (not oem recovery). Just follow the link at the beginning of this thread and the updated instructions for restoring the file.

If you are able, list the contents of the C:\winnt\system32\i386\driver cache directory. Specifically, which cab files are present. There may be a usable ntoskrnl file present.

Good Luck

* There seems to be a lot of this about.
* Anyone that is successful in booting their system should do a complete
* Virus Scan

May 27th, 2004, 6:44 pm

Thanks Jrzy Crim,

I have tried all that you said. My brother had said that a difference in service pack number might cause a problem. I think that I covered all possible bases in advance and that there is not much hope left of replacing the ntoskrnl.exe file. But wes19 had mentioned a repair installation. Is that as he described that the system pack number would be eliminated but that my programs woul remain? I was contemplating overall format and repartitioning so any help would be much much appreciated.
thanks,
Cerberus 561

May 27th, 2004, 6:47 pm

If a repair installation is an option with your CD, then all of your programs will be left intact. Service packs and updates will have to be reinstalled.

Sorry about your troubles, btw, I know what a pain things like this can be.

May 27th, 2004, 6:51 pm

Agreed. Im bettin we have all been there. Good luck with it.

May 27th, 2004, 7:05 pm

thanx

June 2nd, 2004, 5:21 pm

JrzyCrim , I have the same problem as that person, but when i turn on my computer it wont run setup, and i can not get into safe mode at all.
Can you please help me out.

June 6th, 2004, 4:33 am

i hav tried both of those sets of commands, the first says it works, then i reboot and the same problem happens. the second set of commands says that the file cannot be found.

ne help would be greatly appreciated, and thanx for all the help already[/php]

June 20th, 2004, 4:09 am

After much work, prob about 4 hours a night for like 3 nights on this one prob, not to mention my brother trying to recompile the linux kernel in order to gain NTFS readability from my linux OS to salvage some of my documents and stuff, my computer is finally up and running. It is the best machine in this household and I am much obliged to JrzyCrm and Wes19 for starting the thread. If I didn't mention you, consider yourself thanked anyway. By the way I am writing this post from this fixed machine. Oh, and one last point. I reinstalled Windows 2000 (no recovery disc or anything) and it said that is would overwrite the My Documents, yet is neither overwrote My Documents nor Program Files. Stoked!!! Just thought I'd let u know my solution to this epidemic problem. Sorry for the length.

[ATNO/TW]

June 20th, 2004, 5:44 am

I had the pleasure of a corrupted ntoskrnl this week myself. *lol Not sure exactly what caused it, but something went a little whacky when I instlled XP Pro as an additional OS using System Commander. I thought I had hidden the Win2k Pro partition on install, but must have missed it.

I thought immediately of this thread. Unfortunately, I can't confirm how well the instructions work because I didn't follow them. I was overdue to clean up my OS anyway, so my workaround solution was to add a third partition and installed a clean second copy of Win2K. That went off without a hitch and XP was unaffected. My reason for choosing this method was because I knew with the clean install the original corupted Win2K would still show up as my d: drive (which it does, so I still retain access to all my original files which is all I needed it for anyway. In addition, I also can access the XP files while on Win2K and vice versa. The only downside was reinstalling all the programs but I wanted better organization anyway.

Not quite the perfect workaround, but it satisfied my needs.

July 5th, 2004, 9:34 pm

Ok I am having a problem with this ntoskrnl.exe file.

When I boot up my computer I get an error saying "Invalid Boot.ini file. Now booting from C:\Windows..."

Then like 5 seconds after that screen pops up, another black screen pops up saying "Windows could not start because the following file is missing or corrupted: <windows root>system32\ntoskrnl.exe. Please reinstall this file."

Well I tried to fix the boot.ini file first by going into the recovery console and typing in:

bootcfg /rebuild. But it always says "Error: failed to successfully scan disks for Windows installations. This error may be caused by a corrupt file system, which would prevent bootcfg from successfully scanning. Use chkdsk to detect any disk errors."

I ran chkdsk and it said it fixed errors but this error still appears at startup.

So now I try to fix the ntoskrnl.exe problem by following the directions in this thread http://www.ozzu.com/posting.php?mode=reply&t=24580 But everything I try it just ends up saying "The following file could not be found" or something like that. I may be typing them in wrong but I tried both of the solutions from the second post numerous times. I could reinstall windows but last time I ignored these same exact errors they just eventually came back. What should I do?

July 5th, 2004, 10:44 pm

Hello Duto8672,

Unfortunately I do not have any other advice to offer beyond what has already been given. It sounds as if your installation is corrupted beyond repair.

The only thing I can suggest is to start from scratch. I know this not what you want to hear but I do not believe your existing installation is recoverable.

You mentioned reinstalling Windows and that later these same problems occured. Was that a repair install? If it was a clean install, did you reformat?

If not, I would suggest you follow this guide for reinstalling XP.
http://www.blackviper.com/Articles/OS/I ... xppro1.htm

During setup, you should delete all partitions and then recreate any partitions you need. Do a full format, not quick, and then proceed with the installation.

If these steps still do not fix your problem, It might be indicative of a failing hard drive. I hope for your sake it isn't but honestly, I don't know what else to suggest. You might try going to the manufacturer's website to download a diagnostic utility to test your drive.

Feel free to respond with more questions.

Good luck

I'm very sorry about your troubles.