none
Windows 10 blue screen - BAD_SYSTEM_CONFIG_INFO RRS feed

  • Question

  • After upgrade My Laptop ( HP Ultrbook ) the upgrade complete successfully , but after first restart i got the the following error

    Windows 10 blue screen - BAD_SYSTEM_CONFIG_INFO

    i couldn't find any way to back step . Please help 


    Mahdy

    Saturday, August 15, 2015 4:35 PM

Answers

  • Hi Mahdy,

    The following is the information is from the MSDN site about the BAD_SYSTEM_CONFIG_INFO:

    "

    The BAD_SYSTEM_CONFIG_INFO bug check occurs if the SYSTEM hive is corrupt. However, this corruption is unlikely, because the boot loader, known as NT Loader (NTLDR) in versions of Windows prior to Vista, checks a hive for corruption when it loads the hive.

    This bug check can also occur if some critical registry keys and values are missing. Thee keys and values might be missing if a user manually edited the registry.

    "

    Source: https://msdn.microsoft.com/en-us/library/windows/hardware/ff559188(v=vs.85).aspx

    We may try to hard restart the system fro more than 3 times, this would bring the Windows Recovery Environment, then we may choose options there that would work. We may also take use of the install media and then do the recovery form there.

    Recovery options in Windows 10

    http://windows.microsoft.com/en-us/windows-10/windows-10-recovery-options

    Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, August 17, 2015 6:57 AM
    Moderator

All replies

  • Did you update or clean install from the ISO?

    Can we get some more specific information?


    Wanikiya and Dyami--Team Zigzag

    Saturday, August 15, 2015 4:49 PM
    Moderator
  • Hi Mahdy,

    The following is the information is from the MSDN site about the BAD_SYSTEM_CONFIG_INFO:

    "

    The BAD_SYSTEM_CONFIG_INFO bug check occurs if the SYSTEM hive is corrupt. However, this corruption is unlikely, because the boot loader, known as NT Loader (NTLDR) in versions of Windows prior to Vista, checks a hive for corruption when it loads the hive.

    This bug check can also occur if some critical registry keys and values are missing. Thee keys and values might be missing if a user manually edited the registry.

    "

    Source: https://msdn.microsoft.com/en-us/library/windows/hardware/ff559188(v=vs.85).aspx

    We may try to hard restart the system fro more than 3 times, this would bring the Windows Recovery Environment, then we may choose options there that would work. We may also take use of the install media and then do the recovery form there.

    Recovery options in Windows 10

    http://windows.microsoft.com/en-us/windows-10/windows-10-recovery-options

    Regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Monday, August 17, 2015 6:57 AM
    Moderator
  • What OS did you have on the notebook prior to upgrade?
    Monday, August 17, 2015 4:27 PM