MemTest86 Support

If you have a problem with MemTest86 first check the forums and the list of known issues below, to see if a solution is already available. If you think there is a bug in the software please see the section below on bug reporting and gathering trace information and gather as much information as you can about the problem before contacting us.

Problem & Bug Reporting

To improve the quality of MemTest86, accurate reporting of problems and bugs essential. Please carefully follow the instructions below to report problems.

Note:The information here is targeted at troubleshooting problems with execution of the test code and not for diagnosing reported memory errors.

MemTest86 v5 or later (UEFI)

One of the new features of MemTest86 v5 is the ability to log to a file on a USB flash drive. A log file (MemTest86.log) is automatically created and updated while MemTest86 v5 is running. This file is saved in the 'EFI/BOOT' directory in the USB drive's first partition. For obvious reasons, a log file is not generated when booting MemTest86 from a CD; please use a USB flash drive instead. If you believe you may have encountered a bug with MemTest86, please report problems to PassMark Softare.

MemTest86 v4 (BIOS)

In Version 4.1.0 a Boot Trace feature was added that provides a simple mechanism for troubleshooting of test failures by both technical and non-technical users. With the very large variety of computer hardware available it is impossible to test MemTest86 an all platforms and some incompatibilities exist causing failures. With trace information many of these faults may now be resolved.

Enabling Boot Trace - The boot trace feature is enabled with either a boot time option or an on-line command. However, most problems occur during startup so the boot option is the preferred method. All of the released images have a boot option to start the test with boot tracing enabled. When booting from a Linux system with LILO or GRUB add "btrace" to the boot options line. When Boot Trace is enabled two columns of trace information will be displayed one the bottom two thirds of the screen. The CPU, line number from the source file, a short message and two parameters are displayed in each trace point. A ">" character denotes the current trace point. A total of 26 trace points are displayed and older trace points are lost as execution progresses. Pressing any key will advance to the next trace point. As initialization proceeds other portions of the screen will be filled in with information and the header lines will be erased.

Gathering Trace Information – There are two types of failures where trace information is needed to help diagnose the problem, hangs and crashes. Gathering traces for a situation when the test hangs is very simple. Just continue to press return until the test stops. At minimum email the last 5 trace points. More useful would be a digital picture of the screen. For cases where the test crashes we need to find the trace points just before the crash. This requires slowly stepping through the traces and identifying the point where the test crashes or reboots. Then run the test again and stop at the trace point just before the crash and report the information. Again, email at least the last 5 trace points or better a picture of the screen. Please email failure information using the form below.

Using Trace Information - Technical users will be able to diagnose problems using trace data that previously would have required detailed understanding of MemTest86's internal workings. By following the trace points in the source you will be able to follow the path of execution and identify problems. As needed new trace points may be added to the code to provide more detail when diagnosing a problem.

Additional Information - It is also very valuable to know how failures affect different releases. Please try each of the test versions provided and report. A number of failures affect only operation when multiple CPUs are being used. Please run using the option to run with only one CPU and report.

Back to top

Known Issues

MemTest86 can not diagnose many types of PC failures. For example a faulty CPU or motherboard that causes Windows to crash will most likely just cause MemTest86 to crash in the same way.

Often the memory works in a different system or the vendor insists that it is good. In these cases the memory is not necessarily bad but is not able to operate reliably at high speed. Sometimes more conservative memory timings on the motherboard will correct these errors. In other cases the only option is to replace the memory with better quality, higher speed memory. Don't buy cheap memory and expect it to work reliably. On occasion "block move" test errors will occur even with name brand memory and a quality motherboard. These errors are legitimate and should be corrected.

MemTest86 supports all types of memory. In fact the test has no knowledge of the memory or CPU type nor does it need to. MemTest86 is able to test all types and brands of memory. If the information reported regarding chipsets or CPU's is incorrect it will not affect testing in any way. This not a problem or bug but is listed here due to the many questions about this issue.

MemTest86 v5 or later (UEFI)

MemTest86 depends on the services provided by the UEFI firmware, which include mouse/keyboard support, multiprocessor services, file input/output, and PCI device management. Because the services that are provided by the firmware are developed individually by the motherboard manufacturers, there may be functional differences than can limit or prevent the proper operation of MemTest86. Some of these issues are highlighted below:

  • Some UEFI implementation do not provide full mouse support, preventing the use of the mouse in MemTest86. If this is the case, use the keyboard or try updating to a new firmware build.
  • Multiple CPU testing may not be available due to limited or non-functional implementations of Multiprocessor services provided by UEFI, especially for older firmware. This may cause a reduced number of processors available for testing, or even program freeze when attempting to run on other processors. If this is the case, run in single CPU mode or try updating to a new firmware build. There is a blacklist.cfg file that contains a list of baseboards that are known to have issues running MemTest86. Adding a baseboard to the list may allow MemTest86 to run, albeit with limited functionality. The following is a snipbit of the blacklist.cfg file:
    "Z170X-Gaming 3",ALL,EXACT,RESTRICT_MP
    "Z170X-Gaming 7",ALL,EXACT,RESTRICT_MP

    Each blacklisted baseboard is stored on a separate line with the following format:

    [baseboard],[BIOS version],[exact|partial match],[restriction flags]


    [baseboard] is the case-sensitive baseboard string in double quotes

    [bios version] is the first BIOS version (string in double quotes) that no longer exhibits the issue. If no fix is available, specify ALL

    [exact|partial match] determines whether exact or partial matching is used on [baseboard string].

    [restriction flags] determines the restriction policy to impose if there is a match. This can be one of the following values:

    • RESTRICT_STARTUP - Display a warning message before MemTest86 boots
    • RESTRICT_MP - Do not perform the multiprocessor test during startup, and set the default CPU mode to SINGLE
    • DISABLE_MP - Completely disable multiprocessor support, restricting the CPU mode to SINGLE only
  • On some newer machines, UEFI BIOS no longer emulate PS2 keyboard input. This can result in the keyboard being completely unresponsive or intermittently responsive. In these cases we suggest leaving the test to run automatically and powering down the machine once the tests have been completed.

MemTest86 is also inherently limited by the UEFI environment and as such, gives rise to the following limitations:

  • MemTest86 USB flash drives cannot be read in Windows XP (32-bit) due to its lack of support of GPTdisks
  • MemTest86 cannot remap itself to different portions of memory in order to run tests in the section of memory it was occupying.
  • Dual UEFI entries may be present in UEFI BIOS as boot devices. There is no difference in selecting either entry. This is due to a workaround that allows MemTest86 USB flash drives to be accessible in Windows.

MemTest86 v4 (BIOS)

Sometimes when booting from a floppy disk the following messages scroll up on the screen:


On a small number of machines, false positives were reported when running Test #3 in parallel mode. If this is the case, re-run the test in single CPU mode before concluding that it is a RAM issue.

Back to top

Discussion Forum

MemTest86 User Forum

Back to top

Version History

This is a summary of changes and bug fixes that have been made to MemTest86 in each release.

MemTest86 Version History

Back to top

E-mail support

For problems or suggestions on how to improve our products contact:

E-mail support: Click to send mail (JavaScript required)

If you are reporting a problem please include:

  • The software version.
  • A detailed description of the problem and how to reproduce it.
  • A copy of the result files / log files (if available).
  • Details of how we may be able to contact you.

Pro Edition users will of course be given priority.

Back to top

Other Tools from PassMark Software