c000021a (fatal system error)

Hello There


Have you installed roxio goback??

PeteL

The user claims that they have installed no new software.

ebeheler,
This error can be caused by roxio goback see Q316503

http://support.microsoft.com/?kbid=316503

ebeheler,

If not

see https://www.experts-exchange.com/questions/20681890/XP-STOP-error-c000021a.html

PeteLong,

Thanks, I've checked the Microsoft KB, and haven't found an applicable article there.

Other suggestions?

ebeheler,
did you try http://support.microsoft.com/?kbid=318666

Do you have an ERD? If so, do a repair
Else take a look here, similar problem
https://www.experts-exchange.com/questions/20681890/XP-STOP-error-c000021a.html

I don't have an ERD for this system, but I may be able to create one from an identical system.

ebeheler,
Iff you fancy some detective work go here

http://aumha.org/win5/kbestop.htm

PeteLong,

Wow, interesting website.  Lots of information here, but doesn't appear to offer any solutions that I didn't already find in the Microsoft KB.  Bookmarked it though.

Try replacing the RAM.  That error number is typical of bad RAM.

Hmm I have been trying to help someone else through this error message in this topic: https://www.experts-exchange.com/questions/20714320/XP-reboots-after-admin-password-entry.html

Sounds similar and I have tried similar suggestions..

dew_associates,

You may be on the right track.  I booted into the recovery console and started chkdsk /r.  It got to 51% pretty quickly, within perhaps a minute.  It then slowed way down, maybe 1% every 2 minutes.  I thought it had locked up at first.

I left the system when it got to 60% and will check on it in the morning.  It might end up being a dead HDD.

I thought I would post the exact text of the BSOD, as I wrote it down (instead of how the user read it to me).

STOP: c0000021A {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a status of 0x00000407 (0x00000000 0x00000000).
The system has been shut down.

Okay, but let chkdsk run. If there are a lot of files on the drive, or it is fragmented, this will take time.

looking at the complete error, maybe using recovery console to repair/replace winlogon might help. I've done this once before, but can't find an url regarging more info at the moment.

chkdsk finished, found some errors and fixed them.  The system would then boot and let me log in, but double-clicking on most icons didn't do anything.  While troubleshooting, I rebooted the system and during the reboot, the drive gave a SMART error, indicating that the hard drive was dying.  Problem found!

Thanks for your help.

Anytime!  If you need more, let me know.

I just had this error booting into safemode on a XP Pro box. Booting into normal mode gives an out of system resource error and no Login options, just reboots. The error message states lsass.exe could not start. Upon starting up with a DOS/Win98 bootup disk, I found the culprit. The user saved too much data...drive shows 0.018MB of free space....deleted some files and presto, system works fine.

Sometimes the easiest steps are often overlooked! Even I made that mistake at first.