Memtest86+ finds errors in almost every computer

[dr.spock]

In last Ubuntu releases (at least Kubuntu 64 bit ones), if you run Memtest86+ from GRUB, you'll get infinite errors on test #7. It makes Memtest86+ unreliable, so unuseful.

Now I'm using Kubuntu 12.10 64 bit, but in my shop's lab we have found this bug on several flavors and versions.

[Tom van Leeuwen (mrzx4l98d4tp89jab6giohdrjqysbyjs4npz2ccq25kvjmf5h8u4cmidcko7s4tfr6ur1teuv4ju1af4klpdqp0vd87ddz5sh53mwfrw5819ohmadctcbsrykdp4exz2w0xzyv54zb4ksnirbzfvybudw577zswcymukpheqeiptvlrx87cyumfa232omr5gcyxpni3rwgnjdqw38fhshrdw19z5s2fyst45o0e5sk2nk-ubuntu)]

I have a Compaq N610c (Pentium 4 1.8ghz, relatively old) and also experience problems with test 7.
However, I don't see the problem with the original build from www.memtest.org.
More details will follow soon.

[Tom van Leeuwen (mrzx4l98d4tp89jab6giohdrjqysbyjs4npz2ccq25kvjmf5h8u4cmidcko7s4tfr6ur1teuv4ju1af4klpdqp0vd87ddz5sh53mwfrw5819ohmadctcbsrykdp4exz2w0xzyv54zb4ksnirbzfvybudw577zswcymukpheqeiptvlrx87cyumfa232omr5gcyxpni3rwgnjdqw38fhshrdw19z5s2fyst45o0e5sk2nk-ubuntu)]

Bad words are 0x00000000 if test 7 is started immediately, else they correspond to the last written pattern before i ran test #7.

Since i only see the problem with i386 builds (my machine is i386 but the x64 version of memtest seems to run fine), i decided to re-build the memtest from the source package. However, this did not make any difference.

memtest86+_4.20-1.1ubuntu2_i386: False errors on test #7 (both self-build and original)
memtest86+_4.20-1.1ubuntu2_x64: No false errors

I forgot to mention that the PC is a laptop. I have an identical one but haven't been able to run memtest on that laptop yet. I tested with a 256MB and (later) with only a 1GB memory module.

[Tom van Leeuwen (mrzx4l98d4tp89jab6giohdrjqysbyjs4npz2ccq25kvjmf5h8u4cmidcko7s4tfr6ur1teuv4ju1af4klpdqp0vd87ddz5sh53mwfrw5819ohmadctcbsrykdp4exz2w0xzyv54zb4ksnirbzfvybudw577zswcymukpheqeiptvlrx87cyumfa232omr5gcyxpni3rwgnjdqw38fhshrdw19z5s2fyst45o0e5sk2nk-ubuntu)]

Oops, this bug was already reported and fixed: Bug #1071209