Error 0xc000021a Blue screen, Wouldn't boot, SFC DISM *Log included

[windoo]

Hey guys!

Over the past 3 days I was dealing with the error 0xc000021a which gave me a blue screen before getting into the login screen.

Prior to that my computer was running fine, I got home from work one day turned on my computer only to find it crashing before the login screen, windows startup repair didn't repair anything, after a lot of trial and error with the sfc/dism tools using CMD from the recovery menu (also tried to fix the C:/ HD on another computer with the codes) then somehow I manage to to get the login screen after 3 days.

After logging in, I had a black screen and it wouldn't let me run explorer.exe saying it belong to a different version of windows. After using the SFC and dism combinations I manage to get into windows.

After logging successfully without any blue screen errors, I ran SFC and DISM/SFC codes and SFCFIX it still says I have corrupted files that cannot be repaired. I would like to know how to fix them to prevent anymore of those deathly errors that almost made me refresh/format my HD

Here is the log:

I'm running windows 8.

Thanks in advance

SFCFix version 3.0.0.0 by niemiro.
Start time: 2017-02-07 09:41:17.635
Microsoft Windows 8.1 Update 3 - amd64
Not using a script file.




AutoAnalysis::
WARNING: Failed to get store name from identity name with return code 2 for component NetFx4-vbc_exe and file vbc.exe. File is reported as corrupt by SFC.
CORRUPT: vbc.exe of component NetFx4-vbc_exe.


CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-a..ence-inventory.data_31bf3856ad364e35_6.3.9600.18472_non e_49d4cd34ea80a298\hwcompat_RS1.txt
CORRUPT: C:\Windows\winsxs\amd64_microsoft-windows-fontext_31bf3856ad364e35_6.3.9600.17415_none_8f909 369c75abe1a\fontext.dll
CORRUPT: C:\Windows\winsxs\wow64_microsoft-windows-fontext_31bf3856ad364e35_6.3.9600.17415_none_99e53 dbbfbbb8015\fontext.dll
CORRUPT: C:\Windows\winsxs\amd64_netfx4-system.data.sqlxml_b03f5f7f11d50a3a_4.0.9600.20976 _none_7cb7100cdc3deb11\System.Data.SqlXml.dll
CORRUPT: C:\Windows\winsxs\msil_system.core_b77a5c561934e08 9_4.0.9600.20976_none_42d84340745d6f2e\System.Core .dll
CORRUPT: C:\Windows\winsxs\amd64_netfx4-system.core_b03f5f7f11d50a3a_4.0.9600.20976_none_4 e1aaf982ded864f\System.Core.dll
CORRUPT: C:\Windows\winsxs\x86_netfx4-system.core_b03f5f7f11d50a3a_4.0.9600.20976_none_9 5c7e66f4269af55\System.Core.dll


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 8
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 0
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2017-02-07 10:00:08.263
----------------------EOF-----------------------

[windoo]

My computer is running into the same issue again

It keeps crashing before it gets to the login screen, continuous loop of blue screen to the repair screen.

Dism doesn't work anymore, it says error 50

DISM does not support servicing windows PE with the /online option.

Sfc /scannow shows that it repaired erros and it needs to reboot, but still the same issue

Any help would be appreciated, thanks.

[Jintan]

Howdy Windoo,

If the system doesn't boot, did you get to a command prompt to run that tool? If so, have you tried running a check disk?

[Jintan]

What is DISM please?

[Ned Seagoon]

Originally Posted by Jintan

What is DISM please?

Never used it, but since you ask, does this help?

[Lewis-H]

There are a number of solutions to fix this error. Just follow the instruction properly.

Method # 1: Repair Corrupt System Files
Download and run Reimage Plus by clicking here to scan for corrupt files, if corrupt and missing files are found, repair them.

Method # 2: Booting Windows Manually
In order to resolve this problem, you have to boot Windows manually. Booting the Windows in safe mode wouldn’t more in most cases. So, you have to boot it using force drivers to have the signature disabled option available inside Advanced Boot Options. To access this option, follow the steps below.

1. Restart the PC from Windows holding the Shift key and clicking on the Restart. If you can’t access the Restart option on your Windows, then you might need to boot through a Windows bootable USB.

2. It will take you to an options screen. Select Troubleshoot to access the advance tools.

3. From the next screen, choose the Advanced option.

4. On the next screen, you will see plenty of options. All you need to do is to click on Startup Settings as shown in the picture below.

5. On the startup screen, there would be a number of options to select from. Press F7 labeled as Disable driver signature enforcement.

Your PC would restart with the option you selected and now, you can tweak your PC using different options.