Recovering SSD with bad blocks?

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 54
    Windows 10 64 Version 10.0.18363.628
    Thread Starter
       #21

    I ran the SFC Offline:

    Recovering SSD with bad blocks?-2020-01-28-11.57.35.jpg

    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:
    Recovering SSD with bad blocks?-2020-01-28-14.59.26.jpg

    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.
    Recovering SSD with bad blocks?-2020-01-28-15.08.16.jpg

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

    Do I need to fix this?
      My Computer

  2. topgundcp's Avatar
    Posts : 2,760
    MintMate19x64 Win10Prox64
       #22

    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.
      My Computer


  3. Posts : 54
    Windows 10 64 Version 10.0.18363.628
    Thread Starter
       #23

    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.
      My Computer

  4. topgundcp's Avatar
    Posts : 2,760
    MintMate19x64 Win10Prox64
       #24

    JeffFinnan said:
    RegBack (spelling) is empty.

    Curious, I looked in my notebook Regback directory. It is empty too.
    Yep, I know that in the recent version of Windows 10. They stop making backup of the registry. But was hopimg something is still there. 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.
      My Computer

  5. Compumind's Avatar
    Posts : 2,715
    Windows 10 Pro x64, Various Linux Builds, Networking, Storage, Cybersecurity Specialty.
       #25

    JeffFinnan said:
    Got new SSD. Copied the image from old SSD using intelligent sector copy while ignoring bad blocks.
    How do you know that those bad blocks that were ignored didn't contain critical data?

      My Computer

  6. topgundcp's Avatar
    Posts : 2,760
    MintMate19x64 Win10Prox64
       #26

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

    That's what sfc does. Fixing and replacing corrupted/missing critical system files. Look at his screen shot.
      My Computer


  7. Posts : 54
    Windows 10 64 Version 10.0.18363.628
    Thread Starter
       #27

    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:

    Recovering SSD with bad blocks?-installsubfolders.jpg

    If one works through them to the config folder there is in folder 1:
    Recovering SSD with bad blocks?-installsubfolder1config.jpg

    And for folder 2:
    Recovering SSD with bad blocks?-installsubfolder2config.jpg

    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
      My Computer

  8. topgundcp's Avatar
    Posts : 2,760
    MintMate19x64 Win10Prox64
       #28

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

    Recovering SSD with bad blocks?-2020-01-28_232427.jpg
      My Computer


  9. Posts : 54
    Windows 10 64 Version 10.0.18363.628
    Thread Starter
       #29

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

    Recovering SSD with bad blocks?-2020-01-28_232427.jpg
    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:
    Recovering SSD with bad blocks?-configssd.png

    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.
      My Computer

  10. topgundcp's Avatar
    Posts : 2,760
    MintMate19x64 Win10Prox64
       #30

    Last try: Rebuild the BCD (boot config. data). Also restore all files that you made backup in config folder.
    Boot up KHYI's WinPE. Click on the menu and look for Disk Management, run it and identify the disk # of C drive.
    Open admin command and type:

    diskpart
    select disk # ====> where # is the disk of C drive
    list par ====> identify the EFI system partition
    select par # ====> where # is par # of EFI System
    assign letter=Z
    exit

    then type:
    bcdboot C:\Windows /s Z: /f UEFI ====> put space in between options /s and /f
      My Computer


 
Page 3 of 4 FirstFirst 1234 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 06:41.
Find Us




Windows 10 Forums