Windows 10: Help needed in debugging bugcheck: 0xC000021a'

The 0XC000021A bugcheck has reoccurred - I'm not sure why. I did allow a Microsoft cumulative update to take place a few days ago, but I'm not sure that was the sole reason for this latest bugcheck. I am attaching some output from Windbg for anyone interested in debugging this latest problem. I did run Windbg just to compare the previous bugcheck and they are somewhat similar, but the error seems to have occurred at a different location NTKRNLMP.EXE (module was updated?). I also have a full dump, if needed.

Attachment 41061Attachment 41063Attachment 41064

 

Why are you only uploading a few pictures of the crashes?

 

Sorry about that. As I mentioned above, I had to run a system restore in order to bring up Windows 10 successfully and update this thread. However, the minidump included in the attachment is for this most recent bugcheck - just wanted to be clear. I'm not sure that what was collected into the attached zip file will be consistent with the minidump.

 

I failed to send you the file that you're waiting for, here it is Attachment 41070

 

With a system restore it doesn't mean the dump files are removed. Everytime I thought that I was wrong *Wink

 

Just to be sure no dump is accidentally removed

We have ruled out system files and possible programs interfering.
Only thing for now left is drivers.





Diagnostic Test

DRIVER VERIFIER


Warning Please make a backup of your important files and get your rescue media or create one.
Please create a restore point.
Please follow this tutorial to run driver verifier.

Driver verifier stresses your drivers and will crash your pc if any driver fails due to a violation.

Driver verifier should be performed for a max of 48 hours, or when you have a bluescreen, whatever comes first.

If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset in safe mode driver verifier, or in the troubleshooting options open command prompt and type verifier /reset.



Note Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.

Please fill in your system specsPlease follow this tutorial and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely.How to fill in your system specs:

 

I enabled the driver verifier as shown in your tutorial, restarted Windows 10, and got a blue screen with the following violation:
'driver_verifier_iomanager_violation'. After the second failed restart, the system went into recovery mode and I chose to do a system restore which according to the restore process, failed. The system restarted and it BSOD'ed with an 0xC000012a (original failure). It then restarted and came up successfully with a message block indicating that the system restore was successful. At this point, I'm totally confused and am seriously thinking about going back to Windows 8.1. Any ideas ????

 

I meant 0xC000021A not 0xC000012a

 

Please use the tool and upload the zip file.

 

Which tool are you referring to?

 

What do you mean with which tool?
At the BSOD section there is just one tool.

 

If you're referring to 'dm_log_collector.exe, then I've uploaded that file to you in a previous posts. But here it is again Attachment 41202 . Please be a little patient - I appreciate your help, but this is a new experience for me. Having a very unstable system is not making things easy for me. I am now booting my 8.1 system which has been extremely stable (not 1 crash of any sort) and will deal with Windows 10 whenever I have time.

 

Hi clk1946,

You indeed uploaded the zip file previously, but that zip file doesn't contain the dump with driver verifier.
Unfortunately, the new uploaded zip file has one dump that is not created by driver verifier.

It is always a risk, as I mention in the instructions with recovery possibilities, but I need you to run driver verifier again.
This time when you get a crash again, in the recovery options, please try to open command prompt and enter the command
Code: verifier /reset[/quote] That should reset driver verifier so you can boot Windows normal.

FYI, the instructions are written with expectations that you again have a few crashes and get the recovery options after the crashes.
If you are able to open command prompt and reset verifier without recovery options, please do so.

 

After running with driver verifier for 8 hours, no BSODs were encountered. I reset the driver verifier and rebooted the system. The system came up without a problem and KB3093266 (cumulative fixes) was installed. The system was rebooted and BSOD'ed with 0xC000021A'. The system then rebooted and came up without a problem. I did not run the 'tool' because this is like all the other problems that I have been encountering with this system. I will tell you that when the driver verifier was running, the system was next to unusable. I think that I will wipe the Windows 10 partition and do a clean install - I called MSFT support and they concur.

 

Hij clk1946,

Please run driver verifier again and do not use your PC.
As I said, the PC will be very sluggy due to the stressing of drivers, this is totally normal.