Windows 10: BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow

Page 1 of 6 123 ... LastLast
  1.    20 May 2018 #1

    BSOD crash with CRITICAL_PROCESS_DIED cant boot or run sfc /scannow


    not sure I can run dm log collector from recovery console?

    My desktop PC with 32-bit Windows 10 has crashed at version 10.0.17134.0. It worked fine for a few days after the upgrade to version 10.0.17134.0, and I was not using the PC at the time of the crash. It now starts up "attempting automatic repair", "diagnosing your PC" and ending with "Automatic Repair couldn't repair your PC".

    My windows 10 installed on C: drive used to be version 10.0.17134.0 but is now 10.0.16299.15, after I tried going back to a previous version to try and fix the problem.
    I also have a 10.0.17134.1 version bootable USB drive, which is 0.1 newer than win 10.0.17134.0

    Things I've tried so far:
    1) Running ESET and Kaspersky anti-virus and anti-rootkit scanners from separate bootable USB drives. No problems found
    2) Standard windows Automatic repair from the C: drive, no luck
    3) Standard windows Automatic repair from a bootable USB drive, which has the latest edition of windows 10, no luck

    4) chkdsk /f /r from the system C: drive
    this refuses to run due to
    "Windows cannot run disk checking on this volume because it is write protected"
    I assume it is because I'm running recovery on it?

    5) chkdsk c: /f /r from the bootable USB drive works fine:
    “Windows has scanned the file system and found no problems”

    6) sfc /scannow from C:\windows\system32 - this fails without even trying to scan with the message "Windows Resource Protection could not perform the requested operation"

    I went into regedit, found that the ProgramFilesDir key was pointing to X:\Program Files, not C:\Program Files
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion]

    sfc /scannow now completes 100% (instead of reporting the error right away), however at the end it still shows the error below:
    "Windows Resource Protection could not perform the requested operation" after the 100% completion.

    I looked through the cbs.log and it looks like there are some hash errors found in dlls, but the dll fixes are not applied. On second, third, fourth SFC scans the same errors are found - hence confirmed that they are not fixed.


    7) sfc /scannow /offbootdir=c:\ /offwindir=c:\windows
    from USB bootable image, shows error:
    "Windows Resource Protection could not perform the requested operation"

    I was not able to get around the error, even though sfc /scannow at least executes to 100% completion from C: drive, but not from bootable usb.

    tried:
    ICACLS C:\Windows\winsxs , this completed fine,
    but SFC still reports
    "Windows Resource Protection could not perform the requested operation"

    8) from C:\windows\system32
    dism /online /cleanup-image /RestoreHealth

    This initially fails with error 50
    ‘Error 50 DISM does not support servicing Windows PE with the /online option’
    I'm able to get around this error by following instructions here, via regedit and WinNT key
    Fix: Error 50 DISM does not support servicing Windows PE with the /online option - Appuals.com

    However, once I get past error 50, I get another error after DISM completes with 100%
    DISM Error: 1, incorrect function
    I googled a variety of issues for errors inside the DISM .log , but didn't find anything actionable.

    Since the standard fixes don't seem to work, I thought it would be a good idea to get professional help here on the forums.

    It seems like fixing SFC /scannow would be the first priority.
    cbs.txt is attached from the sfc /scannow executed from C: drive

    Any help would be greatly appreciated!
    I don't want to do a clean reinstall at this time.

    Thank you,
    Tele
    BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow Attached Files
    Last edited by Telenochek; 20 May 2018 at 21:14.
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       26 May 2018 #2

    Hello Telenochek,

    Are you still needing help? Can you boot into safe mode and run the log_collector?
      My ComputersSystem Spec

  3.    26 May 2018 #3

    Hi Phil,

    Thank you for your response. Yes I do still need help.
    I can't boot into any kind of safe mode (with command prompt, with internet etc....). I can only get into recovery console and command prompt.

    I've tried a variety of things as outlined in my original post. Nothing too risky, just a variety of attempts to somehow get SFC.exe or DISM.exe to run properly, and to actually fix the errors found.

    Best regards,
    Tele
      My ComputerSystem Spec

  4. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       26 May 2018 #4

    A useful recovery disk with lots of tools built in for diagnostics can be found here:

    Windows 10 Recovery Tools - Bootable Rescue Disk

    Have a look through the thread and try out some of the tools to work on sfc and DISM
      My ComputersSystem Spec

  5.    28 May 2018 #5

    Hi - I downloaded the tools, but they pretty much report exactly the same problems as sfc /scannow and DISM.
      My ComputerSystem Spec

  6. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       28 May 2018 #6

    Do you have more than one hard drive attached? Has the boot record got messed up somehow? The EasyBCD tool on the recovery disk might have a boot repair function you could try.

    I not sure exactly what happens when you now try to boot - can you describe what you get in detail please.
      My ComputersSystem Spec

  7.    28 May 2018 #7

    Yes I do have another drive attached. Let me disconnect it.

    what happens currently at bootup is that there are a series of light blue Windows booting screens, as follows:
    "attempting automatic repair", "diagnosing your PC" and ending with "Automatic Repair couldn't repair your PC"
    Same as original post.

    So far the only difference between the original post and today is that I'm able to run 4) chkdsk c: /f /r from within the system drive. I think what fixed 4) is that I made sure to run chkdsk on a clean PC reboot. In all the previous occasions I ran it, I think I may have run another process such as redegit or other, and chkdsk was not able to dismount the volume.
      My ComputerSystem Spec

  8. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       28 May 2018 #8

    Sometimes the automatic repair has to run three times in succession to work but I guess you have already done that by now.

    The repair records the results in a logfile:
    C:\Windows\System32\Logfiles\Srt\SrtTrail.txt

    See if you can find it and review the contents.
      My ComputersSystem Spec

  9.    28 May 2018 #9

    Attached is the SrtTrail - not very informative, I'm afraid.
    Error 0x32 sees to be a generic message.
    BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow Attached Files
      My ComputerSystem Spec

  10. philc43's Avatar
    Posts : 3,590
    64bit Win 10 Pro ver 1809 Build 17763.1 and W10 Insider Build 18252
       28 May 2018 #10

    Only shows 1 repair attempt - try and do three in succession restarting the PC between each attempt.

    Run Startup Repair in Windows 10
      My ComputersSystem Spec


 
Page 1 of 6 123 ... LastLast

Related Threads
Hey there, computer overlords, Thanks for checking this out. TL;DR—BSOD, "INACCESSIBLE_BOOT_DEVICE" when updating to 1607. Restored from backup and tried again. Ran chkdsk. sfc /scannow fails (see log link). Drivers updated. I let Windows...
CRITICAL_PROCESS_DIED on boot in General Support
Hi. My mom's laptop is crashing on boot with a CRITICAL_PROCESS_DIED error. It boots in Safe Mode but most things are unresponsive: no windows menu, command prompt opens right away but admin prompt takes 10-20 minutes to open, so do task manager...
Hello! I've been having issues with a Critical_Process_Died BSOD for several weeks now and have already spent quite a bit of time troubleshooting it, to no avail. The start of my problems did not coincide with any major hardware or software changes....
Hello, I am having BSOD's again. I am getting the above error on the blue screen. It's worse now though because it never makes it past the "collecting data" it just freezes at 0%. After I shut it down and restart it manually, it gives me a...
Solved BSOD Critical_Process_Died in BSOD Crashes and Debugging
The OS (win10Pro) is an upgrade from Win7Ultimate and this BSOD issue only started happening this morning. Unfortunately, my last image is from Friday so I'm not sure that will be of any help either. The diagnostic file is attached. One thing that...
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 14:41.
Find Us