How to fix 0xc000021a, BSOD?

axe0 said:

What videos do you mean?
Chkdsk or any other utility like sfc doesn't need you to be logged in.

I didn't mean the tests. I meant command prompt in recovery options.

axe0 said:

I understand what you mean, but it is usually a utility that needs the login and not the utility that accesses those utilities. I have never seen cmd ask for such information.

OK Sorry it was off topic a bit.
But pls help me solve the BSOD.
Can you check the uptime from the minidumps? Maybe then we
salvage some data.
Is it possible that the BSOD is due to lack free space? I can't check because I don't own an external drive right now so I can't free HDD space till May(Will buy one).
Thx for real quick response.

axe0 said:

It is more likely possible that chkdsk has issues writing due to lack of free space.
It is less likely possible that a BSOD occurs due to lack of free space, AFAIK this should be happening on the boot partition in order to cause trouble.

Up times are less than 1.5 minutes, normally the HDD and/or RAM would be causing issues with such up times but since you can't properly test the RAM it's either RMA the RAM and hope for success or trying other things.

So I guess we have come back in May. I don't know much about forums. So do we freeze this thread or something till may or start new thread again in May 2017 or let it be as it is.

Can you check these files for me please(Compare with standard Windows 10 PC)?
What is "C:\$GetCurrent\Logs\downlevel_2016_10_18_20_56_47_927.log" log for?
I don't know why but i feel 2016/10/18 may the day it all got messed up.
I know its not right way to solve the problem but have to start somewhere.
These hidden folders are in C: drive.
I deleted $Windows.~BT & $Windows.~WS folders some time ago(Wanted to inform).
The only hidden folders starting with $ in C: drive is now uploaded two folders and $RECYCLE.BIN folder(I suppose there should be more).
Also Code:

Code:

    bootrec /scanos

gives Total identified Windows installations: 0 (Bugging me most). Please answer this as it is in my first post too.
(My thoughts:I once thought Windows is somehow not detected properly.)

I once being tired of finding methods to fix the bsod reluctantly used driver verifier(Sorry I know I shouldn't). What happened was the PC was not booting even in driver signature enforcement disabled mode and I was happy that it was a different BSOD(i.e "Driver Verifier Detected Violation"). I used RegBack folder to get back to earlier state of BSOD. But oddly it didn't give me any minidumps for which I had done the experiment. Any opinions.
(My exams start on 9th and end on 28th of this month. Any help before or after this period is appreciated).