Error 0xc000021a. BSOD. Computer won't boot and none of the fixes works

[0xc000021a]

I upgraded to windows 10 3 days ago and everything was fine until today when it decided to BSOD and never turn on again. It just happened out of nowhere. I didn't do anything unusual or install anything new.

Here's what happens when I try some of the most common fixes (sry about the poor formatting)

System restore --- Runs for a few minutes and then says "Could not restore your computer. No changes were made"

Clicking on any of the advanced startup options --- BSOD

Using the command prompt

dir D:\ --- Big HDD filled with random junk. Holds WindowsImageBackup and a backup of Home-Computer

dir E:\ --- This fucker magically jumps from drive to drive. It used to be on C:\ a couple of hours ago, then F:\ and now E:. It's very confusing, anyway this is a SSD where Windows is installed and all my program files. It Holds Windows and Windows.Old and everything else a system root should hold.

dir X:\ --- "Volume in drive X is boot" --- This drive holds the same directories as the E:\ drive but most of the folders are empty. I have no idea what this drive is but I know that the command prompt runs on it.

E:\Windows\System32\Drwtsn32.exe -I --- "is not recognized as an internal or external command, operable program or batch file."

E:\windows\system32\rstrui.exe --- "No system restore points have been created"

X:\windows\system32\rstrui.exe --- "No system restore points have been created"

dism /image:E:\ /cleanup-image /revertpendingactions --- "The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB."

So I tried to free up space in the E:\ drive using only the command prompt. It was pretty tedious to say the least and I did it all in vain because that message still showed up even though I had 13 gb of free space.

dism /image:X:\ /cleanup-image /revertpendingactions --- Error: 87 "the /image option that is specified points to a running windows installation. To service the running OS, use the /online option. For more information, refer to the help by running dism.exe /online /?."

Dism.exe /online /? --- "dism does not support servicing windows PE with the /online option.


I've tried a whole lot of other things aswell but I forgot to log them

Please don't bury this thread right away. I spent a very long time writing all of this up on a phone and this thread holds alot of information that can't be found anywhere else on google so if someone searches for one of these cmd outputs they're going to find this thread at the top of the list and hopefully find the solution they're looking or bring a solution

 

[Vivek Kairi]

Try reinstalling windows 10 again. It is the best option available to u and while installing format ur hard disk

 

[0xc000021a]

How do I do that?

 

[Vivek Kairi]

Download media creation tool and select Create installation media then download the iso, make bootable usb and then boot it using it.
It will ask for license key so make sure u have it
http://www.microsoft.com/en-us/software-download/windows10

 

[Rhinofart]

You could also try booting to the command prompt in the recovery section of windows, or on the installer iso, and then:Boot from the Install disk > Choose keyboard and click Next > Use recovery tools… and click Next > choose Command Prompt
type > bootrec /fixmbr (writes mbr but does not overwrite partition table)
type > bootrec /fixboot (writes new boot sector to system partition)
type > bootrec /scanos (scans for other OS’s that you might want to add to bcd)
(personally I find the above unneeded and use the last step)
type > bootrec /rebuildbcd (scans for other OS’s, unlike rebuildbcd it allows you to select the OS’s you want to add to bcd)

 

[0xc000021a]

I downloaded windows to a usb and tried to boot with it but then this happened http://answers.microsoft.com/en-us/windows/forum/windows_8-windows_install/going-into-circles-w-the-computer-started-using/cd15eec8-b8cb-4176-8d3e-c9ea50749b50?page=2

 

[budparker]

I upgraded to windows 10 3 days ago and everything was fine until today when it decided to BSOD and never turn on again. It just happened out of nowhere. I didn't do anything unusual or install anything new.

Here's what happens when I try some of the most common fixes (sry about the poor formatting)

System restore --- Runs for a few minutes and then says "Could not restore your computer. No changes were made"

Clicking on any of the advanced startup options --- BSOD

Using the command prompt

dir D:\ --- Big HDD filled with random junk. Holds WindowsImageBackup and a backup of Home-Computer

dir E:\ --- This fucker magically jumps from drive to drive. It used to be on C:\ a couple of hours ago, then F:\ and now E:. It's very confusing, anyway this is a SSD where Windows is installed and all my program files. It Holds Windows and Windows.Old and everything else a system root should hold.

dir X:\ --- "Volume in drive X is boot" --- This drive holds the same directories as the E:\ drive but most of the folders are empty. I have no idea what this drive is but I know that the command prompt runs on it.

E:\Windows\System32\Drwtsn32.exe -I --- "is not recognized as an internal or external command, operable program or batch file."

E:\windows\system32\rstrui.exe --- "No system restore points have been created"

X:\windows\system32\rstrui.exe --- "No system restore points have been created"

dism /image:E:\ /cleanup-image /revertpendingactions --- "The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. Use the /ScratchDir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB."

So I tried to free up space in the E:\ drive using only the command prompt. It was pretty tedious to say the least and I did it all in vain because that message still showed up even though I had 13 gb of free space.

dism /image:X:\ /cleanup-image /revertpendingactions --- Error: 87 "the /image option that is specified points to a running windows installation. To service the running OS, use the /online option. For more information, refer to the help by running dism.exe /online /?."

Dism.exe /online /? --- "dism does not support servicing windows PE with the /online option.


I've tried a whole lot of other things aswell but I forgot to log them

Please don't bury this thread right away. I spent a very long time writing all of this up on a phone and this thread holds alot of information that can't be found anywhere else on google so if someone searches for one of these cmd outputs they're going to find this thread at the top of the list and hopefully find the solution they're looking or bring a solution

 

[budparker]

I was running Windows 8 and (sadly) allowed Microsoft to "Update" me to Windows 10 which, like you, caused the dreaded Blue Screen of Death with error: 0xc000021a

"Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then
we'll restart for you. (100% complete)"

Of course, "they" didn't restart for me after quite a few hours of waiting. When you allow MS to update you from one Operating System to another you have no disc with Windows 10 on it to reinstall from, and no USB Drive with any repair data. Of course, your S/N is embedded in the computer that adamantly refuses to boot past the BSOD. I wonder if Microsoft has ever produced an operating system that was not plagued with an endless list of problems? I guess XP was as close to good as Microsoft has ever come.

 

[EsmaFingerpin]

I was running Windows 8 and (sadly) allowed Microsoft to "Update" me to Windows 10 which, like you, caused the dreaded Blue Screen of Death with error: 0xc000021a

"Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then
we'll restart for you. (100% complete)"

Of course, "they" didn't restart for me after quite a few hours of waiting. When you allow MS to update you from one Operating System to another you have no disc with Windows 10 on it to reinstall from, and no USB Drive with any repair data. Of course, your S/N is embedded in the computer that adamantly refuses to boot past the BSOD. I wonder if Microsoft has ever produced an operating system that was not plagued with an endless list of problems? I guess XP was as close to good as Microsoft has ever come.

How long did it take do you remember ?

 

[budparker]

I was running Windows 8 and (sadly) allowed Microsoft to "Update" me to Windows 10 which, like you, caused the dreaded Blue Screen of Death with error: 0xc000021a

"Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then
we'll restart for you. (100% complete)"

Of course, "they" didn't restart for me after quite a few hours of waiting. When you allow MS to update you from one Operating System to another you have no disc with Windows 10 on it to reinstall from, and no USB Drive with any repair data. Of course, your S/N is embedded in the computer that adamantly refuses to boot past the BSOD. I wonder if Microsoft has ever produced an operating system that was not plagued with an endless list of problems? I guess XP was as close to good as Microsoft has ever come.

How long did it take do you remember ?

It took me approximately 7.003 milliseconds to figure that out . . .

 

[etcss642]

I have the same problem with a clean install of Win10 Pro Ani Addition. Narrowed the problem down to the Aug 31 Cumulative Update KB3176928. Until this update, everything works fine. After update, BSOD with 0xc000021a. Startup repair fails both from restart and from ISO boot. Currently, I have to reload an image that I made with Macrium Reflect to get this HP Laptop (Profbook 6550a) to function. I came across some thoughts that it might be related to windows not being able to update the registry. Hope someone has a solution.

 

[etcss642]

Looks like there was a problem with Cumulative Update 31 August, 2016 KB3176938. I just reloaded my image and allow the superseding update 12 September, 2016 KB3189866 install and this time there was not a problem on the restart. Hope this helps you out