| |
|
 |
| |
|
|
| |
|
| |
Description |
|
| |
|
|
| |
Security has been breached by a bug in an application, device driver, or improper system file restoration.
On some versions of Windows, this error may appear as "WINLOGON_FATAL_ERROR". This is a fatal Windows error, typically called a Stop message, Bug Check, or more commonly the Blue Screen of Death (BSoD). The system is in a forced reboot state. Any unsaved work is likely lost.
|
|
| |
|
|
| |
Sample Screen |
|
| |
|
|
| |
|
A problem has been detected and Windows has been shut down to prevent damage to your computer.
STATUS_SYSTEM_PROCESS_TERMINATED Technical Information:
*** STOP: 0xC000021A
Beginning dump of physical memory
Physical memory dump complete.
Contact your system administrator or technical support group for further
assistance. |
|
|
| |
Text may appear differently depending on where the error occurs.
Additional technical information (hex values) specific to a machine are not shown. |
|
| |
|
|
| |
Key Facts |
|
| |
|
|
| |
Full Title |
|
STATUS_SYSTEM_PROCESS_TERMINATED
|
Stop Code |
|
0xC000021A
|
Type |
|
Fatal
|
|
Windows |
|
XP, Vista, 2008, 7, 8
|
Vendor |
|
Microsoft Corporation |
|
|
| |
|
|
| |
Solutions and Fixes |
|
| |
|
|
| |
|
Check if this software bug applies to your system: An incompatible version of GoBack (included with Symantec System Works) will cause this issue. It will be necessary to remove this version of GoBack. See Microsoft article 316503 for instructions to disable and remove GoBack.
Older versions of Internet Explorer version 6 can cause this issue. Apply the latest updates to IE6 or upgrade to the current version of IE (Microsoft article 318666). |
| |
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
|
Use Last Known Good Configuration |
|
|
If you are unable successfully boot into Windows because of the fatal error, Windows has an option to reload registry information from the last successful boot. To revert to the last successful boot:
- Reboot the computer.
- Near the end of the BIOS messages or graphic, but well before anything appears from Windows, press the F8 key. You may only have a few seconds to get the right spot to press F8 before it attempts to go into Windows. If the BIOS complains about a pressed key or asks you to go into BIOS setup, you've pressed F8 too soon (Don't go into BIOS setup).
- When successful, you should see a black screen with white text "Windows Advanced Options". Use the up or down arrow keys to highlight Last Known Good Configuration and press Enter.
|
| |
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
|
Check if you are using the latest hardware drivers, especially the chipset and video drivers. Older drivers are a common contributor to BSoD issues.
You can use a product like Driver Genius or Radar Sync to verify you have the latest drivers and help keep all your drivers up-to-date. If you're comfortable with driver installations, you can individually find and install current drivers.
A some of the most popular driver download sites:
|
| |
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
|
Uninstall the Last Install |
|
|
If you can get the system up for more than a few minutes or can use safe mode, try removing the last installed software application or driver.
For removal of an application (Windows 8+)
- Press the Windows Key and X together, then Control Panel, then Programs and Features.
- Select the software to uninstall and select Uninstall.
For removal of an application (Windows 7 & Vista):
- Click on Start, Control Panel, then Programs and Features.
- Select the software to uninstall and select Uninstall.
For removal of an application (Windows XP):
- Click on Start, Control Panel, then Add or Remove Programs.
- Select the software to uninstall and select Remove.
To disable a driver:
- Bring up the system information dialog:
On the keyboard, press the Windows key + Pause/Break.
or
Select Start, right click Computer and on the drop-down, select Properties.
- Click on the left side option Advanced system settings (7/Vista only).
- In System Properties, select the Hardware tab, then click on Device Manager button.
- Find the hardware/driver of interest (you may need to expand a choice at the "plus" graphic) and double click the choice.
- Select the Driver tab. Here you can perform a number of actions such as update the driver, roll Back the driver to an older version, disable or uninstall the driver.
- Click OK to exit, then close the Device Manager and other previously opened dialogs.
|
| |
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
|
Fix Improper File Restore |
|
|
If you just restored from a backup, the backup may have failed to save key system files that were in use at the time of the backup. As a result, the restoration would restore some system files, but not others. This can cause different versions and/or a failure to repair some damaged system files.
This is a bit of a mess, and not easily solved. If you have a another complete backup, you might try it. You might also try using the Recovery Console to restore system files. |
| |
|
|
FaultWire Staff
Posted: 2-Sep-2009 |
|
|
|
Restore From Backup or Image |
|
|
If you know the hardware is good and you have a current backup or image of the drive, you could reformat the hard drive and start over. This is often the last resort when all else fails, as you will often lose your latest settings and important data. If you have a spare drive, it may be worth it to install the drive in place of the first drive and do a fresh install of Windows. This will help confirm if this is a hardware or software issue (unless the original system drive is the source of the problem). |
| |
|
|
FaultWire Staff
Posted: 5-Oct-2008 |
|
|
Also see our list of common Fatal Error Solutions. |
|
| |
|
|
| |
Forum Help |
|
| |
|
|
| |
 |
Check out what others say about this issue and review or add your own comments and solutions!
Go to Forums on topic. |
|
|
| |
|
|
| |
Technical Details |
|
| |
|
|
| |
| |
 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. The operating system switches to kernel mode since Windows cannot run without WinLogon or CSRSS causing this fatal error.
After the Stop code will be 4 hex values: {Parameter 1, Parameter 2, Parameter 3, Parameter 4}.
Parameter 1 specifies a string that identifies the problem.
Parameter 2 specifies the error code.
Parameter 3 is not defined.
Parameter 4 is not defined.
|
|
|
| |
|
|
| |
Vendor Summary |
|
| |
|
|
| |
|
|
| |
|
|
| |
|
While BSoD fatal stop errors are identified by Microsoft Windows, they are often caused by
non-Microsoft applications, drivers and hardware issues. |
|
| |
|
|
| |
Research this Issue |
|
| |
|
|
| |
Getting search results...
|
|
| |
|
|
| |
Notes |
|
| |
|
|
| |
While we believe this information up to date and accurate, FAQware is not responsible for any inaccuracies. If you find something that is out of date or inaccurate, please let us know at
so we can correct it. |
|
| |
|
|
|
|
 |
 |
 |
| | |
|
|
