Random "Bad system config info" errors after system restarts

Coach81 · 21 Jul 2018

Good day

I was hoping i could be assisted on the above matter.

I started getting "bad system config info" errors on startup recently. However, instead of my system constantly relooping at startup never to get into windows the issue does resolve itself at the BSOD then my system restarts again and i am able to get into windows from there no problem.

The problem is the issue is very random and difficult to replicate and the only thing in common is that it only happens on system reset or boot-up. Ive read help forums about booting into safe-mode and using the command-prompt to do chkdsk's and other diagnostics but those only seem to really help if you cant get into windows in the first place whereas i am able to.

I am wondering if i should be worrying about it as it doesnt happen after every restart. However the randomness does concern me a bit bearing in mind my system is only 2 weeks old. If there are any tips or advice that anyone could impart i would be grateful.

Kind regards

Ztruker · 21 Jul 2018

Dump shows:

Code:

BugCheck 74, {2, ffffe50da4637970, 2, ffffffffc000012d}
Probably caused by : ntkrnlmp.exe ( nt!CmpLoadHiveThread+b60f0 )

Code:

BAD_SYSTEM_CONFIG_INFO (74)
Can indicate that the SYSTEM hive loaded by the osloader/NTLDR
was corrupt.  This is unlikely, since the osloader will check
a hive to make sure it isn't corrupt after loading it.
It can also indicate that some critical registry keys and values
are not present.  (i.e. somebody used regedt32 to delete something
that they shouldn't have)  Booting from LastKnownGood may fix
the problem, but if someone is persistent enough in mucking with
the registry they will need to reinstall or use the Emergency
Repair Disk.

If you are not messing with the registry then running chkdsk c: /f from a elevated command prompt is the first thing to do. It will ask if you want to run on next boot, reply Y then restart. If it reports/corrects any errors, then run it again.

I see this in Event viewer log:

Code:

Event[2443]:
  Log Name: System
  Source: Microsoft-Windows-Kernel-Boot
  Date: 2018-07-18T13:00:51.050
  Event ID: 29
  Task: N/A
  Level: Error
  Opcode: Info
  Keyword: N/A
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: DESKTOP-DOS8QLP
  Description: 
Windows failed fast startup with error status 0xC00000D4.

Disable Fast startup, see if that resolves the problem. How to Turn On or Off Fast Startup in Windows 10

Coach81 · 21 Jul 2018

Hi There

Thank you for the quick response.

Chkdsk log file didnt contain any errors so i went with disabling fast-startup. Hopefully after a few restarts it shouldnt be an issue anymore.

Kind regards

BSODHunter · 23 Jul 2018

There a lot more things which should be checked:

1) There is Software installed which is known for causing bluescreens and crashes:
- MSI Afterburner
- MSI Command Center
- MSI RamDisk (not good!)
- Unigine Heaven Benchmark

2) There are entries for AVAST and NORTON. You should only use one security software at the same time.

3) Since the registry and maybe system files are corrupted, running chkdsk is not enough. Running sfc and dism should be your next steps to really repair system components:

Repair Windows Filesystem:

1. Open an elevated command prompt.
2. In the elevated command prompt, type these five commands below, and press Enter:

dism /Online /NoRestart /Cleanup-Image /RestoreHealth
dism /Online /NoRestart /Cleanup-Image /StartComponentCleanup
sfc /scannow
chkdsk C: /F /R /X
fsutil dirty set C:

SFC:
The SFC command scans the integrity of all protected system files and replaces incorrect versions with correct Microsoft versions.
DISM:
If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem.
For example, you would use DISM to fix Windows component store corruption when a sfc /scannow command is unable to repair corrupted or modified system files because the component store (source) is corrupted.
CHKDSK:
Checking your drives for errors every once in a while can help fix some performance issues. Drive errors can usually be caused by bad sectors, improper shutdowns, bad software, corruption, physical damage, etc...

Coach81 · 23 Jul 2018

Good day

Thank you for the additional information.

1. I removed the MSI apps listed above. Do all MSI apps cause these problems and are they worth installing? Majority of MSI apps i install from Live Update 6.
2. Yeah removed Norton, actually not sure how it got there must have installed it by mistake from cd that came with motherboard.
3. Did all of those commands, nothing unusual came up. The "StartComponentCleanup" command took a little bit of time although also not much out of the ordinary.