Fix BAD SYSTEM CONFIG INFO error in Windows 10 [BSoD Help]

Blue Screen of Death errors, are one of more serious problems on Windows 10. They can be caused by incorrect system settings, software, or even by faulty hardware. Don't worry because we've got the solution in the article below.

BSoD errors are less frequent nowadays but if you come across one, we.ve got the solution in our troubleshooting BSoD category.

System errors happen pretty often but you will most likely find a solution in our System Errors hub.

We wrote a plethora of articles about Windows 10 errors so check out our Windows 10 errors hub.

Fix the BAD_SYSTEM_CONFIG_INFO error resulting in BSOD on Windows 10 by following instructions we provided here.

Blue Screen of Death errors, also known as STOP errors, are one of more serious problems on Windows 10. These errors can be caused by incorrect system settings, software, or even by a faulty hardware.

Since these errors can so problematic, today we’re going to show you how to fix BAD_SYSTEM_CONFIG_INFO BSoD error.

BAD_SYSTEM_CONFIG_INFO can cause various problems on your PC, and in this article, we’re going to show you how to fix the following issues:

Bad_system_config_info registry – According to users, sometimes this error can occur due to problems with your registry. Several users reported that registry corruption was the main cause for this error.

Bad_system_config_info RAM – Your hardware can also cause this problem to occur. According to the users, the most common cause for this problem is faulty RAM.

Bad system config info on startup, boot – According to users, this error often appears as soon as your PC boots. This can be a big problem since your PC will restart as soon as this error appears.

Blue screen of death bad_system_config_info – Many users reported this Blue Screen of Death error on their PC. In most cases this error is caused by faulty hardware or a bad driver.

Bad_system_config_info after update – Several users reported this error message after installing an important update. If that’s the case, you can fix this problem simply by removing the problematic update.

Bad_system_config_info hard drive, HDD – Hardware failure can often cause this problem to appear. According to users, this error usually appears if your hard drive is faulty.

Bad system config info loop – In some cases your PC might end up in a reboot loop due to this error. Several users reported that their PC can’t boot at all because of this error.

Bad_system_config_info ntoskrnl.exe, ntfs.sys, classpnp.sys, rdyboost.sys – This error message will often inform you which file caused the error to occur. Once you know the file name, you should be able to find the application or device that is causing this error.

Fix BAD SYSTEM CONFIG INFO BSoD error

Solution 1 – Update your drivers

Outdated or incompatible drivers can cause many issues. For example, if your drivers don’t work, you won’t be able to use certain hardware, and in worst case scenario, you’ll get a BSoD error such as BAD_SYSTEM_CONFIG_INFO.

Since many Blue Screen of Death errors are commonly caused by drivers, we strongly advise you to update your drivers as often as you can. In order to avoid all BSoD errors, be sure that all major components are up to date with latest drivers.

Downloading drivers is fairly simple, and all you need to do is to visit your hardware manufacturer’s website, locate your device and download the latest drivers for it.

After installing the latest drivers, BSoD errors should be resolved. Bear in mind that you’ll have to update as many drivers as you can in order to successfully fix this problem.

In order to fix BAD_SYSTEM_CONFIG_INFO and many other BSoD errors, it’s important that you update all drivers on your PC.

This tool is approved by Microsoft and Norton Antivirus. After several tests, our team concluded that this is the best automatized solution in order to prevent permanent damage to your system by downloading and installing the wrong driver versions.

Solution 2 – Use bcdedit command

BAD_SYSTEM_CONFIG_INFO error can often appear if your system configuration isn’t correct.

If your system isn’t properly configured, and the number of processors and amount of memory in the configuration file doesn’t match the correct value, that will cause BAD_SYSTEM_CONFIG_INFO error.

To make things even worse, this error will prevent access to Windows 10 completely. Although this sounds rather serious, we can easily fix this issue by doing the following:

Restart your computer while it boots. Repeat this step until you start Automatic Repair.

Choose Troubleshoot > Advanced Options > Command Prompt.

Once the Command Prompt starts, enter the following lines:

bcdedit/deletevalue {default} numproc

bcdedit/deletevalue {default} truncatememory

Close Command Prompt and try starting Windows 10 again.

FAQ: Read more about BAD_SYSTEM_CONFIG_INFO

What causes bad system config info?

Bad system config info error can be either caused by software or hardware. If the error is caused by hardware components, unfortunately, you will be forced to replace that particular component. The software problems that can cause this error can be faulty updates and software incompatibility, corrupted registry, incorrect Boot Configuration Data (BCD) file, corrupted MBR, bad drivers and other.

How do you reset your settings on Windows 10?

Press Windows + X keys and select Run. Enter msconfig in the Run box and hit Enter. On the Services tab of the System Configuration dialog box, select the Hide all Microsoft services checkbox, and click Enable all. On the Startup tab of the System Configuration dialog box, click on Open Task Manager. On the Startup tab in Task Manager, for each item from the list, select it and then click Enable. On the Startup tab of the System Configuration dialog box, click OK. Finally, restart the computer.

How do I fix the blue screen of death?

There are a lot of BSoD errors out there so you will have to read carefully the error code displayed on the screen while the BSoD is making its appearance and search for that specific code. However, you can try to run your computer in Safe Mode and see if the problem manifests again.