How to reinstall file

  • Thread starter Thread starter Dan Garrett
  • Start date Start date
D

Dan Garrett

I have the following on my computer:

Windows could not start because the following file is
missing or corrupt:
<Windows root>\system32\notskrnl.exe.
Please reinstall a copy of the above file.
 
I have the following on my computer:

Windows could not start because the following file is
missing or corrupt:
<Windows root>\system32\notskrnl.exe.
Please reinstall a copy of the above file.

http://support.microsoft.com?kbid=103673 "Err Msg Windows Could Not
Start...[Missing Ntoskrnl.exe]"
http://support.microsoft.com?kbid=119467 "How to Create a Bootable Disk for an
NTFS or FAT Partition"
http://support.microsoft.com?kbid=124550 "Err Msg Windows NT Could Not
Start...Ntoskrnl.exe"
http://support.microsoft.com?kbid=827188 "You Receive a 'STOP 0x7F' Error"


Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 
In said:
I have the following on my computer:

Windows could not start because the following file is
missing or corrupt:
<Windows root>\system32\notskrnl.exe.
Please reinstall a copy of the above file.

Double check that spelling "notskrnl.exe".
See Jerold's post for "ntoskrnl.exe"
 
I just got this on a system yesterday...it appears to be a popular error,
but wondering if there's been a surge in occurances, found lots of recent
posts regarding it.....any way not really cmdprmpt related :)
 
i was building a new system over the weekend and I got the error.

I had played with my BIOS settings... more aggressive memory timings and
such... when i took it back to the defaults, it was fine.

I normally see this when i am pushing the limits of my hardware just a
little bit too far.

If you have been playing in the bios, go back to the defaults and you should
be ok. If you insist on making changes, make only one change at a time, and
test the system stability thoroughly before making other changes.

Even changes, such as CAS level of your memory can result in this message,
so be very careful, and make sure you take copious notes as to the changes
you make. that way, you have a good record of what works best with your
hardware, should you have to clear the cmos at somepoint in the future.

A good tool to measure performance effects of changes you make is Sandra.
(www.sisoft.com)

Good luck,

NuTs
 
Back
Top