|
|
|
missing or corrupt: ntoskrnl.exe
|
Original Message
|
Name: Michael Chernik
Date: July 21, 2000 at 08:16:41 Pacific
Subject: missing or corrupt: ntoskrnl.exe
|
Comment: I was just putting the finishing touches on an NT 4.0 server today when my supervisor told me I had to add 128mb more RAM, it had 128mb in it currently after installing the RAM I turned back on the machine and in the boot process received this error:
"Windows NT could not start because the following file is missing or corrupt:
\system32\ntoskrnl.exe
Please reinstall a copy of the above file."Is the solution as simple as running the Windows NT 4.0 Server installation CD ROM? OR??
Report Offensive Message For Removal
|
|
Response Number 1
|
Name: lm-s
Date: July 21, 2000 at 08:27:23 Pacific
|
Reply: (edit)That message usually means you need to run the ERD sequence for the installation... You can use either the 3 set-up disks, or the CD if your system will boot from CDROM... If you haven't got the ERD... then allow NT set-up to 'fix/repair' without the ERD. Usually it will... If it can't, and you're still stuck, you are probably best off by doing a bare-bones parallel installation into a separate (differently identified NT folder - e.g. winnt-2). This will re-establish the boot.ini etc. and you should be able to boot to original NT install, and the 'new bare-bones' version. When you're happy and able to access the original, delete the bare-bones version... I can't quite 'see' why upping the RAM would results in this error message... unless it's not correctly installed - even then it doesn't quite ring 'right...'? What happens if you remove the 'new' RAM and 'boot-up? Also what happens if you remove/re-install the RAM in case it is not properly seated/installed...
 Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: anon...
Date: July 21, 2000 at 09:07:49 Pacific
|
Reply: (edit)running the ERD and choosing the 'check the boot.ini' (or words the effect...) option does just that - and 'fixes' the problem...
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: Michael Chernik
Date: July 21, 2000 at 09:35:40 Pacific
|
Reply: (edit)"I can't quite 'see' why upping the RAM would results in this error message... unless it's not correctly installed - even then it doesn't quite ring 'right...'?" --------------
That would not be the error message for incorrect RAM type or RAM not properly installed.
--------------------------
"What happens if you remove the 'new' RAM and 'boot-up? Also what happens if you remove/re-install the RAM in case it is not properly seated/installed..."
----------------------------- Yes I did remove the RAM and reboot and the same error message resulted
I replaced the RAM agian and the same error message resulted. Possibly that extra boost of RAM jolted the feeble NTOSKRNL that was precariosly loaded in the original installtion therefore eventually this error message would have come up?
Report Offensive Follow Up For Removal
|
|
Response Number 5
|
Name: lm-s
Date: July 21, 2000 at 10:30:03 Pacific
|
Reply: (edit)Agree the error message is not the correct one for questionable RAM... But with M$ NT one never knows... As before, run the ERD and it 'should' repair/restore' your system to 'normal functioning... (In my not too limited experience with NT, it's capable of offering up errors 'at the drop of hat' for some systems/folks... but in fairness it is more stable etc. than '9x...)
Report Offensive Follow Up For Removal
|
|
Response Number 7
|
Name: lm-s
Date: July 21, 2000 at 15:05:26 Pacific
|
Reply: (edit)If you get the message "NTOSKRNL.EXE is missing, or corrupt," the culprit is usually the BOOT.INI file: Either it's missing, or its internal pointer to the NT system files is incorrect. If you've opened BOOT.INI in a text editor and verified that all is well, try copying NTOSKRNL.EXE from the distribution media to the \Winnt\system32 folder. courtesy of: http://www.aditec.com/troubleshooting.htm#26 which is part of: http://www.aditec.com/ the first link is worth following for a lot of useful info...; the second is the main/home page with other info...
Report Offensive Follow Up For Removal
|
|
Response Number 10
|
Name: Charlie
Date: September 19, 2000 at 10:12:18 Pacific
|
Reply: (edit)Hey. Well I get the same error message, my problem i have no setup disks. Is there anyway to bypass the ntdetect os loader>??
so i can just boot Win.?
please help this is very important. If possible send me an direct email.
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
|
|
|
