Memtest86 and Memtest86+ are open sourcememory test software programs designed to test and stress test an x86 architecture computer's random access memory (RAM) for errors. Each tries to verify that the RAM will accept and correctly retain arbitrary patterns of data written to it, and that there are no errors where different bits of memory interact, and there are no conflicts between memory addresses.

Contents

There are two versions (or development streams) of Memtest86. The original is simply known as Memtest86.[1] The other, known as Memtest86+,[2] is a development fork of the original Memtest86 (see history). Their on-screen appearance and functionality were almost identical up until the V4 releases. However the current V6 release of MemTest86 now makes use of the UEFI graphical user interface and the mouse.

These programs work with nearly all PC compatible computers from 80386 and 80486 based systems to the latest systems with 64-bit processors. Each new release adds support for newer processors and chipsets.[3][4]

Memtest86 is designed to run as a stand-alone, self-contained program from a bootablefloppy disk, CD-ROM, USB drive, or from a suitable bootmanager without an operating system present. This is because the program must directly control the hardware being tested and leave as much of the RAM space as possible for examination. It is also a quick and convenient way to start the program, and avoids running a complex operating system/application which could be endangered by hardware with memory problems (for example, a hard disk file system can be corrupted by writing erroneous data from faulty RAM.)

Memtest86's testing is very comprehensive so it can find otherwise hidden problems on machines that appear to work normally.[5] With many chipsets, Memtest86 allows counting of failures even in error-correcting ECCDRAM (without special handling, error correcting memory circuits can mask problems with the underlying memory chips).

Running one complete pass of the program (executing all the selected tests one time) can take from a few minutes to a few hours, depending on the amount and speed of memory installed, and the CPU speed. Some errors manifest intermittently or depend on the precise bits being stored, and do not occur on each pass; such errors may be revealed by running many passes over an extended period. Some tests use different data each pass to reveal data-dependent errors.[6] The program can run continuously until the machine is switched off or rebooted.

The programs were first made available on the Internet as small downloadable diskette image files, and included a small Windows program to make the floppy disk. Under Linux, the standard dd utility command is used to make the floppy disk.[7][8] The floppy is then used to boot the computer whose RAM is to be tested.

Distribution now includes a USB image and a bootable CDiso image which the user must burn to a writeable optical disc, such as a CD-R, before using. The easiest way for a beginner to access the programs may be as part of a bootable LiveCD. Popular Linux distributions such as Knoppix and Ubuntu offer an option, when the CD starts, to run Memtest instead of booting Linux. Memtest86 and Memtest86+ are included in rescue sets of utilities, such as the Ultimate Boot CD, which contains both.

Additionally, some high-end computer motherboards come with MemTest86 integrated into the BIOS. The user runs Memtest86 by pressing a certain key during boot-up. One example is the Biostar TPOWER i55 motherboard.

Memtest86 was developed by Chris Brady. After Memtest86 remained at v3.0 (2002 release) for two years, the Memtest86+ fork was created by Samuel Demeulemeester to add support for newer CPUs and chipsets. As of November 2013[update] the latest version of Memtest86+ is 5.01.[9][10]

Starting from Memtest86 2.3[3] and Memtest86+ 1.60,[4] the program can output a list of bad RAM regions in the format expected by the BadRAM[11] patch for the Linux kernel; using this information, a Linux system can reliably use a RAM module even if it has a few bad bits.[12]Grub2 is able to supply this same information to an unpatched kernel,[13] making the BadRAM patch unnecessary.

At some point the original memtest86 was sold to PassMark who continued to improve it through version four. Version five was rewritten and released under another licence. Version six provides support for DDR4 RAM, UEFI secure boot, plus a new 'row hammer test' based on research from Yoongu Kim et al, [14]

Detections of faulty memory are displayed prominently. The application shows not only which memory locations failed, but also which patterns made them fail.

Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.[15]

The default pass does 13 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.

Memory cache (such as cache on board the CPU chip) is not disabled. However, access patterns are designed to keep most cache organizations flushed so that memory accesses are actually seen to the RAM.

Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some support changing the expected memory speed. In this case, if memory is overclocked and the expected memory speed is changed to match, Memtest86 can test whether memory performance is error-free with the faster settings.

Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.

This information, if available to the program, can be displayed via a menu option.

The Memtest86 programs do not diagnose computer problems not due to memory; a problem due to a CPU or motherboard problem is likely to make Memtest86 crash. Some memory problems diagnosed may be due not to faulty memory, but to memory being run at a higher speed than it is capable of.[citation needed]

On some machines with the newer UEFI instead of BIOS, the Memtest86 Web site warns that PS2 keyboard input is no longer emulated, which can cause the keyboard to be completely or intermittently unresponsive. In these cases it is suggested to leave the tests to run automatically. [16]

^In computing, dd is a common Unix program whose primary purpose is the low-level copying and conversion of raw data. According to the manual page for Version 7 Unix, it will "convert and copy a file". It is used to copy a specified number of bytes or blocks, performing on-the-fly byte order conversions, as well as more esoteric EBCDIC to ASCII conversions. It can also be used to copy regions of raw device files, for example backing up the boot sector of a hard disk, or to read fixed amounts of data from special files like /dev/zero or /dev/random.