• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7421
  • Last Modified:

Error: STOP c000021a -status 0x00000080

Windows NT 4.0 SP3 - BSOD (Blue Screen of Death)
Occurs after loading of drivers.  Occurs exactly 1 second
after the regular (aqua color-background for desktop)
comes up... it comes after Bootloader, after kernal and HAL
and after ndetect.com, just after CSR Subsytem begins.
and right as or before LSASS is about to appear.

BSOD Windows Logon Process system process terminated unexpectedly with a status of 0x00000080 (0x0000000 0x00000000).

Beginning Dump of physical memory

HELP!!!!!  CD-ROM is in storage!!  No repair disk...
What does the c000021a and the 0x00000080 mean ? Are those
specific addresses in code, or are they error codes ?

I want to isolate the file or cause of this and feel I may
be able to change a file and get it to reboot,  since it already goes so far through the boot up process.  Any ideas?


1 Solution
This article may answer your question

PSS ID Number: Q163874
Article last modified on 09-03-1997
PSS database name: WINNT

The information in this article applies to:
 - Microsoft Windows NT Workstation version 4.0
 - Microsoft Windows NT Server version 4.0
If Client Services for NetWare (CSNW) is installed and a user presses the
CTRL+ALT+DEL key sequence immediately after entering his or her password at
the logon prompt, the system halts with a C000021A STOP code.
It is by design within Windows NT that, if the Secure Attention Sequence
(SAS) (CTRL+ALT+DEL) is pressed, any logon scripts currently running are
terminated. This gives the user the ability to easily kill any logon
scripts that may have stopped responding. However, if this sequence is
pressed before a process running a logon script has started running
properly, a blue screen STOP error can result. This error is caused because
Winlogon.exe performs an access violation.
NOTE: The user does not have to have a logon script defined for this
problem to occur. With CSNW, the logon script processor is responsible for
checking to see if a logon script is actually available to run and,
therefore, is started even if no script is defined.
There is a fix available from Microsoft Technical Support that fixes this
Microsoft has confirmed this to be a problem in Windows NT version 4.0.
This problem was corrected in the latest Microsoft Windows NT 4.0 U.S.
Pack. For information on obtaining the service pack, query on the following
in the Microsoft Knowledge Base (without the spaces):
   S E R V P A C K
Additional query words:
Keywords          : kbbug4.00 kbfix4.00 kbfix4.00.sp3 NTSrvWkst kbbuglist kbfixlist
Version           : 4.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbservicepack
Copyright Microsoft Corporation 1997.


research2Author Commented:
There was some confusion on shutdown and this may be the right answer.  However,  Does anyone know what the "status of
0x00000080" means ?   I'm trying to isolate the exact line
item in a boot up file or other system file that causes the
BSOD.  My hope is that I can edit the "list" of things the
computer is doing on startup,  in order to locate the piece of
data or line item that is causing this.  I'm hoping that once I
can do this,  I can edit the file that hasa the wrong flag or
phrase and then try to reboot.  I cannot install the fixes,
until I can get to a NT command windows,  is that right ?

In other words, can the fix be applied simply by copying over
certain files to the NT (16bit) boot partition (winnt or system32
sub directory or system directory) and then rebooting WITHOUT
having to boot into NT first.  Right now, I am using a WIN 95 disk to boot up to the first non-ntfs drive.  The NTFS drive is
inaccessable,  even though most everything loads up, right before
the BSOD happens... thanks!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now