This lack of settings severely hampers the overall ECC functionality, since a big part of it is that the motherboard should be able to log errors. Right now, no such logging capability exists.
...
If it does not, the hardware might be silently correcting single-bit errors and even detecting 'catastrophic' two-bit errors, but you will never know about it since there will be no log.
...
The first command (wmic memphysical get memoryerrorcorrection) essentially queries Windows as to whether it detects any form of memory error-correcting code functionality. Regrettably, 3 signifies "none". The other options could have been 2 (unknown), 4 (parity), 5 (single-bit ECC), or 6 (multi-bit ECC).
...
If the TotalWidth value is larger than the DataWidth value then ECC is enabled. Ideally, we would have liked to see 72 for the TotalWidth instead of 64, since that would have indicated that the OS detects a 72-bit memory bus width, which as we discussed in the first page is the norm for ECC memory. Once again, no such luck.
...
Just for the hell of it, we loaded up Windows Server 2016 in the slight hope that an operating system that was designed to be used on exclusively ECC-enabled hardware might produce different results. We tried all of the same Windows commands, as well as all the same applications, and they all reported the same information as Windows 10 Pro.
...
Based on just the above information, it would not be prudent to say that ECC is enabled on this platform
....
HOWEVER, things are not quite perfect. On that last line you will notice "1 UE". That is an uncorrected error (UE), otherwise known as a two-bit error or a hard error. Two-bit errors cannot be corrected by ECC memory. What is supposed to happen when they occur is that they should be detected, logged and ideally the system should be immediately halted. These are considered fatal errors and they can easily cause data corruption if the system is not quickly halted and/or rebooted. Regrettably, only 2 of the 3 steps happened. The hard error was detected and it was logged, but the system kept running. The only reason that it's the last line on that image is because we immediately took a screenshot just in case the system would halt, but that never happened.
....
In conclusion, what is currently available on the AM4 platform is an incomplete implementation of ECC.