Bug Check 0xC000021A: WINLOGON_FATAL_ERROR

The WINLOGON_FATAL_ERROR bug check has a value of 0xC000021A. This means that that the Winlogon process terminated unexpectedly.

This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

WINLOGON_FATAL_ERROR Parameters

A string that identifies the problem

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

Resolution

Running the kernel debugger may not be 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 to isolate the cause. Contact the manufacturer of the software about a possible update.

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.

Look at the most recently installed applications. To do this navigate to «Uninstall or change a program» in control panel and sort the installed applications by install date.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. For more information, see Open Event Viewer. Look for critical errors in the system log that occurred in the same time window as the blue screen.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing the error. Look for critical errors in the system log that occurred in the same time window as the blue screen.

Remarks

Use the System File Checker tool to repair missing or corrupted system files. The System File Checker is a utility in Windows that allows users to scan for corruptions in Windows system files and restore corrupted files. Use the following command to run the System File Checker tool (SFC.exe).

Run a virus detection program. Viruses can infect all types of hard disks that are formatted for Windows, and the resulting disk corruption can generate system bug check codes. Make sure the virus detection program checks the Master Boot Record for infections.

Verify that the system has the latest updates installed. To detect which version is installed on your system, select Start, select Run, type winver, and then press ENTER. The About Windows dialog box displays the Windows version number (and the version number of the service pack, if one is installed).

Using Safe Mode

Consider using Safe Mode to isolate elements for troubleshooting and, if necessary, to use Windows. Using Safe Mode loads only the minimum required drivers and system services during the Windows startup.

To enter Safe Mode, use Update and Security in Settings. Select RecoveryВ > Advanced startup to boot to maintenance mode. At the resulting menu, choose TroubleshootВ > Advanced OptionsВ > Startup SettingsВ > Restart. After Windows restarts and displays the Startup Settings screen, select option 4, 5, or 6 to boot to Safe Mode.

Safe Mode may also be available by pressing a function key on boot, for example F8. Refer to information from the computer’s manufacturer for specific startup options.

Operating system failure windows bug check stop

Вопрос

We are getting intermittent BSOD failures on a number of servers running Server 2012 R2. The BSOD stop check message all read Windows bug check, STOP: 0x0000001E (0xFFFFFFFFC0000005, 0xFFFFF8012767F8AD, 0x0000000000000000, 0x0000000000000008)

We have tried various fixes for this with little or no success from disabling SMB v1 & v2 and disabling TCP offloading as suggested on other forums

Can anybody help guide me to a potential fix for this

Все ответы

The KMODE_EXCEPTION_NOT_HANDLED bug check has a value of 0x0000001E. This indicates that a kernel-mode program generated an exception which the error handler did not catch.

To evaluate the BSOD please post logs for troubleshooting.

Using administrative command prompt copy and paste this whole command.

Make sure the default language is English so that the logs can be scanned and read.

The command will automatically collect the computer files and place them on the desktop.

Then use 7zip to organize the files and one drive or drop box to place share links into the thread for troubleshooting.

This command will automatically collect these files: msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

Open administrative command prompt and copy and paste the whole command:

copy %SystemRoot%\minidump\*.dmp «%USERPROFILE%\Desktop\»&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt «%USERPROFILE%\Desktop\SFdebugFiles\»&type %SystemRoot%\System32\drivers\etc\hosts >> «%USERPROFILE%\Desktop\hosts.txt»&systeminfo > «%USERPROFILE%\Desktop\systeminfo.txt»&driverquery /v > «%USERPROFILE%\Desktop\drivers.txt» &msinfo32 /nfo «%USERPROFILE%\Desktop\msinfo32.nfo»&wevtutil qe System /f:text > «%USERPROFILE%\Desktop\eventlog.txt»&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall «%USERPROFILE%\Desktop\uninstall.txt»&reg export «HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components» «%USERPROFILE%\Desktop\installed.txt»&net start > «%USERPROFILE%\Desktop\services.txt»&REM wmic startup list full /format:htable >»%USERPROFILE%\Desktop\startup.html»&wmic STARTUP GET Caption, Command, User >»%USERPROFILE%\Desktop\startup.txt»

There are two files for you to find manually:

Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.

2) dxdiag: In the left lower corner search type: dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread

Please remember to vote and to mark the replies as answers if they help.

Bugcheck: 0x0000001e

As above, nearly every 2nd — 3rd day, AFTER I’ve shut Win7 down. Once I turn the system on again, I know its crashed (because its dual booting with Windows 2k). It boots straight in Windows 7 (It doesnt show the menu, so I can choose 2k, or Win7), then a black screen appears, with the line flashing left hand side of the screen. And hangs. Only thing I can do, is reset. Once I reset, it brings up resume or something, which fails, but if I reset / reboot again it’ll bring up the boot menu, so I can choose the OS I want to boot into.

Memory has been tested, its fine. I’ve scanned for errors. No errors. The ATI drivers havent been installed on this (its using Win7 vid drivers). I see it has something to do with KMODE EXCEPTION NOT HANDLED. Which still doesnt tell me anything. And the only time it happens, is when I shut Windows 7 down. It doesnt crash, while I’m in it / using whatever program. I could be on it all day, and it wont (with any bugcheck, or stop error). Any other ideas, on what else I can check?

NOTE: This has only started within the last week. Its been fine before now (since Win7 was installed about 3 mths)

Replies (32) 

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

See this thread on how to troubleshoot BlueScreens using BlueScreenView and MyEventViewer and
other methods.

Are you using RAID? If so those drivers would be very suspect. Also diskspace and other hard drive
issues are high on the list.

If you are sure disk issues are not the cause :

Think Video drivers mainly though it can be others. See the driver section in my generic bluescreen
troubleshooting methods below. BIOS, low level chipset drivers and antivirus/antispyway/security
programs can also cause this. Check the troubleshooter and when you get to the driver section refer
to the generic methods in next message and then return to the troubleshooter if needed.

BCCode: 1e 0x0000001e

Cause

This is a very common bug check. To interpret it, you must identify which exception was generated.

Common exception codes include:

An unaligned data reference was encountered.

A breakpoint or ASSERT was encountered when no kernel debugger was attached to the system.

A memory access violation occurred. (Parameter 4 of the bug check is the address that the driver attempted to access.)

For a complete list of exception codes, see the ntstatus.h file located in the inc directory of the Windows Driver Kit.

If you are not equipped to debug this problem, you should use some basic troubleshooting techniques. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates. Try changing video adapters. Check with your hardware vendor for any BIOS updates. Disable BIOS memory options such as caching or shadowing.

If you plan to debug this problem, you may find it difficult to obtain a stack trace. Parameter 2 (the exception address) should pinpoint the driver or function that caused this problem.

If exception code 0x80000003 occurs, this indicates that a hard-coded breakpoint or assertion was hit, but the system was started with the /NODEBUG switch. This problem should rarely occur. If it occurs repeatedly, make sure a kernel debugger is connected and the system is started with the /DEBUG switch.

If exception code 0x80000002 occurs, the trap frame will supply additional information.

If the specific cause of the exception is unknown, the following should be considered:

Hardware incompatibility. First, make sure that any new hardware installed is listed in the Microsoft Windows Marketplace Tested Products List.

Faulty device driver or system service. In addition, a faulty device driver or system service might be responsible for this error. Hardware issues, such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate this error.

If a driver is listed by name within the bug check message, disable or remove that driver. Disable or remove any drivers or services that were recently added. If the error occurs during the startup sequence and the system partition is formatted with NTFS file system, you might be able to use Safe Mode to rename or delete the faulty driver. If the driver is used as part of the system startup process in Safe Mode, you need to start the computer by using the Recovery Console to access the file.

If the problem is associated with Win32k.sys, the source of the error might be a third-party remote control program. If such software is installed, the service can be removed by starting the system using the Recovery Console and deleting the offending system service file.

Check the System Log in Event Viewer for additional error messages that might help pinpoint the device or driver that is causing bug check 0x1E. Disabling memory caching of the BIOS might also resolve the error. You should also run hardware diagnostics, especially the memory scanner, supplied by the system manufacturer. For details on these procedures, see the owner’s manual for your computer.

The error that generates this message can occur after the first restart during Windows Setup, or after Setup is finished. A possible cause of the error is a system BIOS incompatibility. BIOS problems can be resolved by upgrading the system BIOS version.

Look in the Event Viewer to see if anything is reported about those.
http://www.computerperformance.co.uk/vista/vista_event_viewer.htm

MyEventViewer — Free — a simple alternative to the standard event viewer of Windows.
TIP — Options — Advanced Filter allows you to see a time frame instead of the whole file.
http://www.nirsoft.net/utils/my_event_viewer.html

Here are some methods to possibly fix the blue screen issue. If you could give the Blue Screen
info that would help. Such as the BCC and the other 4 entries on the lower left. And any other
error information such as STOP codes and info such as IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA and similar messages.

BCCode: 116
BCP1: 87BC9510
BCP2: 8C013D80
BCP3: 00000000
BCP4: 00000002

or in this format :

Stop: 0x00000000 (oxoooooooo oxoooooooo oxooooooooo oxoooooooo)
tcpip.sys — Address 0x00000000 base at 0x000000000 DateStamp 0x000000000

This is an excellent tool for posting Blue Screen Error Information

BlueScreenView scans all your minidump files created during ‘blue screen of death’
crashes, and displays the information about all crashes in one table — Free
http://www.nirsoft.net/utils/blue_screen_view.html

Many BlueScreens are caused by old or corrupted drivers, especially video drivers however
there are other causes.

You can do these in Safe Mode if needed or from Command Prompt from Vista DVD or
Recovery Options if your system has that installed by the maker.

You can try a System Restore back to a point before the problem started if there is one.

Do these :

Start — type this in Search Box -> COMMAND find at top and RIGHT CLICK — RUN AS ADMIN

Enter this at the prompt — sfc /scannow

How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program
generates in Windows Vista cbs.log (and Windows 7)
http://support.microsoft.com/kb/928228

The log might give you the answer if there was a corrupted driver. (Does not tell all the possible
driver issues).

Also run CheckDisk so we can rule out corruption as much as possible.

Often updating drivers will help, usually Video, Sound, Network Card (NIC), WiFi, 3rd party
keyboard and mouse, as well as other major device drivers.

Manually look at manufacturer’s sites for drivers — and Device Maker’s sites.
http://pcsupport.about.com/od/driverssupport/ht/driverdlmfgr.htm

Installing and updating drivers in 7 (updating drivers manually using the methods above is
preferred to ensure the latest drivers from System maker and Device makers are found)
http://www.sevenforums.com/tutorials/43216-installing-updating-drivers-7-a.html

How to fix BlueScreen (STOP) errors that cause Windows Vista to shut down or restart
unexpectedly
http://support.microsoft.com/kb/958233

Troubleshooting Vista Blue Screen, STOP Errors (and Windows 7)
http://www.chicagotech.net/vista/vistabluescreen.htm

Understanding and Decoding BSOD (blue screen of death) Messages
http://www.taranfx.com/blog/?p=692

Windows — Troubleshooting Blue Screen Errors
http://kb.wisc.edu/page.php?id=7033

In some cases this might be required.

StartUp Repair from Recovery Options or Windows 7 disk

Hope this helps.

Rob Brown — MS MVP — Windows Desktop Experience : Bicycle — Mark Twain said it right.