I recently had to repair the NT 4.0 server OS as it carshed. I repaired it using the cD and it reinstalled a few files. The problem was I did not have an Emergency Repair Disk. So I just repaired it using the CD and it replaced some files. Then I reinstalled NT 4.0 option pack for IIS. However, there is a new problem now. The computer randomly crashes giving a message that an exception in ntoskrnl.exe has not been handled. Also when I boot up I get the message "\systemroot\system32\drivers\spud.sys device driver could not locate the entry point MmUserProbeAddress in driver ntoskrnl.exe". This server happens to be our development server. As a result everything's at a standstill right now. Please help.

Thanks,
Ram.

Maybe others can post their experience, but I have never seen an NT server or workstation "repaired" (with or without the ERD) function normally after the repair. There are always glitches, either large or small, and I always end up having to format and reinstall from scratch.

Exactly, I have tried the ERD repair several times, but other things always crop up, and it simply doesn't work. Only tape restores will do. The repair option in NT's setup craps out as well.
One of the problems that cause this is that I have Service Packs on the system that NT's original CD files overwrite, thus making a mess of the system files. Reinstalling the Service Packs again sounds good on paper, but no go...
I would be interested in feedback on someone who has had any success in a repair.

yup, same here. had BackOffice 4.5 go down after applying a "security patch", upon rebooting got the bsod with ntoskrnl.exe referenced. no erd could be used, it was complaining that line 1020 was corrupt and could not be restored...whole new install in process as i type. pos.

c-

Same again.

If do not have a incremential tape backup ,
no chance .

Start formatting and setting up right now,
the shortest way is the way that is for sure!

NTLDR Was missing so I rebooted with the
EMERGENCY BOOT DISK now NTOSKRNL.EXE IS MISSING OR CORRUPT The path is winnt\system32
\ntoskrnl.exe, this file is 1.6MB.
HOW CAN I RESTORE THIS FILE.
PLEASE HELP

FRANK

I'm no genius but I had a problem similar to yours. After installing a 3rd OS (ME/2000/XP - tri boot!) on my computer I was no longer able to boot Windows 2000. I got the exact same message NTOSKRNL.EXE corrupted etc.. The problem was found in the Master Boot Record ((root)C:\boot.ini). I found that XP changed my 2000 boot partition from multi(0)...(0)...(0)...(2) to multi(0)...(0)...(0)...(1), which was the cause of the problem. There was no bootable partition there.

This may not help but maybe check the MBR to make sure it hasn't rewritten the boot partition to boot something that doesn't exist.

I should add, I was still able to access my so-called corrupted file (through XP). It was untouched, unmodified, and otherwise completely intact.

My corrected MBR:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS

[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /fastdetect

multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Professional" /fastdetect

C:\ = "Microsoft Windows ME"

I have a new computer with XP and it will not load as it says there is a problem with

NTOSKRNL.EXE

and it still shows if I use a CD recovery or Starp-up disks.

How to I get into the system to reset it all?

Help

Thanks

Had this problem just yesterday.

Found that re applying WinXp (upgrade option) and resetting the cmos solved the problem.

Fairly simple, but an annoying headache at first :)

I like orange juice.