Page 3 of 3 FirstFirst 123

  1. Joined : Aug 2015
    Escondido
    Posts : 24
    windows10
       04 Oct 2015 #21

    I meant 0xC000021A not 0xC000012a
      My System SpecsSystem Spec


  2. Joined : Jun 2015
    Posts : 10,908
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       04 Oct 2015 #22

    Please use the tool and upload the zip file.
      My System SpecsSystem Spec


  3. Joined : Aug 2015
    Escondido
    Posts : 24
    windows10
       05 Oct 2015 #23

    Which tool are you referring to?
      My System SpecsSystem Spec


  4. Joined : Jun 2015
    Posts : 10,908
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       05 Oct 2015 #24

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


  5. Joined : Aug 2015
    Escondido
    Posts : 24
    windows10
       05 Oct 2015 #25

    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.
      My System SpecsSystem Spec


  6. Joined : Jun 2015
    Posts : 10,908
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       05 Oct 2015 #26

    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
    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.
      My System SpecsSystem Spec


  7. Joined : Aug 2015
    Escondido
    Posts : 24
    windows10
       05 Oct 2015 #27

    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.
      My System SpecsSystem Spec


  8. Joined : Jun 2015
    Posts : 10,908
    Windows 10 Pro / Windows 10 TP / Windows 8.1 Pro / Windows 7 Pro
       06 Oct 2015 #28

    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.
      My System SpecsSystem Spec


  9. Joined : Aug 2015
    Escondido
    Posts : 24
    windows10
       25 Oct 2015 #29

    To solve my problem, I did a 'clean' install of windows 10 - no problems and it has been over two weeks of BSODless computing.
      My System SpecsSystem Spec


 
Page 3 of 3 FirstFirst 123


Similar Threads
Thread Forum
BSOD on Startup. The bugcheck was: 0x0000001e
Hi, I received a BSOD on startup on the 7th of August at 6:57 pm. I have been trying to look into why this has happened but couldn't find out. Could you please help me find out the cause of the BSOD and how to fix it?
BSOD Crashes and Debugging
driver_overran_stack_buffer then 0xc000021a
I was browsing Tumblr on Microsoft edge and suddenly I get a BSOD which said driver_overran_stack_buffer. Now I get the endless reboot, 0xc000021a. I do not have a restore point or disc from which to recover from. I upgraded downloading the tool...
BSOD Crashes and Debugging
Solved Debugging Tools for Windows 10 Question
Shouldn't Windbg work with any dump file, even if its for 10? OR is this Windbg only going to work with 10. What am I doing wrong? (BTW, this is a dump from a Windows 7 machine I'm trying to open) I get this error:
BSOD Crashes and Debugging
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 08:17.
Find Us
Twitter Facebook Google+



Windows 10 Forums