BSOD on Startup, No successful boots BAD_SYSTEM_CONFIG_INFO 0x00000074

silekonn · 02 Apr 2016

Have tried Last Known, Safe w CP, bcdedit /set {default} numproc 2 and/or deleting that and truncatememory (which didnt exist), bootrec /fixmbr & /fixboot, chkdsk /f (and tried a full scan via wddiag, each no errors), and bluescreenview in a bootable liveos looking for the logs (they are not there or not in the std location, bsv only finds things from years ago). Any suggestions? I would provide any logs I can.

BorisTheAnimal · 03 Apr 2016

Hello silekonn and welcome to 7forums! :)

There is a known resolution for this problem and that is to use the "last known good configuration" and by accessing it, you will need to press F8 before the Windows logo, if you see the logo then you'll have to try again. If you have done it correctly you'll be represented with a screen like this:

Highlight LKGC and press enter!

Cheers, Boris :)

silekonn · 03 Apr 2016

Boris,
The first four words of the post refer to that. It does not resolve the issue. Any other suggestions?
Thank you,
Silekonn

BorisTheAnimal · 03 Apr 2016

Oh geez, I'm sorry musta overlooked those words, hehe. *blush*

Cause

The BAD_SYSTEM_CONFIG_INFO bug check occurs if the SYSTEM hive is corrupt. However, this corruption is unlikely, because the boot loader, known as NT Loader (NTLDR) in versions of Windows prior to Vista, checks a hive for corruption when it loads the hive.
This bug check can also occur if some critical registry keys and values are missing. Thee keys and values might be missing if a user manually edited the registry.

Resolution

Try restarting the computer by selecting "last known good configuration" in the boot options.

If the restart does not fix the problem, the registry damage is too extensive. You must reinstall the OS or use the Emergency Repair Disk (ERD) that you previously created by using the Windows Backup tool.

The above is taken from here:
Bug Check 0x74: BAD_SYSTEM_CONFIG_INFO

Boris :/

silekonn · 03 Apr 2016

I read that one previously and understand, however it is a bit vague/contradictory and I don't appreciate the ambiguity. "The registry damage is too extensive" doesn't say much of anything beyond 'they think it be broke.' The system restore was somehow turned off so there are no points from which to take a registry, the fact the article doesn't suggest checking for any other registry copies further detracts from the value the article should contain. I am considering the 'regback' copy, my understanding is that is an old version, maybe only one week. I will try this tonight. Suggestions are welcome.
T. I. A.
Silekonn