A bit of an update since is that the numbers of errors has grown since, presumably the entire chip (out of the few that are on the RAM stick) is broken which will likely keep revealing itself over time.
I don't know yet if it's possible to somehow learn which memory addresses belong to which chip and pre-emptively mark all of these ones on the chip as "do not use", or if it's possible to start the test again while the OS is running (theoretically possible if the errors are somewhere in the memory used by userspace), so you probably want to restart the OS more often (I used to leave it in sleep for days so that's a bit of a problem).