No boot Windows 7. Error: ntoskrnl.exe is missing or corrupt
Had Windows XP, Did a custom installation (with format) of Windows 7. The installation was successful and got the desktop. When I restarted the computer, it gave me an error saying ntoskrnl.exe is missing or corrupt. I think this is not a Windows 7 file.
It doesn't boot into windows advanced options. No issues with the windows 7 disk.
HELP WILL BE APPRECIATED!!
This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread.
When you boot your Windows 7 you might be seeing the following message
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click “Next”.
3. Click “Repair your computer.”
The file is ntoskrnl.exe, and it's a core operating system file. If it's
corrupt or missing you have a major problem. Quite often though, this error
is a symptom of a different problem. You stated that you made no recent
changes to hardware/software, but have you accounted for driver updates and
updates to programs like your antivirus software? There is also the
possibility that you may be experiencing a hardware failure, this is not
uncommon in a new system. If such is the case, the system should still be
under warranty and Sony should be contacted.
Have you tried accessing the boot menu by hitting F8 at startup? If so, have
you tried loading Safe mode?
First try booting and safe mode and see what happens
To boot into safe mode, follow the below steps:
1. Remove all floppy disks, CDs, and DVDs from your computer, and then restart your computer.
Click the Start button, click the arrow next to the Lock button, and then click Restart.
2. Do one of the following:
• If your computer has a single operating system installed, press and hold the F8 key as your computer restarts. You need to press F8 before the Windows logo appears. If the Windows logo appears, you will need to try again by waiting until the Windows logon
prompt appears, and then shutting down and restarting your computer.
• If your computer has more than one operating system, use the arrow keys to highlight the operating system you want to start in safe mode, and then press F8.
3. On the Advanced Boot Options screen, use the arrow keys to highlight the safe mode option you want, and then press ENTER. For more information about options, see Advanced startup options (including safe mode).
4. Log on to your computer with a user account that has administrator rights.
When your computer is in safe mode, you'll see the words Safe Mode in the corners of the display. To exit safe mode, restart your computer and let Windows start normally.
If Safe Mode does lilttle help, there are 2 workarounds that may fix the issue.
Workaround 1 :
You’ll need to manually restore some files again to the version that came with your Windows installation DVD. Use the Windows DVD to boot into repair mode and restore these files using the command prompt:
In your “\Windows\System32\” folder, restore just these files:
ntoskrnl.exe (You shouldn’t need to replace it because it’s not really corrupted.)
ntkrnlpa.exe (Same as ntoskrnl.exe. Try booting without replacing them first)
And in your “\Windows\System32\Drivers” folder, restore these:
Make sure to rename or backup the files you’re going to replace (just in case you do something wrong). All the original files you’ll need to replace your “corrupted” files with should be found inside the virtually mounted drive (X:\), so they should be in “X:\Windows\System32″\
and “X:\Windows\System32\Drivers\” (you don’t need to “expand” any files like the old XP days, you’ll just need to use basic “copy” and “rename” commands).
HINT: If you’re not too comfortable using the command prompt, you can use the notepad’s file browser to copy and paste files from inside the repair DVD. Just type “notepad.exe” in the command prompt and set the file type to ALL inorder to see non-txt files.(WARNING:
It doesn’t prompt you when overwriting files and It doesn’t show hidden or system files, but you shouldn’t need it to anyways)
You should’nt need to restore any other files for you Windows to boot. Don’t just replace all the files inside your “System32\Drivers\” folder like what that article said, that will probably do more harm than good. I used the debug boot log file from inside
my Windows folder (ntbtlog.txt) to determine which files Windows is using while attempting to boot, and then I checked their file version from inside the repair DVD (right click>properties>details or just leave the mouse pointer on the file for a second);
If it was 6.0.6001.18000 (SP1 release version), I replaced it with the old version from my boot DVD.
hal.dll did actually give me some trouble because it wasn’t in the X: drive. And unfortunatly it’s the VERY FIRST file the Windows Loader tries to load at boot so you’ll have to get it somehow. You can use the Automatic Repair Method as follows
If you look inside your “C:\Windows\System32″ folder, You will see three files: hal.dll, halacpi.dll, and halmacpi.dll. You will likely see that hal.dll is the same size as one of them. That’s because it’s exactly the same file just copied and renamed. Basicly
if you have a multi-core PC you’ll need to use halmacpi.dll and rename it to hal.dll, If you’re running a single core PC you need to use halacpi.dll instead. The “winsxs” folder only has these two files and not hal.dll straight up because it kinda depends
on the type of processor you’re using. So look inside your “winsxs” folder for folders that start with “x86_hal.inf_XXXXXX_6.0.6000.20500_none_XXXXXXX” and you’ll find these two files inside along with a “hal.inf” which you won’t need to replace (it’s inside
the “inf” folder in your Windows directory), and then copy whichever one you should use -depending on your processor- to your “C:\Windows\System32\” folder. Now that I think about it, It’s probably better if you replace both halacpi.dll and halmacpi.dll inside
your System32 folder too (Just to be on the safe side).
NOTE: You’ll probably find two or more folders that start with “x86_hal.inf” in your “winsxs” folder, but make sure:
1)The folder starts with just “x86_hal.inf” not “x86_hal.inf.resources”
or you can look for it in your Windows folder inside your “winsxs” (ex C:\Windows\Winsxs\) folder (a folder that Windows 7/Vista uses to basicly backup every version of every file ever made for Windows 7/Vista) But it’s kinda of tricky because:
1)The file is deep inside “winsxs” which has TONS of folders and files
2)The file itself is kinda of tricky to back up because the exact file isn’t actually there.
Workaround 2 :
1) Close all applications running and temporarily shut down if you have any Anti Virus program
2) Disconnect all usb (EXCEPT MOUSE)
3) Now boot with the Windows 7 Operating System CD and do a repair using the following procedure
* Insert your Windows 7/Vista DVD and then restart your computer.
* Press any key or the appropriate function key (depends on your computer) to boot to the DVD.
* When your computer has booted to the DVD select your language and then press Next.
* Click Repair your computer on the next screen.
* Select the operating system your want to repair. There is usually only one here unless you’re dual booting.
* Click Startup Repair on the next screen.
* The Startup Repair tool will attempt to fix your computer and get it booting up again.
You don’t have to do anything from here on. Your computer might reboot a few times and it might be a few minutes before it finishes.
It goes thru the following
Long time to load (green bar)
Installing Stage 1 of 3
Installing Stage 2 of 3
Installing Stage 3 of 3
Installing Stage 1 of 3
Installing Stage 2 of 3
Installing Stage 3 of 3
6) Finally it starts up with the Windows 7/vista Screen Saver – hit any key and logon.
7) Now re-connect all USB and re-start any programs.
Also see :
Source link : http://social.answers.microsoft.com/Forums/en-US/vistainstall/thread/7663939c-6e45-43ab-82e5-0d90894de156
Hope it works
Azeez Nadeem - Microsoft Support
30 people were helped by this reply
Did this solve your problem?
Sorry this didn't help.
Great! Thanks for marking this as the answer.
How satisfied are you with this reply?
Thanks for your feedback, it helps us improve the site.