Recovering SSD with bad blocks?

I ran the SFC Offline:



It found corrupted files, But it did not save the log file. Therefore, I could not see what happened. Rerunning SFC showed no corrupted files.

I still got the BSOD. However, I notice that one of the screens in the restarts showed inaccessible boot device:


Now in my previous post on DISM, I had not noticed in Diskpart that List Volume shows drive C but does show it as boot device. I rechecked.


Drive C: should be showing Boot in info, right?

Do I need to fix this?

topgundcp said:

Try from command prompt:
cd C:\Windows\System32\config\regbak
The above folder is where the Registry backup store, find out if there's any files in this folder. If so, go back to config folder and rename all the files that exist in regbak. Once done, copy everything from regback folder to config folder then reboot.

RegBack (spelling) is empty.

Curious, I looked in my notebook Regback directory. It is empty too.

Compumind said:

How do you know that those bad blocks that were ignored didn't contain critical data?

Oh yeah, I assume that is where the problem arose. But I presume that files or partial files residing in those bad blocks are inaccessible.

- - - Updated - - -

topgundcp said:

It would not hurt if you want to copy the files from the installation Media, Use 7-Zip to open the install.wim or install.esd then copy these files from config folder.
Make sure you make backup of the current files first.

There was only the install.esd. There was a boot.wim. On decompressing the install.esd—It took a while—there were the multiple numbered subfolders:



If one works through them to the config folder there is in folder 1:


And for folder 2:


There are some size differences in the files in the configs folders. Which do I use?

then copy these files from config folder.

Assuming I have chosen the correct install config folder (1,2,3, etc.), is it these files BBI, etc. that I copy into the SSD config folder?

As always, thanks,
Jeff

topgundcp said:

1 is for Win 10 Home
6 is for Win 10 pro
Use the files:

Copied from folder 1. After rebooting into media disk, Diskpart > list volume, still does not show the c drive as a boot drive. Also rebooting into the SSD drive gives a new stop code: Critical Process Died, then reboots with a code of System Thread Exception and then Critical Process Died, the Thread Exception, rinse and repeat.

Interesting, if I use the Kythi boot and look at the config folder with Explorer it shows a bunch more files:


But only in this environment. If I take this config folder and look at on my laptop, it does not show all these hidden files, just the COMPONENTS, DEFAULT, etc.

Those .logX files appear binary if opened with notepad in WinPe.

When do I throw in the towel and do a fresh install? One thing that has been holding me back on this I have some older Adobe products that I might have difficulty reinstalling. Adobe might say those licenses have been used up.