AleGr MEMTEST: Complete Guide to Memory Diagnostics and Fixes

Troubleshooting RAM Failures with AleGr MEMTEST: Step‑by‑Step

Overview

AleGr MEMTEST (AleGR MemTest) is a DOS-based, low-level RAM tester often used for thorough memory diagnostics. This guide gives a concise, practical workflow to identify, isolate, and resolve RAM failures using AleGr MEMTEST.

Before you begin

• Prepare: A bootable FreeDOS USB (or DOS environment) and AleGR MemTest.exe (and optional GETMEM utility).
• Safety: Power off and ground yourself before touching components. Note AleGr can draw high current on some notebooks—expect possible shutdowns.

1) Create bootable DOS media and add tools

1. Format a USB drive as FAT32 and make it FreeDOS-bootable (many tools/tutorials exist).
2. Copy AleGR MemTest.exe to the USB.
3. (Optional) Copy GETMEM to help detect usable memory ranges.

2) Boot the system to DOS and determine memory range

1. Boot the target machine from the USB into FreeDOS.
2. Run GETMEM (if available) and note the reported free memory START and SIZE values (useful defaults).
3. If GETMEM is unavailable, use SIZE ≈ total RAM under 4GB (AleGR DOS version cannot test above 4GB).

3) Run AleGr MEMTEST with safe parameters

1. From DOS run: memtest START SIZE
   • Example: memtest 1 1014 (starts at 1MB, tests 1014MB).
2. Avoid testing below 1MB (BIOS/ROM usage) and avoid including memory mapped I/O—reduce SIZE if failures cluster near top addresses.
3. Let tests run multiple passes (aim for many passes; at minimum 4–8, ideally 64 if time allows).

4) Interpret failures

• Consistent failures at same addresses: Likely real RAM faults or bad DIMM/contact.
• Many consecutive addresses near top: Possibly wrong SIZE parameter or testing non-existent/reserved regions—reduce SIZE and retry.
• Intermittent single-bit failures: Could indicate marginal RAM, poor contact, timing/voltage, or motherboard issues.
• Errors only under combined loads: Could be power/EMI or memory controller instability.

5) Isolate the faulty module or configuration

1. Power off, remove all DIMMs except one. Test each module individually in the same slot for several passes.
2. If individual sticks pass, test them in other slots to check motherboard slot issues.
3. If only a particular combination fails, test all pairings to find the bad module or incompatible pair.
4. When using more than two modules, test subsets to isolate.

6) Try quick fixes and retest

• Reseat modules and clean contacts (use compressed air or alcohol if corroded).
• Swap slots to rule out a bad slot.
• Reset BIOS to defaults (disable overclock/XMP) and test again.
• Lower memory frequency or loosen timings in BIOS; increase DRAM voltage slightly if stable and supported (conservative steps only).
• Test with single-channel vs dual-channel configurations to observe differences.

7) Special cases

• Notebooks that power off during test: Use shorter tests, reduce tested size, or test DIMMs individually; consider testing on a desktop motherboard if possible.
• Memory above 4GB: DOS AleGR cannot cover >4GB; use the Windows memory diagnostic or a UEFI memtest to test higher memory regions.
• Row‑hammer (hammer test) style failures: If errors appear on specific aggressive patterns, consider replacing affected modules—some DRAM exhibits disturbance faults.

8) When to replace hardware

• Replace any DIMM that consistently fails across slots and after reseating.
• If all DIMMs pass individually but errors appear in multi‑DIMM configurations, suspect motherboard, memory controller, or power delivery; try BIOS updates, different DIMM combinations, or replace the motherboard/CPU as needed.

9) Logging and reporting

• Note failing addresses and patterns. If vendor RMA is needed, include AleGR failure addresses, number of fails, test parameters (START, SIZE), and hardware configuration (DIMM model, motherboard, BIOS version).

Quick checklist (condensed)

1. Make FreeDOS USB with AleGR MemTest (+GETMEM).
2. Boot DOS, determine START/SIZE (avoid <1MB).
3. Run memtest; let multiple passes complete.
4. Isolate by testing DIMMs one-by-one and in different slots.
5. Reseat, swap, reset BIOS, reduce speeds/loosen timings, increase voltage cautiously.
6. Replace consistently failing DIMMs; investigate motherboard/CPU if problems persist.
7. Log results for RMA or further support.

If you want, I can turn this into a printable step‑by‑step checklist, or produce exact example memtest commands for a specific RAM size and configuration—tell me your total RAM and whether you’re testing a desktop or laptop.