Help needed in debugging bugcheck: 0xC000021a'

axe0 · 19 Sep 2015

Good to hear that :)
Glad the problem is solved :)

clk1946 · 04 Oct 2015

My Windows 10 system has retrograded yet again to the same OxC000021A bugcheck. I am attaching 3 pages from Windbg's analysis output which points at NTKRNLMP.EXE again, but at a different location. In order to get Windows to come up again, I had to do a System Restore from a date prior to the last cumulative Microsoft update that was applied. The effects of this restore is yet to be seen/experienced - right now I'm focused on getting this information out to anyone that might be able to help in understanding why the system continues to act unpredictably. BTW, I am keeping the two full dumps if anyone needs additional information. I am not a Windbg expert, so other than provide some screenshots of Windbg's output, my help in this area is limited.
Attachment 41041 Attachment 41042 Attachment 41043

axe0 · 04 Oct 2015

Please use the tool and upload the zip file.
There are some causes for this crash, but the files needs to be analysed to point to 1 of the directions.

clk1946 · 04 Oct 2015

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 41061 Attachment 41063 Attachment 41064

axe0 · 04 Oct 2015

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

clk1946 · 04 Oct 2015

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.

clk1946 · 04 Oct 2015

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

axe0 · 04 Oct 2015

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

axe0 · 04 Oct 2015

Just to be sure no dump is accidentally removed

If you are using a program like Ccleaner please stop using it while troubleshooting.
This because programs like Ccleaner remove dump files that are needed to troubleshoot.
Or configure Ccleaner to not remove dump files:

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 specs

Please 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:

clk1946 · 04 Oct 2015

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 ????