Post by Mike EasterPost by gamocould I boot the computer without the memtest+ program?
I booted a live Ub 20.04.1 Mate. I see that it has memtest86+ installed
Post by gamoThis tester runs independently of any OS - it is run at computer
boot-up, so that it can test *all* of your memory. You may want to
look at `memtester', which allows to test your memory within Linux,
but this one won't be able to test your whole RAM.
I'm not sure I follow/understand the full meaning of that description.
Running a memory tester in Linux, while the kernel runs.
+-----------+
| Test-able | \
| | \
| | \
| | /
| | /
+-----------+ /
| Kernel |
| |
| |
+-----------+
| BIOS E810 |
+-----------+
Running a memory tester as a bootable binary.
+-----------+
| Test-able | \
| | \
| | \
| | \
| | |--- Mostly testable
| | /
| | /
| | /
| code | /
+-----------+
| BIOS E810 | 1MB not covered
+-----------+
Note: The "code" hunk is moved out of the way,
and the memory tester tests the area the code
used to occupy. Later, the code is moved back.
This means the "code load" area is tested!
The BIOS E810 area is reserved for BIOS usage. If
memtest were to work in there, all hell would break loose.
This is one area that cannot be massaged with "move it out
of the way" code. The machine can take an SMI for
SMM (system management mode) at any time, while the
memory test code is running. On an Asus motherboard,
this could happen 30 times a second while the VCore
phases are adjusted.
*******
How to *really* test memory 100%.
It requires a four slot motherboard and two DIMMs.
The "X" equals no DIMM. You put the two DIMMs on
the same channel (single channel mode).
Channel 0 Channel 1
High X
Low X
If the test passes, you swap the DIMMs
Channel 0 Channel 1
Low X
High X
This solves the 1MB area at the bottom, but may
not cover a few other spots. I would have to find
an E810 description to get an exact inventory.
I've only had one case, where the memory was bad
in a "critical" location. Most other times, random
chance favors the system coming up.
I've had one chip on a DIMM fail and generate random
byte values (likely the bus is floating). This means
there are failure patterns other than a single
stuck-at bit somewhere. Using the above single-channel
test mode, one test case would not boot memtest, while
the other would. The errors were just scrolling off
the screen... :-) That was some Crucial Ballistix.
Paul