https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370368#M34519 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 the above file".<BR />We have 2 ML-350 servers doing intensive I/O work. Sometimes we have to shut those computers down due to power failures (clean shutdown UPS is connected)<BR />Then when we turn on those computers (already happened 3 times for one and 2 for the other) we get the above message<BR />Any help tracking the source of the problem will most appreciated (I know how to recover)<BR />Thanks</WINDOWS> Wed, 01 Sep 2004 16:39:27 GMT Guy Tamir 2004-09-01T16:39:27Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370368#M34519 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 the above file".<BR />We have 2 ML-350 servers doing intensive I/O work. Sometimes we have to shut those computers down due to power failures (clean shutdown UPS is connected)<BR />Then when we turn on those computers (already happened 3 times for one and 2 for the other) we get the above message<BR />Any help tracking the source of the problem will most appreciated (I know how to recover)<BR />Thanks</WINDOWS> Wed, 01 Sep 2004 16:39:27 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370368#M34519 Guy Tamir 2004-09-01T16:39:27Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370369#M34520 Guy:<BR /><BR />It could very well be that the RTC battery is weak and failing. If it cannot keep the configuration settings, this can occur. Does your server require you to press F1 at Boot?<BR />Do you get any POST Error Messges at boot?<BR /><BR />Depending on your version of ML350, you may need to re-run the System Configuration Utiltiy from your SmartStart CD on the server and make sure it detects you boot controller.<BR />Or, enter the RBSU and make sure the boot controller order is correct.<BR /> Wed, 01 Sep 2004 17:49:44 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370369#M34520 JohnWRuffo 2004-09-01T17:49:44Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370370#M34521 <I><BR /><BR />this message appears when the first stage bootloader cannot read the disk supposed to contain the system partition (remember microsoft boots from the system partition and runs the system from the boot partition)<BR /><BR />heat based failure? don't scoff, it happens. disks shut down or connections falter. run the diagnostics when it's cold then again after the server has bee running a while. <BR /><BR />what do you do to recover? that might help determine the root cause.<BR /></I> Fri, 03 Sep 2004 08:07:52 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370370#M34521 Thomas Bianco 2004-09-03T08:07:52Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370371#M34522 Hi,<BR />Thanks for the Information the RTC does seem as the right direction. The main problem is that I'm not on site and getting the info from local stuff (that is not well trained)<BR />so its a bit hard for me to know the exact facts after the system load other then the error description<BR /> Mon, 06 Sep 2004 01:56:31 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ntoskrnl-exe-is-missing/m-p/3370371#M34522 Guy Tamir 2004-09-06T01:56:31Z