A screenshot of Memtest86+ |
|
Developer(s) | Memtest86: Chris Brady Memtest86+: Samuel Demeulemeester |
---|---|
Stable release | Memtest86: 4.0a August 20, 2011 Memtest86+: 4.20 January 25, 2011 |
Operating system | Standalone bootable programs |
Type | Utility |
License | GPL v2.0 |
Website | Memtest86: www.memtest86.com Memtest86+: www.memtest.org |
Memtest86 and Memtest86+ are open source memory 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). They both have almost identical screen appearance.
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 bootable floppy disk, CD-ROM, USB Drive, or from a suitable bootloader 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 damaged RAM.)
Memtest86's testing is very comprehensive[5] so it can find otherwise hidden problems on machines that appear to work normally. With many chipsets, Memtest86 allows counting of failures even in error-correcting ECC DRAM (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 are so subtle that they don't occur on each pass; errors are more likely to be revealed after running many passes over an extended period. This is because some tests use slightly different data each pass,[6] and errors may appear after heat builds up from extended operation. Thus the program will run continuously until the user reboots.
Traditionally, the programs were 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 can then be booted directly on the test computer.
This mode has become obsolete as floppy disks are no longer in widespread use, so distribution now includes a USB image and a bootable CD iso image which the user must burn to a writable 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 immediately (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 would simply have to press a certain key during boot-up and MemTest86 would run without a boot disk. (One example of this 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 2009, both are being actively maintained.[9][10]
Memtest86 is written in C and x86 assembly. The source code is released under the GNU General Public License (GPL). The bootloading code was originally derived from Linux 1.2.1. Both versions now support current dual- and quad-core-CPUs and the corresponding chipsets. The latest release of Memtest86+ supports Intel-based Macintosh computers.
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] negating the need for the BadRAM patch.
Memtest86 writes a series of test patterns to most memory address, reads back the data written, and compares it for errors.[14]
The default pass does 9 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 even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these 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.