BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow

Page 6 of 7 FirstFirst ... 4567 LastLast

  1. Posts : 31,471
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #51

    Telenochek said:
    The CBS Manifest corruption count is now at 0...
    That's great news. Now let's see if @philc43 can sort out the remaining errors for you.
      My Computers


  2. Posts : 31
    windows 10 32bit
    Thread Starter
       #52

    Hi guys - I have not heard any responses for a week.
    Please let me know what to try next - should I try replacing the .dlls with hash mismatches in the DISM log.
      My Computer


  3. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #53

    Sorry for the long delay. I was away for a while and then lost track of this one. Is Windows working normally or are you having BSOD errors? I would suggest you post a new set of logfiles if you are still getting errors.
      My Computers


  4. Posts : 31
    windows 10 32bit
    Thread Starter
       #54

    Hello Phil, welcome back!
    Nothing changed from the last DISM log posted, which was dism9.txt
    I still cannot boot the machine - with all the original symptoms.
    The only thing that happened between the original post and dism9.txt is that we cleaned up all the errors associated with MUM corruption by copying the correct .cat and .mum files from a machine with identical version of windows install on it.

    While I have purchased a new PC - I still need the old one working, as there is too much unique and old scientific software on it, that I would need to run on the original PC, before I can try running on the new PC. For example, a number of files which contain the settings - can only be opened with the old software.
    MS Office and all the currently supported software is relatively easy to install on the new PC, but the old files & models - not so easy, it's all proprietary formats. I need to open them first to get some of the numbers.

    Please let me know where to go from dism9.txt
    Thanks!
      My Computer


  5. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #55

    In posts #4 and #5 the Kyhi bootable rescue disk was used.

    See if you can perform any of these on the disk:

    1) HD Tune: (free edition)
    https://www.hdtune.com/
    Post images of the test results for these tabs:
    a) Health (SMART)
    b) Benchmark
    c) Full error scan

    2) Disk management > widen each status and volume columns so that the characters in each row are in full view and no letters are cut off > post an image into the thread
    Disk Management - How to Post a Screenshot of | Windows 10 Tutorials

    3) See if you can retrieve the chkdsk reports from the event viewer > post a one drive or drop box share link into the thread
    Read Chkdsk Log in Event Viewer in Windows 10 | Windows 10 Tutorials
      My Computer


  6. Posts : 31
    windows 10 32bit
    Thread Starter
       #56

    @zbook are you sure your post is for me?
    Have you read the rest of the thread?
      My Computer


  7. Posts : 41,413
    windows 10 professional version 1607 build 14393.969 64 bit
       #57

    The thread had been quite and I had not remembered whether the hardware and partitions had been checked.
    If they had been checked then you can continue troubleshooting the corruption
      My Computer


  8. Posts : 31
    windows 10 32bit
    Thread Starter
       #58

    Yes - the SSD has been checked.

    I verified SSD health using GParted with smartmontools included.
    Both the short offline and long offline tests reported that they completed without errors.
    sudo smartctl -t short -a /dev/sda and
    sudo smartctl -t long -a /dev/sda
    Wear_leveling_cnt is at 97%, so this is practically a new drive.

    This is consistent with my expectations, as I swapped in an SSD instead of HDD about 2-3 years ago.
      My Computer


  9. Posts : 5,169
    64bit Win 10 Pro ver 21H2
       #59

    Hello Telenochek,

    Looking at the DISM log it seems that you have corrupted or are missing some of the provider.dll files and this probably causes the remaining errors.

    Code:
    2018-06-19 23:44:21, Warning               DISM   DISM Provider Store: PID=1996 TID=2000 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2018-06-19 23:44:21, Warning               DISM   DISM Provider Store: PID=1996 TID=2000 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    Can you start by trying to copy those over from your good matching Windows installation and seeing if it helps? The strategy is like you did before for finding and replacing the missing packages.


    I will also go back over the earlier posts and see if there is anything else we need to explore - I am convinced you may also have some boot file location problems too and will need to repair them.
      My Computers


  10. Posts : 2
    Windows 10 64-bit
       #60

    Hello!

    Now I've been following this thread recently today, and I am really curious to know if the OP was able to resolve the DISM issues?

    I also am trying to repair my windows 10 with similar issues.

    Thanks!
      My Computer


 

  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 03:07.
Find Us




Windows 10 Forums