brainbolt
asked on
ACTIVE ISSUE: \system32\ntoskrnl.exe missing or corrupt
This issue is getting all of my live attention right now, so I thought I would post it and get some suggestions as I try to troubleshoot.
I tried to install a SCSI DAT72 tape drive on my Dell PowerEdge 2800 tonight. I powered the machine down and then attached device and powered the machine back on. When I did, I got the following error:
Windows could not start because the following file is missing or corrupt:
<windows root>\system32\ntoskrnl.ex
please re-install a copy of the above file.
I powered the machine back down, disconnected the DAT72 drive (to eliminate it as a variable) and powered the machine back on. Same issue.
Right now I am running chkdsk from the recovery console, but I'm worried because it keeps cycling from 70% complete back to 50% complete. It's been going for about an hour now, but I don't know if that is normal or not.
Any thoughts?
I tried to install a SCSI DAT72 tape drive on my Dell PowerEdge 2800 tonight. I powered the machine down and then attached device and powered the machine back on. When I did, I got the following error:
Windows could not start because the following file is missing or corrupt:
<windows root>\system32\ntoskrnl.ex
please re-install a copy of the above file.
I powered the machine back down, disconnected the DAT72 drive (to eliminate it as a variable) and powered the machine back on. Same issue.
Right now I am running chkdsk from the recovery console, but I'm worried because it keeps cycling from 70% complete back to 50% complete. It's been going for about an hour now, but I don't know if that is normal or not.
Any thoughts?
ASKER
UPDATE:
chkdsk finished, and it reported finding an error and fixing it. I rebooted the machine, and the OS booted up. It looks like chkdsk addressed the issue, but now I am concerned. Could this issue be an indication of something that needs to be further addressed, or is it likely in this case that all is well that ends well?
chkdsk finished, and it reported finding an error and fixing it. I rebooted the machine, and the OS booted up. It looks like chkdsk addressed the issue, but now I am concerned. Could this issue be an indication of something that needs to be further addressed, or is it likely in this case that all is well that ends well?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I forgot to give the repair install link: http://www.techspot.com/vb/topic8356.html
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Review the boot.ini file and ensure it correct.
Any hidden diagnostic partitions on the drive?