Bad System Config Info - unable to fix via RebuildBCD

spongebot64 · 16 Jun 2017

Recently, I was browsing YouTube on my desktop when all of a sudden the power went out - causing a hard shut down. Upon turning it on, it seemed to load longer than usual, before throwing a BSOD with Bad_System_Config_Info. Restarting it, a different one came asking for recovery media to be use for troubleshooting. As I looked through online guides, it seems that, somehow, the Boot Configuration Data was corrupted, and I am unable to "access devices" as the second blue screen indicated.

Using my recovery USB, I checked all volumes were assigned correct letters then tried using bootrec /scanos to ensure the BCD was still there, and /rebuildbcd finding it remained. Despite using the command, it brought the error "The requested system device cannot be found". Further reading has shown Windows RE not functioning fully in certain USB ports, yet switching from USB 3 to 2 somehow corrupted the recovery USB and wouldn't let it boot - prompting me to reinstall the media on it.

I'm still experimenting with other ports, sticking with USB 3 in case 2.0 ports actually affect the BCD on the recovery USB. If it fails, I'll try the 2.0 ports.

If the worst is expected and I have to reinstall Windows, I can resort to that, but that's at the detriment of having to reinstall everything even if they're on other drives.

dalchina · 16 Jun 2017

Hi, I would start with basic disk checks.

Please download and create Kyhi's boot disk at the top of the Software and Apps section here.
Boot your PC from it and run
HDTune - which offers a scan for errors too.
and
HDDScan - which includes a surface scan
and post the results.

If ok, please run Minitool Partition Wizard from Kyhi's disk and post a screenshot.

You can try using Macrium Reflect's Fix Boot utility, again from Kyhi's disk and see if there's any improvement when you try booting.

Try running chkdsk on your Windows partition and report the result.

If your C: is still intact and recoverable, but the hard disk damaged, or the above procedures fail to repair damage to other areas, then there is one more thing to do:

a. Create a disk image of C:
b. Reinstall Win 10
c. Replace the newly created Windows partition by restoring the image of your old C:
d. Run Startup Repair.

spongebot64 · 16 Jun 2017

After having run HD Tune, it's recognised around 1.8% damaged blocks, and performing a benchmark immediately brought an error stopping it. Running HDDScan's surface test as I write.

spongebot64 · 16 Jun 2017

Read and Verify Surface tests complete, Read found bad blocks. Advice to take from here?

dalchina · 16 Jun 2017

HDTune also looks at SMART params- see if any show as not OK.

The drive is suspect at least. The question that follows is whether C: is recoverable.
One quite easy way to find out is to try creating a disk image of just C: - no others- using Macrium Reflect.

If any part is unreadable or corrupted, MR will fail with a CRC error.

That's the next step, and if that's ok, then you'd need a new disk and follow the outline steps I gave above.

We strongly and repeatedly recommend the routine use of disk imaging; having a maintained and updated image set means you could readily recover from this by restoring your image to a new disk.

spongebot64 · 18 Jun 2017

Tried Macrium and it gave me an MFT error. One chkdsk /r later, and the entire C: drive is backed up in an image. Should I be looking for a replacement primary drive for now?

dalchina · 18 Jun 2017

Have a look at the SMART params.

That you've been able to create an image suggests a lot of the drive is good- but you still presumably have an unbootable PC due to corruption elsewhere.

Safest way forward is a new drive. Then you can choose between a clean install, and replacing the newly created C: with your restored image. You may be lucky and have everything back up and running ok.

If you can run Hard Disk Sentinel at some point on your old drive, that gives a very clear indication.

spongebot64 · 19 Jun 2017

Was unable to run Hard Disk Sentinel because icmp.dll was missing. Ran CrytsalDiskInfo and that too showed the drive heath was fine. Formatted the partition where Windows was, then restored the disk image; another HD Tune test showed only one block damaged.

Should I try formatting the entire disk and repeating the steps or should I remain cautious?

dalchina · 19 Jun 2017

If Windows is booting ok, that's a good sign- I assume it is.

However
Attachment 140223
I wonder about your missing dll.
Try running
SFC /SCANNOW from an admin command prompt.

You should also check you can access recovery options (Recovery partition) e.g. by SHIFT + left click restart and navigating the menus to e.g. Safe Mode.

You have one other possible check I can think of- using a partition manager such as Minitool Partition Wizard, you can rt click a partition and do a surface test specifically on that partition. You can do that for each of the partitions required for Windows.
Attachment 140221

You're aware of disk imaging, so maintain a good routine.
Note to image Windows, in Macrium Reflect it's e.g. option Backup, Windows Backup - note all the relevant partitions are ticked.

spongebot64 · 19 Jun 2017

Tried sfc /scannow. Brought up: Windows Resource Protection could not perform the requested operation.

Tried minitool partition manager as well, but said it can't be run in Windows PE unless registered.