>dodgy overclocking Error detection and correction is actually ideal when overclocking. It'll not only save you, it'll let you know you need to back off a bit,

>dodgy overclocking Error detection and correction is actually ideal when overclocking. It'll not only save you, it'll let you know you need to back off a bit, because the handful of errors that may happen once a month despite passing days of tests will show up in the system logs instead of staying silent and causing problems. I speak from experience as I overclocked ECC memory in a first gen threadripper system, playing around with overclocking as a hobby for a bit. ECC memory was fantastic to work with. However the dodgy or outright lack of CPU/Motherboard support results in trying to market that feature to gamers/overclockers having too much friction. Much like what went on with intel's confusing proprietary optane/flash combo M.2 drives that needed certain motherboards in order to fully access both parts of the drive. And with bad sticks, instead of hard to explain crashes, you'll end up with system logs filled with corrected/detected errors and maby crashes if it's really bad. Then you just RMA the sticks like normal. So honestly that's a win too, because that's the whole point of detecting and correcting errors. It's in every other part of the system already, continuing to leave this capability out of memory is an oversight that needs to be.. corrected. I just don't really get the strange resistance people have to ECC, it's not some sacred cow. It's just good sense.