BSOD 0xc000021a - Cannot boot Win 10 at all

Ztruker said:

I am asking for some of the other folks here to take a look and see if they have any suggestions.

One thing I did think of, boot the install DVD or flash drive then take the Repair my computer path to get to a Command Prompt.
Check in C:\Windows\minidump, see if there are any .dmp files there. If there are, copy them to a flash drive then zip them up and upload here.

Hi guys,

Thanks for sticking with me. I'll answer these two posts separately should you both wish to comment.

Ztrucker first...

There are a few minidump files (5 to be exact). I've zipped them up and included them here.


Hi AxeO,

Running your stuff now. this will take a while so will post results as soon as scans are done.

axe0 said:

In case you want to mention me, mentioning someone can be done using the @ before the name like @gaztech, be sure that you get the name correct :)
axe0 is with a zero


Before more suggestions are provided we would like to know the results of the suggestions from my previous post so we can determine a next step.

What I see is a few hardware related crashes, a 0x9F caused by Kaspersky and one I've never seen before showing a lot from the file system.
@axe0 Noted! Still running tests. Will revert here when all are done. It's a 1TB drive so they take a while!

Chkdsk on both the boot partition and the windows partition comes up with no errors. Had to dismount the windows drive first...

I had been trying to get Powershell to start in order to run a few other things, but have been unable through all of my investigation to get it to start at all. Just tried now in order to get the info you need but - guess what? It won't start. Maybe it won't start in the recovery environment?

I've been playing with WMIC to get info out of the system (not to make changes) and it's very interesting just how much info can be extracted using this tool.

I worked through the correct commands to get the Event Log entries as per your request as I couldn't get Powershell to run.

I used this command:
WMIC NTEVENT WHERE "EventIdentifier='1001' AND LogFile = 'Application' " GET EventCode, EventIdentifier, RecordNumber, SourceName, TimeGenerated, Type, Message, EventType /format:list > list.txt

This command works fine on my (working) Win10 machine but when I run from the recovery prompt on my dud machine I get:
Node - MININT - MVEURNP
ERROR:
Description = Invalid Class

No idea what that means.

One thing I did find using WMIC to look at services was that the TrustedInstaller Service wasn't running and other users seem to indicate that both sfc and dism won't run repairs if this service isn't up. However, starting this service didn't make any difference - and I found that after a while, the service is automatically stopped. Not sure what stops it!

Will now look at running the SeaTools to see what that pops up. Later...

Oh, and some more info to add...
I decided to check the ntbtlog.txt file and found that it stops at usbhub3.sys. Checking the system32 directory revealed that this file was missing so I tried copying this file from another working Win10 system (my laptop) to windows\system32. Result - no difference. Still crashes with C000021a error.

I then checked the SrtTrail.txt file (located in Windows\System32\Logfiles\Srt) to see if there were any errors in there. I found that although all the system start attempts had been logged, there were no errors showing at all. All tests showed up as being successful. Under "Root Cause Found" the message is: "Startup Repair has tried several times but still cannot determine the cause of the problem."

Log is showing number of repair attempts: 12. Last successful boot time: 21 June 2016 at 16:27:29 GMT.

Oh, and some more info to add...
I decided to check the ntbtlog.txt file and found that it stops at usbhub3.sys. Checking the system32 directory revealed that this file was missing so I tried copying this file from another working Win10 system (my laptop) to windows\system32. Result - no difference. Still crashes with C000021a error.

I then checked the SrtTrail.txt file (located in Windows\System32\Logfiles\Srt) to see if there were any errors in there. I found that although all the system start attempts had been logged, there were no errors showing at all. All tests showed up as being successful. Under "Root Cause Found" the message is: "Startup Repair has tried several times but still cannot determine the cause of the problem."

Log is showing number of repair attempts: 12. Last successful boot time: 21 June 2016 at 16:27:29 GMT.

Attachment 90120

Seatools final Screen. All looks fine. States that tests were passed.