Since upgrading to Win 10, get frequent BSOD's on startup


  1. Posts : 87
    10 Pro
       #1

    Since upgrading to Win 10, get frequent BSOD's on startup


    I was running Windows 8.1 until roughly a month ago. When Threshold 2 update was released, I decided to try upgrading to Win 10, via the GWX app. Everything pretty much works, I have a few issues but they are mostly minor. One of these issues is that when I start up my PC, it frequently gives me a BSOD - BAD_SYSTEM_CONFIG_INFO. It collects data, and then reboots and starts up like it should after the BSOD.

    This is somewhat inconvenient, it only happens on start-up and I don't get BSOD's while operating. I am mostly afraid that I will BSOD during an update (since they frequently need you to restart), and I will get stuck in a repair loop afterwards.

    I ran the DM_Log_Collector per instructions.
      My Computer


  2. Posts : 14,901
    Windows 10 Pro
       #2

    Hi yu gnomi,

    The 0x74(BAD_SYSTEM_CONFIG_INFO) is caused by system hive corrupting, missing registry keys/values or the memory.
    We can try a few things, but if the tests comes clean, you would need to do a clean install.
    A system hive corruption is, so far I understand, not repairable and would be the outcome if the tests comes clean.
    Please make a backup of your important data a.s.a.p. and follow instructions.




    Diagnostics Test

     System File Check


    Please try following:
    • Open an admin command prompt
    • Copy/paste "sfc/scannow" (without quotes) and press enter
    • When it finished reboot your system
    • Open again an admin command prompt
    • Enter sfc/scannow again

    If sfc/scannow does NOT say "Windows Resource Protection did not find any integrity violation" after the second SFC, please upload the cbs.log file located at {windows partition}\Windows\Logs\CBS\, if the file is too large try a 3rd party uploader like dropbox, onedrive, google drive, mediafire etc.
    System File Check(SFC a.k.a. Windows Resource Protection) needs to have your system rebooted in order for sfc to try to fix the problems that it finds.




    Diagnostic Test

     RAM TEST


    Run MemTest86+ to analyse your RAM. MemTest86+ - Test RAM - Windows 10 Forums

    Note   Note


    MemTest86+ needs to be run for at least 8 passes for conclusive results. Set it running before you go to bed and leave it overnight. We're looking for zero errors here. Even a single error will indicate RAM failure.
      My Computers


  3. Posts : 87
    10 Pro
    Thread Starter
       #3

    Thank you for your help.

    sfc /scannow completed and found nothing.

    Will run Memtest86+ later tonite - will leave it running overnight if necessary- and run sfc /scannow again after booting.

    I am guessing I will end up doing a clean install, maybe this weekend.
      My Computer


  4. Posts : 87
    10 Pro
    Thread Starter
       #4

    I used Windows Memory Diagnostic, instead of Memtest 86+, because it is less of a hassle for me. I currently boot UEFI with Secureboot on; configuring my system to boot off of a non-UEFI thumb drive takes multiple boots and entering UEFI settings, and multiple boots to return to how I have it.

    No memory errors found, and a second sfc /scannow run after startup found no issues.
      My Computer


  5. Posts : 14,901
    Windows 10 Pro
       #5

    You better run MemTest86+, it finds errors where the built-in fails hard.
      My Computers


 

  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 20:43.
Find Us




Windows 10 Forums