Time to Reimage or new System?

[cooldude832]

I keep getting the error of c00021a fatal system error

which cause me to shut the comptuer down for 5-10 minutes then insert my vista install disk and run the repair and restart causing me 20-30 minutes of down time.


The error seems to trigger at high memory usage usually when I play games like CS:s and it makes the game ice up and not load after 10-20 minutes.


I've reviwed c00021a fatal system error but I can't make heads or tails of it

So my question is:

A) Will a reimage completely cleaning off the hard drive solve this
B) If so how do I do it from a vista upgrade disk

C) Should I just get a new system (AMD 939 3800+ 2gb ddr400) that is a e8400 or q6600 system for a few hundred?

D) Alternative solutions


The system runs fine when i'm just internet surfing/iming etc but as soon as I load a game it goes crazy and its not just CS:s any game or high memory usage (photoshop) just trashes the system.

If you have any questions let me know

 

[garysgold]

Hello cooldude832,

Welcome to the forums. Very difficult to say if you should get a new system if we have no idea what you have now or what your thinking of getting 'for a few hundred'. If you go to your userCP and fill in as much of your system specs as you can, that will help a lot. Also you won't have to give that info whenever you have a problem because it will become part of your posts.

I'm not a gamer, but the first thing I would do is run a system file check. Info here if needed. http://www.vistax64.com/tutorials/66978-system-files-sfc-command.html

Also is this a new problem? Did it start after installing some new app? If so you could try a system restore. http://www.vistax64.com/tutorials/76905-system-restore-how.html

Please keep us posted.

Gary

 

[cooldude832]

give me 5 minutes to get it up I just recoevered from it going down again.

 

[cooldude832]

Okay so it crashed while running the scan got back up and the error I got comming back says

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

Additional information about the problem:
  BCCode:    c000021a
  BCP1:    FFFFF880005C3C20
  BCP2:    0000000000000000
  BCP3:    FFFFFFFFC0000001
  BCP4:    00000000001004D8
  OS Version:    6_0_6001
  Service Pack:    1_0
  Product:    768_1

Files that help describe the problem:
  C:\Windows\Minidump\Mini120808-01.dmp
  C:\Users\John\AppData\Local\Temp\WER-42390-0.sysdata.xml
  C:\Users\John\AppData\Local\Temp\WER3BBC.tmp.version.txt

Read our privacy statement:
  http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409

The error has happened randomly since I got a new memory module (they are matched just bought at different times) and now its to the point I can't do much on this computer.

 

[cooldude832]

here is the sfc log printed

2008-12-08 23:11:28, Info                  CSI    00000006 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:11:28, Info                  CSI    00000007 [SR] Beginning Verify and Repair transaction
2008-12-08 23:11:30, Info                  CSI    00000009 [SR] Verify complete
2008-12-08 23:11:30, Info                  CSI    0000000a [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:11:30, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2008-12-08 23:11:32, Info                  CSI    0000000d [SR] Verify complete
2008-12-08 23:11:32, Info                  CSI    0000000e [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:11:32, Info                  CSI    0000000f [SR] Beginning Verify and Repair transaction
2008-12-08 23:11:40, Info                  CSI    00000011 [SR] Verify complete
2008-12-08 23:11:41, Info                  CSI    00000012 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:11:41, Info                  CSI    00000013 [SR] Beginning Verify and Repair transaction
2008-12-08 23:11:45, Info                  CSI    00000015 [SR] Verify complete
2008-12-08 23:11:46, Info                  CSI    00000016 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:11:46, Info                  CSI    00000017 [SR] Beginning Verify and Repair transaction
2008-12-08 23:12:01, Info                  CSI    00000019 [SR] Verify complete
2008-12-08 23:12:02, Info                  CSI    0000001a [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:12:02, Info                  CSI    0000001b [SR] Beginning Verify and Repair transaction
2008-12-08 23:12:06, Info                  CSI    0000001d [SR] Verify complete
2008-12-08 23:12:08, Info                  CSI    0000001e [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:12:08, Info                  CSI    0000001f [SR] Beginning Verify and Repair transaction
2008-12-08 23:12:17, Info                  CSI    00000021 [SR] Verify complete
2008-12-08 23:12:18, Info                  CSI    00000022 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:12:18, Info                  CSI    00000023 [SR] Beginning Verify and Repair transaction
2008-12-08 23:12:25, Info                  CSI    00000025 [SR] Verify complete
2008-12-08 23:12:25, Info                  CSI    00000026 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:12:25, Info                  CSI    00000027 [SR] Beginning Verify and Repair transaction
2008-12-08 23:12:33, Info                  CSI    00000029 [SR] Verify complete
2008-12-08 23:12:34, Info                  CSI    0000002a [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:12:34, Info                  CSI    0000002b [SR] Beginning Verify and Repair transaction
2008-12-08 23:12:43, Info                  CSI    00000030 [SR] Verify complete
2008-12-08 23:12:44, Info                  CSI    00000031 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:12:44, Info                  CSI    00000032 [SR] Beginning Verify and Repair transaction
2008-12-08 23:12:56, Info                  CSI    00000034 [SR] Verify complete
2008-12-08 23:12:57, Info                  CSI    00000035 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:12:57, Info                  CSI    00000036 [SR] Beginning Verify and Repair transaction
2008-12-08 23:13:03, Info                  CSI    0000003a [SR] Verify complete
2008-12-08 23:13:03, Info                  CSI    0000003b [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:13:03, Info                  CSI    0000003c [SR] Beginning Verify and Repair transaction
2008-12-08 23:13:11, Info                  CSI    00000047 [SR] Verify complete
2008-12-08 23:13:12, Info                  CSI    00000048 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:13:12, Info                  CSI    00000049 [SR] Beginning Verify and Repair transaction
2008-12-08 23:13:23, Info                  CSI    00000065 [SR] Verify complete
2008-12-08 23:13:23, Info                  CSI    00000066 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:13:23, Info                  CSI    00000067 [SR] Beginning Verify and Repair transaction
2008-12-08 23:13:31, Info                  CSI    00000069 [SR] Verify complete
2008-12-08 23:13:31, Info                  CSI    0000006a [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:13:31, Info                  CSI    0000006b [SR] Beginning Verify and Repair transaction
2008-12-08 23:13:37, Info                  CSI    0000006d [SR] Verify complete
2008-12-08 23:13:37, Info                  CSI    0000006e [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:13:37, Info                  CSI    0000006f [SR] Beginning Verify and Repair transaction
2008-12-08 23:13:44, Info                  CSI    00000071 [SR] Verify complete
2008-12-08 23:13:45, Info                  CSI    00000072 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:13:45, Info                  CSI    00000073 [SR] Beginning Verify and Repair transaction
2008-12-08 23:13:58, Info                  CSI    0000008b [SR] Verify complete
2008-12-08 23:13:59, Info                  CSI    0000008c [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:13:59, Info                  CSI    0000008d [SR] Beginning Verify and Repair transaction
2008-12-08 23:14:22, Info                  CSI    0000008f [SR] Verify complete
2008-12-08 23:14:23, Info                  CSI    00000090 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:14:23, Info                  CSI    00000091 [SR] Beginning Verify and Repair transaction
2008-12-08 23:14:45, Info                  CSI    00000093 [SR] Verify complete
2008-12-08 23:14:45, Info                  CSI    00000094 [SR] Verifying 100 (0x0000000000000064) components
2008-12-08 23:14:45, Info                  CSI    00000095 [SR] Beginning Verify and Repair transaction

 

[Dzomlija]

Directly from Microsoft (Bug Check 0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED):

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 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.

If mentions newly installed hardware, which in your case may very well be that new memory module you installed...

 

[cooldude832]

Well the memory install was over 6 months ago

 

[garysgold]

Doesn't seem that it should be 6 months before a problem develops. Still I'd try taking the new stick out and see what happens. I've read that they should be purchased in pairs to assure that they are matched.

Gary