David Maynard wrote:

> It could be anything, including the CPU. After all, memory can't be read
> without the CPU being involved.

Is it even possible for a CPU to malfunction in such a specific way
while still letting everything else work? It's not having problems
whatsoever booting and running memtest86 ... it's just when you try to
load an OS (which needs memory) that you get the problems.

> But with persistent global errors of that type I'd tend to guess a BIOS
> setting before hardware failure. Try 'safe' defaults and, in particular,
> the slowest memory speed settings.

It doesn't seem to matter. I get the same errors. I paid attention
more time and it's more like 00XX0000 the first few seconds of
memtest86 where XX are random hex, but then it settles down to Err-Bits
00ff0000 over and over and over.