Receiving error Stop: c000021a

[Khalith]

I am receiving this message seemingly at random on my laptop, the screen goes black and the screen randomly shuts down then when I turn the laptop back on it turns off.

I checked previous threads but all of them are about windows XP whereas I am using Vista Basic. I tried using the last good settings when I booted the computer, tried a system restore from past windows updates, did ALL windows updates and still have the issue, did a scandisk in DOS but everything was fine, and tried a system repair, nothing is working.

I do not have the vista reinstall disc.

Here's the report of it:

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033

Files that help describe the problem (some files may no longer be available)
Mini123109-01.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: c000021a
BCP1: FFFFF88000B4A160
BCP2: 0000000000000000
BCP3: FFFFFFFFC0000001
BCP4: 0000000000100558
OS Version: 6_0_6002
Service Pack: 2_0
Product: 768_1
Server information: e0dfceb9-d769-4e21-8149-407d957a64eb

Any help would be greatly appreciated, this problem is driving me nuts.

In Control Panel choose Problem Reports and Solutions (type problem in
Start's searchbox), go to Problem History, right click your error and choose
Check For Solution. You can also examine the details.

In Administrative Tools choose Reliability and Performance Monitor and
choose MonitoringTools then Reliability Monitor (type Reliability in search
on Start) . This list is a chart of software installs, uninstalls, Windows
updates, and crashes by date. See if your crashes started happening after
you installed or uninstalled something.

You may wish to do clean boot
troubleshooting http://support.microsoft.com/kb/331796

===============================================
// MessageId: STATUS_SYSTEM_PROCESS_TERMINATED
//-------------------------------------------------------------------------------
// MessageText:
//
// {Fatal System Error}
// The %hs system process terminated unexpectedly with a status of 0x%08x
(0x%08x 0x%08x).
// The system has been shut down.
//
#define STATUS_SYSTEM_PROCESS_TERMINATED ((NTSTATUS)0xC000021AL)

From NTStatus.h

========================================================
Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
------------------------------------------------------------------------------------------------
The STATUS_SYSTEM_PROCESS_TERMINATED bug check has a value of 0xC000021A.
This means that an error has occurred in a crucial user-mode subsystem.

Parameters
The following parameters are displayed on the blue screen.

Parameter Description
1 A string that identifies the problem
2 The error code
3 Reserved
4 Reserved
Cause
This error occurs when a user-mode subsystem, such as WinLogon or the Client
Server Run-Time Subsystem (CSRSS), has been fatally compromised and security
can no longer be guaranteed. In response, the operating system switches to
kernel mode. Microsoft Windows cannot run without WinLogon or CSRSS.
Therefore, this is one of the few cases where the failure of a user-mode
service can shut down the system.

Mismatched system files can also cause this error. This can occur if you
have restored your hard disk from a backup. Some backup programs might skip
restoring system files that they determine are in use.

Resolving the Problem
Running the kernel debugger is not useful in this situation because the
actual error occurred in a user-mode process.

Resolving an error in a user-mode device driver, system service, or
third-party application: Because bug check 0xC000021A occurs in a user-mode
process, the most common culprits are third-party applications. If the error
occurred after the installation of a new or updated device driver, system
service, or third-party application, the new software should be removed or
disabled. Contact the manufacturer of the software about a possible update.

If the error occurs during system startup, restart your computer, and press
F8 at the character-based menu that displays the operating system choices.
At the resulting Windows Advanced Options menu, choose the Last Known Good
Configuration option. This option is most effective when only one driver or
service is added at a time. If this does not resolve the error, try manually
removing the offending software. If the system partition is formatted with
file allocation table (FAT), use an MS-DOS startup disk to gain access to
the computer's hard disk. If the system partition is formatted with NTFS
file system, you might be able to use Safe Mode to rename or delete the
faulty software. If the faulty software is used as part of the system
startup process in Safe Mode, you need to start the computer using the
Recovery Console in order to access the file. If a newly installed piece if
hardware is suspected, remove it to see if this resolves the issue.

Try running the Emergency Recovery Disk (ERD) and allow the system to repair
any errors that it detects.

Resolving a mismatched system file problem: If you have recently restored
your hard disk from a backup, check if there is an updated version of the
Backup/Restore program available from the manufacturer. Make sure the latest
Windows Service Pack is installed.

[Khalith]

The clean boot was not for the version of windows I am using, I'm not sure if it would still work. Thank you for the response, I checked the Reliability Monitor for yesterday when the problem got really bad.

Here's what popped up:

Failure Type Failure Detail Date
Boot Failure 6.0.6002 Service Pack 2 Not Applicable 12/30/2009
Boot Failure 6.0.6002 Service Pack 2 Not Applicable 12/30/2009
Boot Failure 6.0.6002 Service Pack 2 Not Applicable 12/30/2009
Boot Failure 6.0.6002 Service Pack 2 Not Applicable 12/30/2009
Boot Failure 6.0.6002 Service Pack 2 Not Applicable 12/30/2009
OS Stopped working 6.0.6002 Service Pack 2 0xc000021a (0xfffff880000a3ea0, 0x0000000000000000, 0xffffffffc 12/30/2009
OS Stopped working 6.0.6002 Service Pack 2 0xc000021a (0xfffff880005eb070, 0x0000000000000000, 0xffffffffc 12/30/2009
OS Stopped working 6.0.6002 Service Pack 2 0xc000021a (0xfffff880009d6df0, 0x0000000000000000, 0xffffffffc 12/30/2009
OS Stopped working 6.0.6002 Service Pack 2 0xc000021a (0xfffff88001404bf0, 0x0000000000000000, 0xffffffffc 12/30/2009
OS Stopped working 6.0.6002 Service Pack 2 0xc000021a (0xfffff880076a8c30, 0x0000000000000000, 0xffffffffc 12/30/2009

Not sure what to make of it.

Any differences in clean boot troubleshooting is minimal. The steps listed
require Vista or Win 7 (and with changing one word applies to any windows
since 98). It tells me it doesn't apply as well - it is confused.

In reliability find the first occurence of the 0xc000021a error (which
appears to be the 30th) and look for software installs or uninstalls just
prior to that date. As you crash several times a day I'd look at the 29th
and the 30th.

What were you doing with Service Pack 2 - trying to fix the error or
something else?

[Khalith]

The service pack 2 was a recent windows update, that's all.

The problem has been going on for months and months and it suddenly escalated.

I did a system restore and put the machine back to it's factory defaults with absolutely nothing on it at all.

I've narrowed it down however to what program is causing it, it seems to happen mostly (as in 99% of the time) when I am running world of warcraft which is odd as I have been running it for literally months and months upon end without any issues until this problem started a few months ago.

The error code on the blue screen I am getting is (0x0000000000 00000002700f) or something to that degree.

Could it be a problem with the game overloading or messing with something? A friend of mine that reported a similar issue thinks I might just need more RAM but I am not sure about that. But since I did just restore the system to it's factory defaults let me redo all my windows updates as one person that reported the error got that as the cause.

But I highly doubt that will fix it.

Edit: After the new year the records of ALL previous crashes on the reliability thing were erased with no way to recover them. I'll try the clean boot and see what happens after doing all my windows updates.

Double edit: Whenever I get the error, nothing that I have downloaded is left on the computer. I downloaded firefox and AVG and then while trying to reinstall Warcraft the system crashed, when I got back firefox and AVG were gone.

It may help to rule out hardware faults

Type memory in Start's search box and choose Memory Diagnostic

In a command prompt (type command in Start's search box then right click and
choose Run As Administrator) type

chkdsk c: /r

If you have more than one drive replace C: with the other drive letter.

It is unlikely that not enough ram will cause crashes.

[Khalith]

Alright, I did a memory scan with both of my ram cards, a 1 gig and a 2 gig, I scanned both, the 1 gig caused the crash, the second ram card wouldn't even boot the laptop, after looking at both cards I noticed that both were made by different companies.'

It looks like I may need to replace both ram cards and hope for the best.

Sorry to hear that.

--
..
--
"Khalith" <Khalith.445bvc@DoNotSpam.com> wrote in message
news:Khalith.445bvc@DoNotSpam.com...
>
> Alright, I did a memory scan with both of my ram cards, a 1 gig and a 2
> gig, I scanned both, the 1 gig caused the crash, the second ram card
> wouldn't even boot the laptop, after looking at both cards I noticed
> that both were made by different companies.'
>
> It looks like I may need to replace both ram cards and hope for the
> best.
>
>
> --
> Khalith
> ------------------------------------------------------------------------
> Khalith's Profile: http://forums.techarena.in/members/169287.htm
> View this thread: Receiving error Stop: c000021a
>
> http://forums.techarena.in
>