Corrupt files on windows? What cause this?

[Sargon]

A while ago, I had BSOD on my OS, and I found that I had issues with XMP with my 64GB kit.

The first step I did was to correct the file system corruption files with sfc.

 

I then disabled the XMP, and the RAM seemed to work fine.

 

However, recently windows notified me there is again corruption in the file system(in the notifications).

I ran sfc, and it did find corrupt files and fixed them.

I didn't get BSOD since fixing the RAM issue, but what can possibly cause this?

 

It is possible that there was a power outage at some point due to a lightning storm.

So is this the cause?

 

Or does windows file system gets corrupt as a normal thing?

 

Here is the console output of the sfc(didn't incluse the log)

 

 

C:\WINDOWS\system32>sfc /SCANNOW

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

[Grand Admiral Thrawn]

If you are using a Windows 10 / 8.1 / 8, try the following command first:

 

DISM.exe /Online /Cleanup-image /Restorehealth

 

and after the process finishes, check again with sfc /scannow.

If the sfc command finds any corruptions (and/or fixes them), reboot the PC and check the command once more.

[Sargon]

What exactly does it do?

[homeap5]

Your question was about corrupting files, so answer is - this happens only with faulty hardware and it's not normal. Bad overclocking (including XMP) can cause that too. That is why stability tests are important after you set OC.