A small issue, MemTest86 & MemTest86+, explains why you were this quickly done.
We request that you run MemTest86+ instead of MemTest86, our experience is that MemTest86+ is basically better in finding problems.
To note, 16GB could take a day to 2 days to reach 8 passes with MemTest86+.
I would say that it depends on your definition of 'false positive' in the case of SFC.
It said: "The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see Configure a Windows Repair Source."
Might be something here? but some also says sfc gives alot of false positives :/
A few weeks ago I saw an issue with Avast & SFC, SFC flagged some files from Avast because the hashes were incorrect according to SFC. These cases have returned more often and it turned out that the hive holding the Avast hashes was holding wrong hashes, because of this SFC reported it as a corrupt one but that wasn't the case. That I would call a false positive.
In the case of your corruption, it is the known opencl.dll causing it. The known situation is where Nvidia replaces it with driver updates, thus replacing the Windows version with a newer version. I don't know if you have Nvidia or not, but the opencl.dll is newer than the one from Windows. I wouldn't call that a 'false positive', it has a different hash because it is different from the one Windows expects what theoretically makes it corrupt. Fortunately it does not have affect on the system
Please fill in your system specs
Please follow this tutorial
and download the tool. The tool will give you detailed information about your system specs, please fill in your system specs more completely including PSU, cooling and other used stuff like mouse, keyboard, monitor, case, etc.
The PSU, cooling and other stuff are NOT mentioned in the tool.
How to fill in your system specs: