The System can not log you on (C00000DF)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Paul fpvt2 - 08 Nov 2004 20:49 GMT

This morning when we rebooted our NT 4.0 server, we got the blue screen with
error "Stop 0xC000021A (Fatal System Error)
The Windows Logon Process system process terminated unexpectedly
with a state of 0x00000080 (0x00000000, 0x00000000).
The system has been shut down."
As far as we know, we did not install any Service Pack on this computer.

So, we repaired the server using Emergency Repair Disk that was created from
another NT server. During the repair it gave us a few error like "the
following file is either corrupted or missing: REGSVR32.EXE". Other files
with the error is: COMCAT.DLL, etc.
We hit ESC on all these errors to skip it. Finally we saw the NT logon
screen, and when we tried to login, we got a message "The System can not log
you on (C00000DF). Please try again or consult your system administrator."

What can we do to fix this problem ?

Thank you very much.

Reply to this Message

Karl-Stephan Werkmeister - 09 Nov 2004 20:06 GMT

> [...]
> So, we repaired the server using Emergency Repair Disk that was created from
> another NT server.
>[...]
> Finally we saw the NT logon screen, and when we tried to login, we got a message "The System can not log
> you on (C00000DF). Please try again or consult your system administrator."

See:
http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&query=c0000
0df&x=19&y=11
especially:
http://support.microsoft.com/default.aspx?scid=kb;en-us;196603

In short word:
changes that happened from Service Pack to Service Pack result often in
ERD cause more problems than it solves.
Most likely your system will run again after you have replaced the
mismatching files as described in the MS articles.

Concerning your first trouble [STOP 0xC000021A" error]
(http://support.microsoft.com/kb/156669/EN-US/):
I saw seen this once myself on an NT4WS but the error had not been too
fatal. The system booted and the logon procedure was often successful
(BSOD appeared not before the 2nd or 3rd logon).
A service that should handle a SCSI controller (scanner) was to blame
(maybe because the controller card itself was no longer present).
Deactivating this service was all to be done to eliminate this BSODs.

Stephan

Reply to this Message

Scott Harding - MS MVP - 10 Nov 2004 17:19 GMT

This should help. Never use an ERD from another system and never use an old
ERD. They typically make the system worse and non bootable.

http://support.microsoft.com/default.aspx?scid=kb;en-us;307866

Signature

Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

> > [...]
> > So, we repaired the server using Emergency Repair Disk that was created from
[quoted text clipped - 4 lines]
>
> See:

http://support.microsoft.com/search/default.aspx?catalog=LCID%3D1033&query=c0000
0df&x=19&y=11

> especially:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;196603
[quoted text clipped - 15 lines]
>
> Stephan

Reply to this Message