Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows 2000 Could not Start :( ntoskrnl.exe 2

Status
Not open for further replies.

skipholiday

Technical User
May 9, 2002
129
US
I tried to install a copy of 2000 pro on my pc and I keep getting this error...
(Windows 2000 could not start because the following file is missing or corrupt:
<windows 2000 root>\system32\ntoskrnl.exe
Please re-install a copy of this file)
At 1st I thought it was something to do with my harddrive so I tried another and recieved the same error at post.
I have tried formatting repartioning and nothing works.
I also tried to install a copy of 98 to see if it was something wrong with my 2000 disk.98 also gets an error.
Any help would be greatley appreciated.
Thanx in advance
Skipholiday

 
This is sometimes due to an error in the boot.ini file. The entry for Windows 2000 Pro may either missing or incorrect. Edit the boot.ini file and check the entry for Windows is correct, for example for an entry should look something like:

[boot loader]
timeout=10
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT=&quot;Microsoft Windows 2000 Professional&quot; /fastdetect

Check that disk and partition are correct. If you have recently added a new disk or altered the partitions try changing the disk() and partition() values.

If you are sure everything is OK, then the actual file may be corrupt so copy NTOSKRNL.EXE off of the installation CD onto the %systemroot%\system32 directory. (C:\WINNT\SYSTEM32)

Hope this helps.

 
Is your W2K Pro installation disk with SP4?
 
You've almost certainly got a hardware problem. Start with RAM (use each stick on its own, if > 1, otherwise get hold of known good replacement), then try elimination (disconnect as many hardware dveices as possible, replace where can't disconnect, as far as possible).

Check all cabling is sound and firmly connected, everything seated properly, fans working...
 
No it doesnt have service pack 4, I update after I install.
I did install a new video card and all worked well b4 I decided to repartiton and and install a fresh copy of 2000.
Hmmmm could that be my problem?
Thanx for all the help. I will keep working on it :)
 
Thanx for the help .It was the video card??
I really don't understand why it started. The card was working fine b4 I re-installed 2000.I had put it in after the original install,then when I repartioned the drive and re-installed the problem started. O well its going now :)
Thanx again
Skipholiday
 
I can't believe it,after about 2 hours of running and then reboot to install new updates the error is back? I'm usint the onboard graphics on an epox mb.
I'm clueless...
 
I re-installed a copy of the file and all seems well so far. :)
Thanx for the help
 
skipholiday, did you try what I said?:

copy NTOSKRNL.EXE off of the installation CD onto the %systemroot%\system32 directory. (C:\WINNT\SYSTEM32)

It should work...
 
yes and thanx :)
Its still running so far.
Something kept corrupting it ,I think when I did the upgrade to sp4 is when it actually happened, (when I rebooted).
The vid card just happened to be installed prior to the update.
Thanx again
I will post back if it all goes whacko :)
 
I had a similar problem to this a while ago.

PC was the following spec.
Asrock Main Board.
AMD 2000 XP CPU
512Meg Ram chip
128Meg Ram chip.

Windows would not install, PC continuously re-booted, during install I would get messeges saying that files could not be found on the CD-ROm, everytime you tired the install different files would be missing.

ntoskrnl errors left right and center.

it was a faulty 128 Meg RAM chip.

 
ntoskrnl.exe this file intilizes memory. When this exe file (program) tries to do its job and the memory is bad you will get this error. Try one ram stick at a time until faulty stick is found. If only one stick try another out of a known operational system. If this works purchase a new stick of ram. I just had this problem last night trouble shooting a customers system that will not boot. It would not even perform the post.

Good Luck
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top