C00002lA Fatal System Error is a blue screen of death error that may occur when you start your Windows NT 4.0 based computer. This error causes the screen to turn blue and the system also shuts down.
The stop C000021A error message is displayed in the following format:
Stop c000021a {Fatal System Error}
The session manager initialization system process terminated unexpectedly with a status of 0xc0000017 (0x00000000, 0x0000000) The system has been shut down.
The stop C000021A error occurs when either Crsrss.exe or Winlogon.exe fails. When the Windows NT kernel identifies that either of these processes has failed, it stops and the error code stop C000021A appears on the computer screen.
Here are some of the underlying causes for the stop C0000021A error:
To resolve the stop C000021A Fatal System Error on your PC try the following solutions:
If the error occurred after you recently installed a new program, then it is advisable to remove that program. The error occurs due to the incompatibility of the program.
To remove the program go to the start menu and click on the control panel. Now click on Add/Remove Program tab and double click on the program name that you recently installed and remove it from the list.
Once removed, not reboot your PC. Reinstall a compatible program and run it. It is most likely to resolve the issue. However, if the stop C000021A error still occurs, then it means the problem is critical. It is related to the registry.
This procedure is slightly long and tricky.
To try it, you need to be technically sound. Here’s what you have to do: first create a parallel installation of Windows NT.
Start your PC to the parallel installation and then open the Registry Editor. On the Registry Editor’s Windows menu click HKEY_LOCAL_MACHINE on Local Machine and then click Load Hive.
Now type the path %systemroot%system32configsystem into the System hive of the prior installation. Then click open. Here you will be prompted to enter the name of the key, type TEST.
Note the setting for the current DWord value in the preceding registry key. This is 0x1 and is denoted by CURRENT:Reg_Dword: 0x1.
This value indicated that the Current Control Set for your original Windows NT installation corresponds to ControlSet001 in this window. Now if the value is 2, it indicated that the Current Control Set corresponds to ControlSet002.
Now locate the following registry key:
HKEY_LOCAL_MACHINETESTControlSetXXXControlSession Manager. XXX is the Current Control Set Value. And delete any pending file rename operation entries. Then click TEST hive and then click Unload Hive. After that again repeat the process, open the registry menu and click load hive, here type the path %systemroot%system32configSoftware to the Software hive of the prior installation and then click open.
Now you type TEST 2 when you are prompted for the name of the key. Remove any pending file rename operations entries in the following registry keys:
HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnce
HKEY_LOCAL_MACHINETEST2MicrosoftWindowsCurrentVersionRunOnceEx
Now click TEST2 hive and then click unload hive. Quit the Registry Editor and then restart your original installation.
This will resolve the stop C000021A error.

Stop: 0x0000000A (parameter1, parameter2, parameter3, parameter4) IRQL_NOT_LESS_OR_EQUAL *** Address x has base at x - filename
Error Causes
That being said, now when services are back we stopped and reflected on the platform itself and on its users. If Facebook is vulnerable so are its users, but sometimes users themselves are responsible for being a target. We step back and take a look at posts that manifest on Facebook and have come with some advice on what things you should never post on Facebook and on other social platforms.
BLUE SCREEN ERROR - QtCore4.dll Not Found
Filei386QtCore4.dll could not be loaded. The error code is 7. Setup cannot continue. Press any key to exit.
Error CausesAre you trying to update your Windows 11 OS and are receiving a 0x800f0905 error? Do not sweat and do not worry we have a couple of solutions that you can try in order to fix this issue. How this error is tied to various things like misconfigured settings, corrupt system files, and more there is no way to present one simple solution that will solve everything in one click.
Therefore we are presenting a couple of solutions that will fix your issue, it is advisable to follow them as presented since they will go from the most common to the more complex one.
The most common fix and one that will actually repair things most of the time is simply running the Windows Update troubleshooter.
If the previous solution did not work we will need to do things manually. Follow the steps as presented in order to reset Windows update components.
Well, that was a lot of typing or copy and pasting line by line followed by ENTER after each one but hopefully, your issue is solved. These provided solutions fixed most users' issues with this error but if for some reason this is not the case for you, move to the next step.
If you are still having 0x800f0905 error after previous attempts do the following:
If for any reason previous solutions have not provided you with the solution we will try to fix the issue by performing system restore.
If for any reason Windows still cannot install the update, try installing it manually.
If nothing worked, reset your Windows 11 to its factory settings to fully repair and reset the whole operating system.
Option to right-click on the taskbar and launch task manager is gone but do not worry there are other same and simple ways you can launch it.