Why MemTest86 Is Not Recognizing Your USB Drive
MemTest86 usually fails to recognize a USB drive because the image was not written as a bootable disk, the wrong MemTest86 version was used, or the PC’s UEFI firmware is not exposing the drive as a boot option. Start by recreating the USB from the current UEFI-compatible MemTest86 download, then select its UEFI boot entry from the computer’s one-time boot menu. If the drive appears but MemTest86 will not start, treat that as a firmware compatibility problem rather than a bad USB stick.
Use this table to match what you see with the most likely fix.
| Symptom | Likely Cause | First Fix |
|---|---|---|
| The USB drive is absent from the boot menu | The drive was not written as a bootable image, the port is not being initialized at startup, or firmware is filtering boot devices | Recreate the USB image, reconnect it directly to the computer, and reopen the one-time boot menu |
| The USB appears, but selecting it loads Windows | The wrong boot entry was selected, the image was copied rather than written, or the drive contains an incompatible MemTest86 version | Select the entry labeled UEFI for the USB drive and recreate the stick from the current download |
| The USB starts, then shows a black screen, hangs, or restarts | A motherboard UEFI implementation is incompatible with part of MemTest86 | Update firmware if available; check for an ASUS optical-drive issue and the included blacklist.cfg file |
| MemTest86 starts but freezes while using multiple CPU cores | Firmware has a multiprocessor compatibility problem | Run MemTest86 in single CPU mode or update the motherboard firmware |
| Windows XP cannot read the finished stick | The MemTest86 USB uses a GPT disk layout that Windows XP 32-bit does not support | Do not treat that alone as a failed write; boot the stick on a compatible PC instead |
What “Not Recognizing” Usually Means
“Not recognizing” can describe three different failures, and they have different fixes:
- No USB entry appears in the firmware boot menu: the system is not detecting the physical stick or a bootable image on it.
- A USB entry appears, but selecting it starts Windows: the wrong entry may have been selected, the image may not have been written correctly, or firmware may not find a valid UEFI boot image.
- MemTest86 begins loading but never reaches the test screen: this points to a UEFI firmware compatibility problem rather than USB recognition. MemTest86 relies on services supplied by your motherboard’s UEFI firmware, and those firmware implementations can limit or prevent it from running.
The most important distinction is this: a drive that is absent from the boot menu is usually a USB-writing or firmware-detection problem; a drive that boots but freezes is more likely a UEFI compatibility problem.
How to Fix a MemTest86 USB Drive That Will Not Boot
A current MemTest86 image written to the whole USB drive and selected through the UEFI boot menu should reach the startup screen.
Step 1: Confirm Which Failure You Have
- Shut down the computer completely.
- Insert the MemTest86 USB drive directly into a USB port on the computer. Avoid an unpowered hub, monitor hub, or docking station while troubleshooting.
- Power on the computer and open its one-time boot menu.
- Look for an entry that includes the USB drive’s brand or model. On UEFI systems, there may be a separate entry beginning with
UEFI:.
If the drive is listed, select the UEFI entry rather than a generic legacy USB entry. If selecting it immediately returns you to Windows, recreate the USB before changing boot-order settings or disabling security features.
On many ASUS motherboards, open the one-time boot menu during startup, but the correct key varies by manufacturer and model.
Step 2: Download the Correct MemTest86 Release
Use the current MemTest86 USB download intended for UEFI-based computers. Do not use the old MemTest86 V4 release unless you are working with an old computer that has only legacy BIOS support.
A common mistake is downloading an older release, extracting its files, and expecting a modern UEFI PC to boot it. A correctly created current MemTest86 USB should contain boot files under an EFI folder, including files in EFI/BOOT.
Also make sure you are not mixing up these separate tools:
- MemTest86 is the PassMark UEFI-based utility discussed here.
- Memtest86+ is a different project with its own images and USB installer.
Do not write a Memtest86+ installer, ISO, or image when you intended to create a PassMark MemTest86 USB.
Step 3: Write the Image Instead of Copying Files
Creating a bootable MemTest86 stick overwrites the USB drive. Copy off anything you need before continuing.
Windows
- Extract the MemTest86 ZIP download.
- Launch the included ImageUSB application.
- In Step 1, select your USB drive from the list.
- Choose the option to write the MemTest86 image to the selected drive.
- Let the writing process finish, then safely eject the drive.
Do not drag the .img file onto the USB drive in File Explorer. That copies the image as a file; it does not write the bootable disk structure that UEFI firmware needs.
On Linux, write the image directly to the whole USB device:
First, identify the whole USB device with lsblk:
lsblk
Use the base device shown by lsblk, such as /dev/sdc, not a partition such as /dev/sdc1. From the directory containing memtest86-usb.img, write the image with:
sudo dd if=memtest86-usb.img of=<dev> conv=fsync status=progress
Replace <dev> with the whole USB device. For example, /dev/sdc is a device; /dev/sdc1 is only one partition on that device. Choosing the wrong destination can erase another disk, so verify the device name before pressing Enter.
On macOS, write the image directly to the whole USB device:
In macOS, identify the USB drive’s device name before writing the image. Use the whole device, such as /dev/disk1, not a partition such as /dev/disk1s1. From the directory containing the image, use:
sudo dd if=memtest86-usb.img of=<dev> conv=sync
Replace <dev> with the USB drive’s whole-device name. Before running the command, verify that <dev> is the USB drive’s whole-device name rather than a partition.
Step 4: Boot From the New USB Image
- Leave the newly created USB drive connected.
- Restart the computer.
- Open the one-time boot menu rather than relying only on permanent boot priority.
- Select the entry for the USB drive, preferably the one marked
UEFI. - Wait for the MemTest86 startup screen.
If Windows still loads, return to the boot menu and check whether there are two entries for the same USB stick. Choosing the non-UEFI entry can cause a UEFI-oriented MemTest86 image to be skipped.
If the drive is still not present, try another direct USB port and then recreate the image on a different USB stick if possible. Testing the newly created stick on another UEFI-capable computer is useful: if it boots there, the original PC’s firmware is the likely cause.
Step 5: Confirm That the Fix Worked
A successful fix gets you to the MemTest86 interface, where the program detects memory and begins or offers to begin testing. At that point, the USB creation and boot-recognition problem is resolved.
If it starts but locks up when using multiple processors, switch it to single CPU mode and retry.
When the USB Is Valid but MemTest86 Still Will Not Start
A correctly written USB image can still fail because MemTest86 depends on motherboard-provided UEFI services.
That means a stick can boot normally on one computer and fail on another even when both systems support UEFI. Firmware updates can resolve some of these problems, especially when the failure happens after the MemTest86 splash screen rather than before the computer recognizes the USB drive.
Check for a Firmware Compatibility Restriction
MemTest86 includes a blacklist.cfg file for baseboards known to have firmware issues. When MemTest86 finds a matching motherboard entry, it may restrict features so the program can start instead of failing entirely.
Do not delete this file to “unlock” features. The restriction may be what prevents a startup failure or multiprocessor freeze. A matching entry can, for example, restrict multiprocessor testing.
If MemTest86 freezes when attempting to use additional processors, run it in single CPU mode. Updating the motherboard’s UEFI firmware may also restore normal multiprocessor operation. MemTest86’s known-issues documentation explains that firmware differences can affect mouse support, keyboard support, processor testing, display behavior, and startup reliability.
ASUS Systems With an Optical Drive
Some ASUS systems with an optical drive can fail to boot MemTest86 because of a UEFI firmware issue involving CD-media filesystem detection.
Before retrying the USB boot:
- Remove any CD or DVD from the optical drive.
- Restart and select the MemTest86 USB from the boot menu.
- If the system still fails and you can do so safely, disconnect the optical drive and retry.
This workaround applies when the ASUS system has an optical drive and inserted disc media; it is not a general requirement for every MemTest86 USB.
Keyboard and Mouse Problems After Boot
A USB keyboard or mouse can stop working in MemTest86 when the motherboard firmware does not provide the required UEFI input support. Try navigating with the keyboard if the mouse does not respond.
If neither works, update the system firmware if an update is available, or try a different keyboard connection type. This is a firmware support limitation, not evidence that the USB image was created incorrectly.
When Windows Cannot Read the MemTest86 USB Drive
Do not use Windows File Explorer as the only test of whether a MemTest86 USB was created correctly. A disk image can use partitions that look unfamiliar, have no normal drive letter, or prompt Windows to format the device.
In particular, Windows XP 32-bit cannot read MemTest86 USB flash drives because it does not support GPT disks. The USB-writing process did not fail. Test the stick by booting it on a compatible UEFI computer instead.
Do not allow Windows to format the stick after writing the image. Formatting it removes the bootable MemTest86 structure and turns it back into an ordinary storage drive.
How to Prevent the Problem Next Time
Use this short checklist whenever you make a new MemTest86 USB:
- Download the current UEFI-compatible MemTest86 package, not the legacy V4 build.
- Write the supplied image with ImageUSB on Windows, or write the image to the whole disk device on Linux or macOS.
- Back up the USB first because image writing erases existing files.
- Select the
UEFIUSB entry from the one-time boot menu. - If the image boots on another machine but not yours, focus on motherboard firmware and known compatibility issues.
- Keep
blacklist.cfgon the created USB drive. - Remove inserted CD or DVD media on affected ASUS systems with optical drives.
If the rebuilt stick appears in the boot menu and opens the MemTest86 test screen, proceed with memory testing. If it remains absent after trying another port and another USB stick, check for a motherboard firmware update or contact the system or board manufacturer with the motherboard model, firmware version, and the exact boot-menu behavior.
Frequently Asked Questions
Why is my USB drive not detected by MemTest86?
MemTest86 does not detect a USB drive from inside Windows; your computer’s UEFI firmware must recognize the drive as bootable before MemTest86 can start. Recreate the stick by writing the image with ImageUSB on Windows, then choose the USB’s UEFI entry from the boot menu. If the stick works on another computer, the original machine’s firmware is likely the issue.
Why does selecting the MemTest86 USB just boot Windows?
If selecting the MemTest86 USB starts Windows, the firmware may not find a valid boot image or the non-UEFI entry may have been selected. Recreate the USB by writing the image rather than copying files, then choose the entry labeled UEFI for that drive. Using an old legacy MemTest86 V4 release on a modern UEFI PC can also cause this behavior.
How do I format a USB drive for MemTest86?
You normally do not need to format it manually first. ImageUSB overwrites the selected USB drive and writes the required bootable disk image. Save any files elsewhere before starting because the image-writing process erases the drive.
Can I use MemTest86 without a USB drive?
MemTest86 runs before the operating system, so a full pre-boot memory test requires removable boot media rather than a normal Windows session. A USB drive is the standard removable medium because it lets MemTest86 test memory before Windows and most background software start.
Why does MemTest86 freeze after it starts?
A freeze after startup can be a motherboard UEFI compatibility issue, especially during multiprocessor initialization. Run MemTest86 in single CPU mode and consider updating the motherboard firmware. Keep the included blacklist.cfg file intact because it can apply restrictions needed for affected baseboards to run.
Why can’t Windows XP read my MemTest86 USB stick?
Windows XP (32-bit) lacks GPT disk support, so it cannot read the MemTest86 USB disk layout. The stick may still be correctly created and bootable on a compatible UEFI system, so test it by restarting a supported computer and selecting the USB from its boot menu.
