- Joined
- Feb 15, 2014
- Messages
- 20,194
So the debug file and dmidecode wasn't particularly useful. No more questions answered than before. It could be something obscure causing the ff's to be provided, but I can't say much more. You're kind of in this boat where you have to "believe" that ECC works without knowing for 100% certainty. It's about the same as AMD. It's impossible to prove AMD is actually using ECC because there's no tool that validates for 100% certainty. You could simulate an ECC error with dmidecode, but I'm not 100% convinced that it proves you are using ECC. /shrug
I know memtest 4.x+ says ECC or non-ECC, but again that's no indicator for 100% certainty (although plenty of people want to (and do) blindly say that it must be correct).
Is that memtest86+ v4.x and up, memtest86 v4.x and up or memtest86+ v4.x only?