One of the most unpleasant (and besidescritical) failures is the appearance of a blue BSoD screen at the start of the operating system with the issuance of a BAD_SYSTEM_CONFIG_INFO stop code in the message. Windows does not load, and it seems that nothing can be done, because the violation in the boot is fixed at each start. However, do not give up, because there is a way out. Next, there are several simple methods that are guaranteed to correct the situation (although, depending on what was the root cause of the errors). For an ordinary user they may seem a little complicated, however, if OS is not loaded under any pretext, they can not be avoided, because it is their application that allows to eliminate such impartial situations. However, everything is in order, but first we will find out what is wrong and why it arises.
First, it's worth noting that this crash appears in almost all the latest Windows systems, starting with the seventh version. But what is the stop code in the message?
Error BAD_SYSTEM_CONFIG_INFO (Windows 8 orany other modification) directly indicates the impossibility of initializing the system configuration (both hardware and software). As the possible reasons for this situation, in most cases, the boot loader (NTDLR) and system files are corrupted, the RAM bars are not working properly, or other possible problems related to them, failures when trying to force access to RAM, etc.).
As one of the main methods of fixing the problem, the standard OS recovery is applied, which can be activated via the boot line of the last good configuration at startup.
To access the boot menu at the very beginningBoot the OS several times to press the F8 key (in Windows 10 to activate this method of access, you must use a removable media with the boot mode set legacy through the command line).
If the standard procedure does not work, but failsBAD_SYSTEM_CONFIG_INFO will appear again, you need to use the same menu, but in boot options select start with command line support. However, it's better to boot from a removable recovery or installation disk (flash drive) and use the command line from it (Shift + F10 in the Recovery Console). The use of a removable device is advantageous in that when BAD_SYSTEM_CONFIG_INFO is booted from the hard disk in normal mode, the BAD_SYSTEM_CONFIG_INFO error can still make itself felt.
After gaining access to the command console, the first thing to do is to check the system files and libraries for damage. This is done by running the sfc / scannow command.
If you are booting with support for network drivers, you can try to restore the system online by using the command shown in the image above.
However, even after performing such operations, a failureBAD_SYSTEM_CONFIG_INFO may appear when attempting to restart with a normal system boot. In this case (again via the boot menu with the F8 key pressed), you need to start in safe mode.
If the download is successful, againA command-line call is used, in which the two lines shown in the image above are written. After confirming their execution, you can restart the operating system in normal mode.
But this is not how the troubleshootingend. Since sometimes the appearance of the screen can really be associated with memory disruptions, in most cases it is recommended to remove the slots from the slots on the motherboard in turn, and then check the possibility of starting the system. If a bad block is detected, it must either be simply dropped or replaced with a similar one.
In some situations, when the system couldit is advisable to use disk antivirus scanners (for example, Rescue Disk from Kaspersky Lab), which have their own download capabilities before the start of the OS and are able to detect even deeply hidden viruses (even in memory).
If failures are associated with a boot loader corruption,perhaps it will help to fix it or even completely overwrite it through the command line using commands based on the Bootrec.exe tool. At least one of the proposed options should have a positive effect. But it's better to do most of the actions with loading from recovery media and calling the command console, which is the first and most indispensable tool for eliminating most known system errors at boot time.
However, it also happens that the screen appears,keeps for a while, and then disappears. If the system is somehow loaded, and the cause of the error lies in the dynamic libraries or system services, you can use the DLL Suite and MS FixIt utilities. The first loads the corrupted or missing DLL objects, the second serves as a fix for problems with the operation of the system services. By the way, it is suitable for many other purposes, when the methods used by the user have no tangible effect. But, as a rule, in our case the use of the command console is the key to success. This is recognized by all experts and users who have encountered this problem.
</ p>
