I performed an "sfc/ scannow" operation through the Command Prompt on 25-03-24. This fixed a load of files which had apparently suffered corruption. Here's a Dropbox share-link for a TXT-file while shows just the 500 lines that that "sfc /scannow" operation generated in the "C:\Windows\Logs\CBS\CBS.log" file .
There are only a few things in the Reliability Monitor tool which, as far as I can see, could have contributed to corrupting the files that "sfc /scannow" fixed. I'll present them below under dated sub-headers. On the morning of 20-03-24 I Clean-Installed W11 to my PC, so there is no record on Reliability Monitor prior to that date.
I'd like to know what caused those files to have been corrupted.
24-03-24
* x16 "Setting > Stopped working" Critical Event | all 16 of these instances were simultaneous. I cannot remember the Settings app crashing on that day.
22-03-24
* "COM Surrogate > Stopped working" Critical Event | the "Problem Details" window shows that it was to do with the "Clipchamp" app, which I do not use.
* "Failed Windows Update" Warning | of the "Clipchamp" app, which app I do not use.
21-03-24
* x2 "COM Surrogate > Stopped working" Critical Event | the "Problem Details" window show that it was to do with the "Clipchamp" app, which I do not use.
* "Windows > Windows was not properly shut down" Critical Event | the shut-down event being just a few minutes prior to the time-stamp of the notice itself.
20-03-24
* "Windows > Windows was not properly shut down" Critical Event | the shut-down event being just a few minutes prior to the time-stamp of the notice itself;
* "WavesSvc64.exe > Stopped working" Critical Event;
* x3 "Windows Explorer > Stopped working" Critical Events | I remember these crashes happening in real-time.
There are only a few things in the Reliability Monitor tool which, as far as I can see, could have contributed to corrupting the files that "sfc /scannow" fixed. I'll present them below under dated sub-headers. On the morning of 20-03-24 I Clean-Installed W11 to my PC, so there is no record on Reliability Monitor prior to that date.
I'd like to know what caused those files to have been corrupted.
24-03-24
* x16 "Setting > Stopped working" Critical Event | all 16 of these instances were simultaneous. I cannot remember the Settings app crashing on that day.
22-03-24
* "COM Surrogate > Stopped working" Critical Event | the "Problem Details" window shows that it was to do with the "Clipchamp" app, which I do not use.
* "Failed Windows Update" Warning | of the "Clipchamp" app, which app I do not use.
21-03-24
* x2 "COM Surrogate > Stopped working" Critical Event | the "Problem Details" window show that it was to do with the "Clipchamp" app, which I do not use.
* "Windows > Windows was not properly shut down" Critical Event | the shut-down event being just a few minutes prior to the time-stamp of the notice itself.
20-03-24
* "Windows > Windows was not properly shut down" Critical Event | the shut-down event being just a few minutes prior to the time-stamp of the notice itself;
* "WavesSvc64.exe > Stopped working" Critical Event;
* x3 "Windows Explorer > Stopped working" Critical Events | I remember these crashes happening in real-time.
- Windows Build/Version
- W11 23H2
My Computer
System One
-
- OS
- Windows 11
- Computer type
- Laptop
- Manufacturer/Model
- Dell Latitude 7430