ntoskrnl.exe is missing or corrupt followed by BSOD

mfozaydin · Oct 19, 2011

Dear Major Geeks,

I got an error message saying Windows cannot start because <windows root> system32 / ntoskrnl.exe file is mising or corrupt. I pressed the ESC key and the windows XP were able to start but first I got the BSOD then I shut down and restarted this time It worked. I am assuming that this was a temporary solution. Please help me to fix this issue.

Thanks.

TimW · Oct 19, 2011

Moved to the software forum.

mfozaydin · Oct 21, 2011

Dear TimW,

I started my laptop by using windows recovery console and ran the "chkdsk /r" command. After I exited and restarted I did not get he ntoskrnl.exe error message but I got 3 consecutive BSOD's. I wanted to attach them with this message for your review but they are not there now. Do you have any idea given your experiences that what could have caused the BSOD.

Thanks.

plodr · Oct 21, 2011

If all BSODs show different errors, the first thing I do is check the RAM.

mfozaydin · Oct 21, 2011

Thanks plodr. Would you please tell me how to read the dump files? What do you mean by checking the RAM?

Regards.

plodr · Oct 21, 2011

I don't know how to read dump files, sorry.
I'd suggest MemTest 86+ burned as a bootable CD and run at a cold boot. If just 1 error is detected, you can stop it immediately because there is a RAM problem.
http://majorgeeks.com/Memtest86_d4226.html
Test each stick individually if there is an error so you can determine the bad stick.
If you don't see any errors, let it run for 3 or 4 passes. It might take awhile so plan to let it run while you do something else.

Log in or Sign up

ntoskrnl.exe is missing or corrupt followed by BSOD

mfozaydin Private E-2

TimW MajorGeeks Administrator - Jedi Malware Expert Staff Member

mfozaydin Private E-2

plodr MajorGeek Super Extraordinaire Moderator Staff Member

mfozaydin Private E-2

plodr MajorGeek Super Extraordinaire Moderator Staff Member