corrupt ntdll.dll. any option besides reinstallation?

[imhotepmp]

keep getting stop error codes c0000221
I looked up that code here: http://www.labmice.net/troubleshooting/errorcodes.htm

and found out that I have a corrupt ntdll.dll file. Ive tried boting into safe mode and replacing it but it wont let me because win2k is using the file. what should i do? both my partitions are ntfs, so theres no way i can access via win98 bootdisk. I've seen programs whihc allow you to access ntfs from fat, but theyre ridicolously expensive. Is there anyway I can get back into my system?

thanks for any feedback anyone can give me.

btw the odd thing is that even though i used to get these errors, after enought tries, it would let me in. Now I cant get in at all.

imhotepMP

 

[BadThad]

hummm....not sure about win2k, but in NT you can start the install from the CD and select REPAIR. I've repaired a bunch of NT4 systems using this. Just be careful what you select in the repair or you'll have to reinstall all your apps...NOT for novices. It's really helpful if you have an ERD for the system.

 

[jaywallen]

I guess you've already tried this, but you didn't say so specifically. Can you boot into Recovery Console? (If it's not installed on the hard drive, you can boot into it on the install CD.) You will have access to your NTFS partitions. You'll have to replace the NTDLL.DLL file with a copy from one of several possible sources.

It's in the \i386\system32 directory on the W2K setup CD. (This is the old, pre-SP1 version -- 5.0.2163.1.)

It's in the \i386 directory on the W2K SP1 CD. (version 5.0.2195.1600)

I fear that this may not be your only problem, however. WFP should have protected that file, unless it has been turned off, or unless something else is going on. There should be a good copy of it in the dllcache.

If you're able to recover, I'd suggest running "SFC /SCANNOW" on the W2K installation(s) to try to head off further problems. And maybe running a very careful virus check. (I suppose a virus could be involved, though I haven't heard of one that works in just this way.)

I hope you'll be able to sort this out.

Regards,
Jim

 

[imhotepmp]

jim

yea i tried to replace it in the recovery console. The replaced file was form the cd and was successful. However after reboot the error remained. I can rule out that the file fom the cd was bad, because I just recently used for an intsall at my apartment and that computer is running without a hiccup.



<< And maybe running a very careful virus check. (I suppose a virus could be involved, though I haven't heard of one that works in just this way.) >>



Used inocultate IT and nothing came up



<< that this may not be your only problem, however. WFP should have protected that file, unless it has been turned off, or unless something else is going on. There should be a good copy of it in the dllcache. >>



I agree. Previously, I would get other stop errors, but until last night it hasnt consistently been the corrupt dll.

I have one more idea than I think I'm just goign to reinstall. btw could bad hardware cause this? I ask this because I can boot into safe mode, but if i try to boot into safe mode w/ networking I get the stop error? So i think im going to try and take out the card(which shoudl of been the first thing I did)

thanks for everyone's reply

will update in a few hours

UPDATE
I tried to install win2k server, but I still get the same [remove]server[/remove]...errr... error.

can anyone offer me some assistance?


imhotepMP

 

[Poof]

What's the hardware you're trying to install it on? It could be the CDROM drive isn't reading the CD correctly and or there's something screwy with the drive controller...

 

[jaywallen]

imhotepmp,

Dang, this is weird. I can't imagine that bad hardware would cause this sort of behavior. Even if it did, I'd expect you to be seeing other errors. I'm gonna go hunting for this. I will definitely get back to you if I find something.

Regards,
Jim

 

[imhotepmp]

<< What's the hardware you're trying to install it on? It could be the CDROM drive isn't reading the CD correctly and or there's something screwy with the drive controller >>



good idea...I thought of that as well.....
but right now im trying to eliminate the hd as the culprit so Im installing it on a different hd. If this dowsnt work Ill try it on another computer completely. Also if it was the cdrom/and or controller why would it always be the same exact file that has the error? something to think about...

Jim
thanks for the effort

thanks


imhotepMP