BAD_SYSTEM_CONFIG Blue Screen on Startup

[Jenjar]

Hello, I have had this PC for a while now, Since July in fact. It was built by Cyberpower and it has an MSI B250M Bazooka motherboard in it, and for the past couple of weeks every time I would turn it on I would get a blue screen that read "BAD_SYSTEM_CONFIG". I have heard that uninstalling one of the programs MSI has fixes the error, and I just done that but I do not know if it fixed it yet.

Today was different, Normally it gives me the blue screen and then it just goes right on to the windows homescreen after it collects data, but today it said the system did not start right and it put me in the automatic repair section, then it let me click the option "Continue to Windows 10".

So, Does anyone have any idea of what could be causing my issue? I went on Live Chat with CyberPower and they just told me to call a number, and then that number did not work, and then I had to call another different number (I really do not recommend Cyberpower). They told me to leave a message, I did and it has been about a week and I have not yet heard back from them.

Thanks.

[RadiatingLight]

probably a borked windows install.

clean install will almost definitely fix the issue.

other than that, I don't really know any other solution.

[Hiitchy]

Usually BAD_SYSTEM_CONFIG_INFO has to do with critical information in your registry being corrupted by itself, or containing values in places where it shouldn't be. The best thing to do is what RadiatingLight suggested, unless you're some tech guru that likes going through the local machine and finding what values are causing it crash... Don't waste your time doing that. Just clean install.

[Jenjar]

5 minutes ago, RadiatingLight said:

probably a borked windows install.

clean install will almost definitely fix the issue.

other than that, I don't really know any other solution.

1 minute ago, Hiitchy said:

Usually BAD_SYSTEM_CONFIG_INFO has to do with critical information in your registry being corrupted by itself, or containing values in places where it shouldn't be. The best thing to do is what RadiatingLight suggested, unless you're some tech guru that likes going through the local machine and finding what values are causing it crash... Don't waste your time doing that. Just clean install.

Its odd. It did it the first time I started it up today and then it just let me continue right on to windows 10, I tried to shut off the PC and restart it a couple times after and the error never came back up, and some days the error happens on startup and then other days the PC runs just fine.

 

If it keeps doing it I'll likely just get a fresh install of Windows. I already have the files on a flash drive ready to go from my friends PC when his windows went back.

 

[jj9987]

Can you get into Safe Mode? Did you try Startup Repair?

[Jenjar]

10 minutes ago, jj9987 said:

Can you get into Safe Mode? Did you try Startup Repair?

It just let me go right into Windows after. Cyberpower picked up today and they also said just to do a fresh install, the next time the error happens I will have a USB drive ready to do that.