4 ms·

So this is the datasheet for the C226 (https://www.intel.com/content/www/us/en/products/docs/chipsets/8-series-chipset-pch-datasheet.html https://www.intel.com/

So this is the datasheet for the C226 (https://www.intel.com/content/www/us/en/products/docs/chipsets/8-series-chipset-pch-datasheet.html https://www.intel.com/content/www/us/en/products/docs/chipse...) and you have an i3-8100 or equivalent that does support ECC, then the BIOS will configure how it wants ECC errors reported. On my Ryzen board they are reported via SMI events and there is a chip that you can talk to on the SMBUS that will tell you how many events it has seen since the log was reset. In my experience getting the information isn't "difficult" so much as it isn't "common". On my FreeNAS device (which has the Xeon) it also has an IPMI controller which lets me ask it over the network how many ecc errors have been seen. (and it can act like a remote console as well but we'll leave that for another time :-)) So find out how the motherboard is tracking ECC, then find the tool that talks to that system to ask it for the logs of ECC errors.

p1mrx 6y ago
Well, non-ECC RAM can report "0 errors" for less money. The problem is how to determine whether your system is actually capable of detecting/logging errors end-to-end. There needs to be a standard way to inject an ECC error and see what happens.
- ChuckMcM 6y ago
  There are also BIOS setups that "mask" soft or correctable errors since nothing bad happens when they correct the problem. I've always preferred to not mask those errors as it was always a good thing to note on server hardware on clusters that if their soft error correction rate started rising then a DIMM was going to need to be replaced.
- Dylan16807 6y ago
  Overclock it one step at a time until it gets mad.
- theevilsharpie 6y ago
  > Well, non-ECC RAM can report "0 errors" for less money. "0 errors" is very different from "ECC not available," and that's a distinction I'd expect the operating system to be able to make. For example, here's how Linux shows ECC and non-ECC memory reports: # ECC $ sudo edac-util -v mc0: 0 Uncorrected Errors with no DIMM info mc0: 0 Corrected Errors with no DIMM info edac-util: No errors to report. # Non-ECC $ sudo edac-util -v edac-util: Error: No memory controller data found.

p1mrx 6y ago

Well, non-ECC RAM can report "0 errors" for less money. The problem is how to determine whether your system is actually capable of detecting/logging errors end-to-end. There needs to be a standard way to inject an ECC error and see what happens.

ChuckMcM 6y ago
There are also BIOS setups that "mask" soft or correctable errors since nothing bad happens when they correct the problem. I've always preferred to not mask those errors as it was always a good thing to note on server hardware on clusters that if their soft error correction rate started rising then a DIMM was going to need to be replaced.
Dylan16807 6y ago
Overclock it one step at a time until it gets mad.
theevilsharpie 6y ago
> Well, non-ECC RAM can report "0 errors" for less money. "0 errors" is very different from "ECC not available," and that's a distinction I'd expect the operating system to be able to make. For example, here's how Linux shows ECC and non-ECC memory reports: # ECC $ sudo edac-util -v mc0: 0 Uncorrected Errors with no DIMM info mc0: 0 Corrected Errors with no DIMM info edac-util: No errors to report. # Non-ECC $ sudo edac-util -v edac-util: Error: No memory controller data found.