How to Fix ‘Bad System Config Info’ Error in Windows 10

Bad System Config Error Featured

Bad System Config Info is a common bug check error on Windows systems, caused mainly by a malfunctioning of the system and registry files or the Boot Configuration Data (BCD) file. Some boot order files in the BCD, or even some older ones, may conflict with newer, stable files. When this happens, the error otherwise known as the Blue Screen of Death (BSoD) occurs.

The bug check error can also be caused by:

  • faulty hardware
  • incorrect system settings
  • a bad driver
  • installing an important update

However, most error messages will often have a description of what the problem may be. Below are some tried and tested solutions to help you fix a Bad System Config Info error in Windows 10.

Check your RAM and Hard Drive

For some, it may seem daunting to look inside your PC and start twiddling around with the physical components. However, the health and fitting of your RAM and hard drive can be the cause of the bad system config info error.

Cpu Performance Ram
Your RAM sticks will look a bit like this. Make sure they’re nice and snug in their slots

If you’re comfortable with opening up your PC, you can take a look inside to make sure that your RAM is correctly fitted into the slots and that your hard drive SATA cables are properly connected, too. These checks shouldn’t take more than a couple of minutes.

Assuming your RAM and hard drive are properly fitted, you should then check on the health of your RAM and health of your hard drive, both of which we have guides for here on the site. If you get back bad results on either front, this could be causing the errors, and it may be time to look into replacing the relevant components.

Update or Reinstall Drivers

Incompatible or outdated drivers are a source of several issues. The worst thing bad drivers can do is bring up BSoD errors, such as the Bad System Config Info.

To resolve this, you should go to the Window Device Manager (Win key, then type device manager). In the Device Manager window, click “Action -> Scan for hardware changes,” then look to see if any yellow exclamation mark symbols appear next to any of the devices. (You’ll need to click the drop-down icons to seek them out.)

Fix Bad System Config Info Windows 10 Update Drivers

If you find any misbehaving drivers, right-click them, then click “Update driver.” If the problem continues, right-click the driver, then click “Uninstall device.” If it’s a system device (like the driver for your onboard ethernet port), it will reinstall automatically after rebooting your PC.

If it’s a third-party driver, it will reinstall after reconnecting the device in question or after reinstalling the software.

bcdedit command

Quite often the Bad System Config Info error can appear when system configuration is incorrect or not configured properly. Additionally, if the memory and processors in the configuration file have the wrong value, the error will appear as well, preventing access to Windows 10.

To resolve this, trigger Windows 10 to access the Advanced Startup menu:

1. Click Start.

2. Click Power.


3. Press and hold Shift and click Restart.

4. The “Choose an Option” screen will display. Select Troubleshoot.


5. In the Troubleshoot window, select “Advanced Options.”


6. In the Advanced Options window, select Command Prompt.


7. Your computer will restart and then display the Command Prompt blue screen. You’ll be asked to select an account to continue. Press Enter and then key in your password for that account.

8. Enter the following lines once Command Prompt starts:

9. Close Command Prompt.

10. Start Windows 10 again.

Fix BCD file

If your BCD file is corrupt or damaged, the Bad System Config Info error may appear and deny you access to Safe Mode and Windows 10 altogether.

To resolve this, you need your bootable USB flash drive with Windows 10 or the installation DVD. You can also use the Media Creation Tool if you don’t have a bootable USB drive.

Here’s what to do next:

1. Insert the bootable Windows 10 installation DVD and boot from it.

2. Windows 10 setup will begin.

3. Click Next.

4. Click “Repair your computer.”

5. Select “Troubleshoot -> Advanced Options -> Command Prompt.”


6. Enter the following lines when Command Prompt starts. (Press enter after each line to execute it.)

7. Close Command Prompt.

8. Restart your computer.

Note: the last command you enter will delete and then recreate Master Boot Records. Be careful using it.

Fix the Registry

There are specific registry issues that can bring up the error, but you can repair the registry to resolve it by following these steps:

1. Boot from the Windows 10 installation DVD.

2. Select “Troubleshoot -> Advanced Options -> Command Prompt.”

3. Enter the following lines when Command Prompt starts. (Press enter after each line to execute it.)

Note: the folders of each of these commands are renamed as you press Enter, and once this is done, Windows 10 won’t use them again. They can be deleted, but you’re better off renaming in case you need to do a system restore much later.

4. Next, enter the lines below into Command Prompt:

This process copies the registry’s backup and replaces old files. Close Command Prompt and restart your PC.

System Restore

If the other methods don’t help, this may be one of your last two solutions to try.

1. Click Start.

2. Click Power.


3. Press and hold Shift and click Restart.

4. Select “Troubleshoot -> Advanced Options -> System Restore.”


5. Choose your username.

6. Follow the on-screen prompts.

7. Select the restore point you want.

8. Click Next and wait for the process to complete.

Reset Windows 10

This is the last solution to try if none of the others worked. Before resetting, create a backup because once you reset Windows, all files will be deleted from the C partition.

1. Click Start.

2. Click Power.

3. Press and hold Shift and click Restart.

4. Select “Troubleshoot -> Reset this PC.”


5. Select “Remove everything -> Only the drive where Windows is installed -> Just remove my files.”

6. Click Reset and wait for it to complete the process. You’ll have a fresh Windows 10 installation once this is done.

The reset should fix the problem if it was related to your PC’s software.

Despite its problems, we think Windows 10 remains a great OS. But if you run into other issues like malfunctioning headphones or abnormally high CPU usage in Windows 10, we’re here to help.


  1. Hi Mike,

    Thanks for this solution, the ‘truncatememory’ was what I needed.
    I had come across the BAD_CONFIG_INFO BSOD last night, because I fooled around with msconfig and changed the processor and memory. I tried fixing it via msconfig and safeboot, but both options failed. Thanks to some other sites I had already done the ‘numproc’ and reset the Number of Processors. I was confused about the ‘truncatememory’ until I came across this thread. Now Im writing this comment from my windows 8.1. YAY!
    I knew I had to reset those values in msconfig, but didnt know how to reset “Maximum
    Memory”. Tried to launch msconfig from startup-repair menu. It kept saying “run from user account with administrator privileges”, but I already am the owner and Admin. Microsoft done some pretty dumb stuff by creating a separate Administrator account that users cannot access in emergencies, which the account was built for. Atleast in my case, I couldnt log into my admin account when I needed to so badly, even though it was active before this error. Microsoft should give the user with admin ability full control Or atleast make cmd able to launch items with admin privileges even from boot options.

    Hope more people find this thread, as I saw a huge number of complaints in many windows forums, from windows 7 to latest versions of 10.

  2. Hi Mike, I wish I had found your solutions first – I got ambitious and tried tweaking my Ram settings to use an overclock on an older PC and it kaked Windows 10 booting. Setting it back to stock Ram speed did not resolve the issue.

    First fix attempt I tried (which I got told elsewhere) was to do a System Restore, which successfully applied itself but did not work for fixing the BAD CONFIG – BSOD, after reading your article and since I knew I had been fiddling with Ram I just tried your suggestion for BCDedit deleting the truncatememory setting and Viola – everything booted back up! – unfortunately since I did that system restore I had to redo a New Years resolution to do a Desktop cleanup that I had completed inbetween that system restore timeframe.

    I also wanted to mention that I fixed a stability issue on an older DuoCore Quad system in MSCONFIG Boot Tab / Advanced by selecting # of processors (4) and ticking PCI Lock – this fixed many random Win10 freezing lockups for me. Hope that helps someone else.

    Also in that same MSCONFIG – BOOT Advanced options I have told it the Maximum amount of system Ram 8192 (8GB) but after restarting the setting is lost – interested if that is a bug or if Windows tries to redetect Ram size each time PC boots up.

    Anyways thanks a Million (thanks that is!) :)

Comments are closed.