BSOD after upgrade to 1909 release of Win10


  1. Posts : 2
    Windows10
       #1

    BSOD after upgrade to 1909 release of Win10


    Hi, after have made the last windows upgrade (1909), My PC with Windows10pro stopped to work with BSOD.
    I buyed EasyRE software but, after have run it, I still have the BSOD screen with this error message:

    "Your PC ran into a problem and needs to restart. You can restart."
    StopCode:0xc000021a.

    I can only turn off the PC, no other choices.

    Any help?

    thanks,
    Roby
      My Computer


  2. Posts : 1,612
    11, 10, 8.1 and 7 all Professional versions, and Linux Mint
       #2

    1. Try disconnecting all external devices except mouse and keyboard if those are so connected.
    2. What is the make and full model of the computer. Is it a laptop or a desktop
    3. Do you have a USB flash drive that you can make a windows 10 installation - on, and of course another computer to make it on, so that we can use that to attempt a repair of this one. IF the options at 1 and 4 fail.
    4. Try this if disconnecting all external devices is no good
    Boot to Advanced Startup Options in Windows 10

    Option 6.
    Presuming you do not get to the log-on screen before the BSOD

    5. If option 1 fails and you can get to the recovery screen - post back and I will guide you further
    Last edited by Macboatmaster; 22 Sep 2020 at 17:11.
      My Computer


  3. Posts : 2
    Windows10
    Thread Starter
       #3

    thanks..


    I arrived in this forum after tryed everything: SFC, DISM, chkdsk and yes, I cannot have the logon screen and I was using a win10 usb to enter into command console.

    At the end I have reinstalled windows10 and I'm reinstalling all the apps and drivers.

    thanks a lot for your support, regards

    Roby
      My Computer


  4. Posts : 1,612
    11, 10, 8.1 and 7 all Professional versions, and Linux Mint
       #4

    Cheers
    If you could not get anywhere with the recovery from 3 reboots and then safe mode or disable driver signature enforcement then you may have suceeded with registry cmds to use the regback feature
    However it is sorted now.
    Sometimes caused by 3rd party apps including antivirus apps that just do not sit well with windows 10 updates.
    Also, as I mentioned can be caused by unsigned drivers being used.
      My Computer


 

  Related Discussions
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 14:06.
Find Us




Windows 10 Forums