1. #1

    Critical_Process_Died and SFC corruptions.

    I got a blue screen today on windows 10. It told me a critical process had died, for some reason. My computer rebooted and now it is kind of broken. My home windows button does not work at all, most of my programs (for example skype) gives me strange error messages about some random windows files not being compatible etc.

    I first tried to Refresh windows 10 by doing a repair install, but i was only greeted with 2 options in the advanced start up. The continue arrow, and turn off icon. Both lacked text to describe them.
    So i tried to instead refresh windows by going to the options instead. This time i was greeted with the two buttons asking if i wanted to keep my data or not, but they were both completely blank without any text. I pressed the upper button because i wanted to keep my data, but that did not work either because it "Could not find the recovery environment."

    So i tried using sfc /scannow but it stopped at 33% every time because Windows Resource Protection could not perform the requested operation. I downloaded sfcfix and here i am, it found some corruptions it could not repair and here i am.

    SFCFix version 3.0.0.0 by niemiro.
    Start time: 2016-03-12 23:48:58.293
    Microsoft Windows 10 Build 10240 - amd64
    Not using a script file.







    AutoAnalysis::
    WARNING: Failed to get store name from identity name with return code 2 for component aspnet_regbrowsers and file aspnet_regbrowsers.exe. File is reported as corrupt by SFC.
    CORRUPT: aspnet_regbrowsers.exe of component aspnet_regbrowsers.


    WARNING: Failed to get store name from identity name with return code 2 for component lsi_sas2i.inf and file lsi_sas2i.inf. File is reported as corrupt by SFC.
    CORRUPT: lsi_sas2i.inf of component lsi_sas2i.inf.


    WARNING: Failed to get store name from identity name with return code 2 for component Microsoft-Windows-Font-Bitmap-MS_Serif and file serf1256.fon. File is reported as corrupt by SFC.
    CORRUPT: serf1256.fon of component Microsoft-Windows-Font-Bitmap-MS_Serif.


    WARNING: Performed DISM repair due to manifest damage on component "amd64_cd76e97c259ee54df08a80beff24dbdc_31bf3856ad364e35_10.0.10240.16603_none_fdbec832800aa169". See CBS logfile for more details.







    SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
    CBS & SFC total detected corruption count: 31
    CBS & SFC total unimportant corruption count: 0
    CBS & SFC total fixed corruption count: 0
    SURT total detected corruption count: 0
    SURT total unimportant corruption count: 0
    SURT total fixed corruption count: 0
    AutoAnalysis:: directive completed successfully.







    Successfully processed all directives.
    SFCFix version 3.0.0.0 by niemiro has completed.
    Currently storing 0 datablocks.
    Finish time: 2016-03-12 23:54:01.871
    ----------------------EOF-----------------------






    • Ad Bot

      advertising
      Beep.

        
       

  2. #2
    Sysnative Staff Member
    Windows Update Senior Analyst
    Security Analyst
    Aura's Avatar
    Join Date
    Mar 2015
    Location
    Québec, Canada
    Age
    23
    Posts
    8,061
    • specs System Specs
      • Manufacturer:
        Custom
      • Model Number:
        Custom
      • Motherboard:
        ASRock Z77 Extreme4
      • CPU:
        Intel i5 3570k @3.4GHz
      • Memory:
        16Gb DDR3 @800MHz
      • Graphics:
        EVGA NVIDIA GTX 670
      • Sound Card:
        Realtek High Definition Audio
      • Hard Drives:
        120Gb Intel SSD | 2x 1TB WD Black
      • Disk Drives:
        ATAPI iHAS124 C
      • Case:
        CoolerMaster StormTrooper
      • Cooling:
        XIGMATEK Dark Knight Cooling
      • Display:
        24' and 21' Dell
      • Operating System:
        Windows 8.1 Professional 64-bits

    Re: Critical_Process_Died and SFC corruptions.

    Hi Dralexz :)

    My name is Aura and I'll be assisting you with your issue. Even though SFC cannot reach 100%, can you run it again, and once it stops, upload your CBS.log for me?

    System File Checker (SFC)
    Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;
    • On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select Run as Administrator
    • On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
    • On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
    • Enter the command below and press on Enter;
      Code:
      sfc /scannow
      Note: There's a space between "sfc" and "/scannow";
    • Once the scan is complete, enter the command below and press on Enter
      Code:
      copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
    • A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;

    Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't have the information from the scan anymore. So archive it and upload it as soon as you can.

    Windows Update Senior Analyst | BleepingComputer Malware Response Team
    If I'm assisting you and I haven't replied to your thread within 3 days, please send me a PM and I'll reply as soon as I see it. Thank you.

Similar Threads

  1. [SOLVED] Blue Screen Critical_Process_Died
    By zbookwin7professional in forum BSOD, Crashes, Kernel Debugging
    Replies: 13
    Last Post: 10-30-2015, 04:45 AM
  2. SFC corruptions
    By 0sQuezada in forum Windows Update
    Replies: 1
    Last Post: 05-28-2015, 10:52 PM
  3. SFC corruptions
    By ANDREW in forum Windows Update
    Replies: 2
    Last Post: 05-06-2015, 04:26 AM
  4. SFC corruptions
    By nmurati in forum Windows Update
    Replies: 3
    Last Post: 05-01-2015, 04:04 PM
  5. CRITICAL_PROCESS_DIED - Windows 8.1 x64
    By Ulysses in forum BSOD, Crashes, Kernel Debugging
    Replies: 7
    Last Post: 08-17-2014, 06:18 PM

Log in

Log in