SFC couldn't fix corruption.

[Floppyflup]

Hi there! I recently started getting unexpected kernel trap BSOD's so I ran SFC and it found some corruption it couldn't fix. I therefore ran dism /online /cleanup-image /restorehealth and the restore operation completed succesfully however SFC is still giving a corruption it couldn't fix error.

I have ran Chkdsk and no issues were found. Here is my SFC log, any and all help would be greatly appreciated!

 

[Sysnative Windows Update]

Hello and welcome!

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:

• Download the portable version of GSmartControl and save it on your Desktop;
• Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
• Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
• You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
• Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
• Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
• Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
• Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
• Please note: If the SMART Status reads: Unsupported, stop and let me know.
  
  

 

[Floppyflup]

Thank you very much for responding! Here's the screenshots for the test, there are no red or pink entries in attributes.

 

[Sysnative Windows Update]

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor as close to failure as possible.
2. Try running SFC just like you have in the past.
3. Stop Process Monitor as soon as the it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.