New
#21
I meant 0xC000021A not 0xC000012a
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
That should reset driver verifier so you can boot Windows normal.Code:verifier /reset
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.
To solve my problem, I did a 'clean' install of windows 10 - no problems and it has been over two weeks of BSODless computing.