- Mar 5, 2019
- 15
- 3
- 15
Recently, I suffered through the "BAD_SYSTEM_CONFIG_INFO" error that occurs when messing with the MSCONFIG processors
and something not being compatible when you change that (to 1 processor, or to 6; either way, I've read where some had the
same error going either way).
So, okay, apparently the only reason to even change the number of processors in the MSCONFIG (Boot...Advanced) area is to
make the computer boot faster and utilize all the processors/cores you have. And, memory, too--as there's a setting there for that
(0 meaning all of the memory being available). But more modern BIOSes and computers automatically take care of that, I guess.
Anyway, I got the error after changing the number of processors to 6 (as I have a six-core Ryzen 5) and set memory to 0 (to use
all of my 32GB of RAM). Rebooted, and it wouldn't go back into Windows 10. Tried EVERYTHING that I read online about it
(using another computer, of course, which I fortunately have). Did the Repair attempts, the roll-back of earlier Restore Points,
etc. Nothing worked. It would not boot, would just go back into the error screen (blue) and route you this way or that to try
and troubleshoot.
Well, I wound up biting the bullet and re-installing Windows 10. And only now did I stumble across the solution, so I thought
I'd pass it along. I did a search on here and saw that MANY people have had this problem over the last few years.
Here's the page (you may have to use Translate, for English):
https://nilcemar.blogspot.com/2012/04/corrigir-badsystemconfiginfo-no-windows.html
Here's the relevant, most important quote:
"
Just get to the Command Prompt any way you can, and type in what's in bold above.
It gets rid of the setting in MSCONFIG, if you put one there and your Windows messed up because of it.
Once I got Windows 10 back up, as I've been installing new programs and such, I've also been making
more backups, and even a DVD Repair Disc, just in case I ever have to catch back up after such an error.
I've left MSCONFIG alone now, even knowing it's bound to say only 1 processor, when I have 6. I never
had a problem with it before, when setting earlier Windows versions to something (like 2, for a dual-core
Athlon or something). Just sometimes a motherboard or something doesn't like it. And, I'm not too
worried about it, I have Windows booting in 10-to-15 seconds (and can probably tweak it faster
outside of MSCONFIG).
At any rate, wish I had known of this guy's solution the other day.
and something not being compatible when you change that (to 1 processor, or to 6; either way, I've read where some had the
same error going either way).
So, okay, apparently the only reason to even change the number of processors in the MSCONFIG (Boot...Advanced) area is to
make the computer boot faster and utilize all the processors/cores you have. And, memory, too--as there's a setting there for that
(0 meaning all of the memory being available). But more modern BIOSes and computers automatically take care of that, I guess.
Anyway, I got the error after changing the number of processors to 6 (as I have a six-core Ryzen 5) and set memory to 0 (to use
all of my 32GB of RAM). Rebooted, and it wouldn't go back into Windows 10. Tried EVERYTHING that I read online about it
(using another computer, of course, which I fortunately have). Did the Repair attempts, the roll-back of earlier Restore Points,
etc. Nothing worked. It would not boot, would just go back into the error screen (blue) and route you this way or that to try
and troubleshoot.
Well, I wound up biting the bullet and re-installing Windows 10. And only now did I stumble across the solution, so I thought
I'd pass it along. I did a search on here and saw that MANY people have had this problem over the last few years.
Here's the page (you may have to use Translate, for English):
https://nilcemar.blogspot.com/2012/04/corrigir-badsystemconfiginfo-no-windows.html
Here's the relevant, most important quote:
"
- On the screen that appears on the command prompt, type bcdedit / deletevalue {default} numproc and give <enter>.
- Enter now: bcdedit / deletevalue {default} truncatememory and give <enter>.
- Close the command prompt.
- Restart your computer and voila!
- Life saved without formatting the windows !!
Just get to the Command Prompt any way you can, and type in what's in bold above.
It gets rid of the setting in MSCONFIG, if you put one there and your Windows messed up because of it.
Once I got Windows 10 back up, as I've been installing new programs and such, I've also been making
more backups, and even a DVD Repair Disc, just in case I ever have to catch back up after such an error.
I've left MSCONFIG alone now, even knowing it's bound to say only 1 processor, when I have 6. I never
had a problem with it before, when setting earlier Windows versions to something (like 2, for a dual-core
Athlon or something). Just sometimes a motherboard or something doesn't like it. And, I'm not too
worried about it, I have Windows booting in 10-to-15 seconds (and can probably tweak it faster
outside of MSCONFIG).
At any rate, wish I had known of this guy's solution the other day.
Facebook
Twitter
Instagram