A kind person once advised me to look at the settings of my computer for the use of multi-cores and a large amount of RAM. You need to look at this case using the msconfig utility, in the “Download” tab, “Advanced parameters” button. There you can tell stupid Windows how many processors it has and how much memory it has.
Well, you don’t need to ask me twice (or rather, advise me twice), and the person who advised me was reliable and proven. I did as they suggested. I sent the computer to reboot. I'm sitting, waiting for a miracle.
And then it started... When I first tried to start, my Windows 7 gave blue screen death (BSOD) with code 0x00000074 and the message that I have “ bad_system_config_info". Attempts to boot the system in protected mode, restoring the last working configuration, etc. had no effect.
I tried "troubleshooting problems" Windows startup", which the installation disk offers - is unprincipled. Almost reached the point of despair Windows installations. But, thank God, I had a laptop at hand, from which, after googling, I found one bourgeois forum where it was recommended to use the magic “bcdedit” utility, which is used to work with a secure storage of boot configuration data.
For reference: earlier, up to and including Windows XP, bootable Windows menu was described in the boot.ini file located at the root of the boot partition. It was ordinary text file, which was convenient to edit even in Notepad. Beginning with Windows Vista, this file has been replaced by this very storage - BCD, which is a binary file. The console utility “bcdedit” is designed to work with it.
The possibilities of the new trend - the features nicknamed BCD - are quite extensive and I cannot describe them all, because... I don't know myself. But, among all the variety, it has the ability to control settings for the number of processors and size random access memory. Including the ability to roll back to default settings. This is done using the following commands (in the recovery console, called by pressing F8 while Windows is loading):
bcdedit/deletevalue (default) numproc- sets the default value for the number of processors;
bcdedit/deletevalue (default) truncatememory- sets the default value for the amount of RAM;
After running these commands and prompting to reboot, my Windows 7 booted like a charm. And checking msconfig, “Download”, the “Advanced settings” button showed that the settings were indeed changed to default. That's all the medicine.
Although, based on what I managed to read about this STOPcode, we can conclude that such an error can also occur with faulty RAM modules (although with a faulty RAM, any error can occur). Well, of course, if there is a problem with hard drive when the BCD storage itself is damaged. I also admit that a problem may arise when using for installation Windows various homemade assemblies, where non-default settings of these parameters (number of processors and size of RAM) can end up in the configs of the Windows being installed. Keep this in mind, comrades!
The bad system config info error belongs to the category of the most irrational troubles that can happen on one of the latest operating systems from Microsoft. The thing is that the appearance of a blue screen of bad system config info usually indicates problems with system libraries, which are automatically loaded by a special NTLDR protocol. But the operating system, purely theoretically, when it starts, should independently check the functionality of such files and correct damage if it is detected.
However, sometimes this, for some unknown reason, does not happen, which leads to bad system config info Windows 7 or a similar message on the eighth and tenth versions of the OS.
Therefore, you need to know how to fix bad system config info Windows 10 (8, 7). There are two methods to solve this problem.
Option one. Loading a successful configuration
Sometimes, to fix bad system config info Windows 8, it is enough to do just a few simple steps.
How to solve bad system config info:
- Start the reboot procedure personal computer or laptop.
- Have time to press the “F8” key.
- Try loading the last known good configuration in the list provided.
Sometimes the user forgets to press in time the desired button, the system continues to boot once again with an uncorrected error, which naturally again leads to bad system config info Windows 10 at boot. If this is exactly what happened, it is recommended to repeat the procedure described above.
If this method did not bring a positive result, then you should move on to the second method.
Option two. Working with the command line
What to do - bad system config info Windows 10, but the first option was not successful?
There is another sequence of actions that almost always leads to positive result solving the problem:
- Reboot the computer again.
- Go to selecting system boot using the same “F8” button.
- Select the menu responsible for troubleshooting the system. It should be located at the very top of the proposed list.
- In the new window, go to the command line.
- Enter two phrases one by one: “bcdedit /deletevalue (default) numproc” and “bcdedit /deletevalue (default) truncatememory”.
All. You can try to start the PC in normal mode. Most often, this method solves the problem. However, sometimes even that is not enough. If this particular possibility occurs, then, unfortunately, you will have to initiate the procedure of reinstalling the operating system. At this stage, of course, you will need to spend significantly more time resources. Initially, you need to have on hand boot disk with the required OS version.
- Insert the disc into the reader.
- Restart PC.
- Go to the BIOS menu and change the priority of reading information from the stationary drive to the drive with boot data.
- Save, start the computer.
If everything is done correctly, the user will see in front of him standard menu OS installations from Microsoft, where everything is quite simple. You only need to follow the recommendations from the installer.
Option three. Official
The manufacturer of the most famous operating systems in the world provides its own solution to this problem. According to information on the official Internet resource of the corporation, the cause of such a situation can easily be damage to the operating memory sticks. Unfortunately, this option often leads to financial waste, since you will have to buy a new product. But, initially, you need to reliably make sure that this is the cause of the trouble.
If the user's computer uses several sticks, this is easy to do:
- Remove the products from the slots one by one and turn on the PC to check for an error.
- If the problem disappears, you will have to replace the RAM that was removed at this point.
In the event that the equipment uses only one strip, you will need to take another one from someone, guaranteed to work, in order to perform a similar verification procedure.
Blue Screen of Death 0x00000074 often occurs on the Windows 7 operating system, however, this critical failure is also possible in other versions of Microsoft OS. The cause of the failure is damage to the so-called system hive.
It is worth noting that this situation is extremely unlikely, and all because the Windows Loader checks the hive when loading the OS. Among other things, the blue screen of death 0x00000074 can occur due to the absence of certain values and keys in the registry. Fortunately, this BSoD can be resolved with a couple of commands entered through the Command Prompt. Let's take a look at them.
Solution BSoD 0x00000074
So, you probably have the following question: how to launch the Command Prompt if you don’t have access to the system? The answer is with installation disk. You need to get yourself an installation disk with your operating system, then boot through it and enter the Recovery Environment (Windows RE), which contains many useful tools for restoring the operating system.
Once you have a disk (or USB storage), boot through it, having previously set the desired boot order in the BIOS. As soon as a window appears in front of you with a button that starts the Windows installation process, follow these steps:
- click on the “System Restore” button;
- Check the box next to “Use recovery tools to help fix problems starting Windows. Select the operating system to restore";
- select Windows 7 from the list below and click on the “Next” button;
- from the list available tools select "Command Line";
- run the following two commands in the console:
- bcdedit /deletevalue (default) numproc
- bcdedit /deletevalue (default) truncatememory
- Once you finish running the commands, restart your computer and remove the Windows installation media from the system.
Your operating system should now boot without any problems, and the Blue Screen of Death 0x00000074 has been fixed.
One of the most unpleasant (and also critical) failures is the appearance at the start stage operating system with the issuance of the stop code BAD_SYSTEM_CONFIG_INFO in the message. Windows won't boot, and there seems to be nothing that can be done because a boot violation is detected every time it starts. However, you shouldn’t give up, because there is a way out. Below are several simple methods, which are guaranteed to correct the situation (however, depending on what was the root cause of the errors). They may seem somewhat complicated to the average user, however, if the OS does not boot under any pretext, they cannot be avoided, since their use makes it possible to eliminate such unpleasant situations. However, first things first, but first let’s find out what kind of failure this is and why it occurs.
BAD_SYSTEM_CONFIG_INFO: what is this error?
Firstly, it’s immediately worth noting that this glitch appears in almost all recent Windows systems, starting from the seventh version. But what does the stop code in the message indicate?
The BAD_SYSTEM_CONFIG_INFO error (Windows 8 or any other modification) directly indicates the impossibility of initializing the system configuration (both hardware and software). As possible reasons The occurrence of such a situation in most cases is called corruption of the bootloader service (NTDLR) and system files, incorrect work RAM sticks or others possible problems, related to them, failures when trying to force access to RAM, etc.).
BAD_SYSTEM_CONFIG_INFO: How to fix boot crash?
One of the main methods for resolving the problem is standard OS recovery, which can be activated through the last known good configuration boot line at startup.
To access the boot menu at the very beginning of loading the OS, you must have time to press the F8 key several times (in Windows 10, to activate this access method, you need to use removable media with setting the legacy boot mode via the command line).
If the standard procedure does not work, and the BAD_SYSTEM_CONFIG_INFO error appears again, you must use the same menu, but in the boot options select start with support command line. However, it is 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 more advantageous because when loading into normal mode With hard drive with command line support, the BAD_SYSTEM_CONFIG_INFO error can still make itself felt.
After gaining access to the command console, the first thing you need to do is check system files and libraries for damage. This is done by running the sfc /scannow command.
If you download with support network drivers, you can try to perform a system restore online by using the command shown in the image above.
Using the Command Line in Safe Mode
However, even after performing such operations, a BAD_SYSTEM_CONFIG_INFO failure may appear when attempting to restart with a normal system boot. In this case (again through the boot menu by pressing the F8 key), you need to start in safe mode.
If the download goes well, the command console call is used again, in which the two lines shown in the image above are written. After confirming their completion, you can restart the operating system in normal mode.
But the troubleshooting methods don’t end there. Since sometimes the appearance of a screen can actually be associated with problems with the RAM, in most cases it is recommended to remove the strips from the slots on motherboard one at a time, and then check whether the system can start. If a faulty unit is identified, you will either have to simply throw it away or replace it with a similar one.
In some situations where the system may have been subject to viral effects, it is advisable to use disk anti-virus scanners (for example, Rescue Disk from Kaspersky Lab), which have their own means of loading before the OS starts and are capable of detecting even deep hidden viruses(and even in RAM).
If the failures are due to a damaged bootloader, it may be possible to fix it or even completely rewrite it via 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 is better to perform most actions by booting from recovery media and calling the command console, which is the first and most indispensable tool for eliminating most known system errors during boot.
However, it also happens that the screen appears, remains for some time, and then disappears. If the system somehow boots, and the cause of the error lies in dynamic libraries or system services, you can use the DLL Suite and MS FixIt utilities. The first loads damaged or missing DLL objects, the second serves as a fixer for problems with the operation of system services. By the way, it is also suitable for many other purposes, when the methods used by the user do not produce any tangible effect. But, as a rule, in our case, using the command console is the key to success. This is recognized by all experts and users who have encountered this problem.
Loading...
