Memory Problems: Freezes, Crashes and Missing RAM

Memory faults produce symptoms that look like almost anything else — freezes, crashes, corrupted files, a machine that will not start. And the most common memory complaint, half the RAM missing, is usually not a fault at all.

Symptom 1: only some of the memory is recognised

You installed 16 GB and the system reports 8. Alarming, and usually fixable in minutes.

The causes, in order of likelihood

A module not fully seated. The most common by a wide margin. Memory needs firm pressure until both retaining clips click. A module that looks seated frequently is not.

The fix: power off, unplug, remove and refit each module firmly. Press at both ends until the clips engage themselves.

Wrong slots. With two modules in a four-slot board, the manual specifies which pair. The wrong pair can mean one module is not detected at all.

A faulty slot rather than a faulty module. Test by swapping — put the suspect module in a known-good slot. If it appears, the slot is at fault. If it does not, the module is.

Dust or debris in the slot. Compressed air, with the machine unplugged.

Memory reserved for integrated graphics. A machine with 8 GB may report slightly less usable, because graphics has taken a share. Normal, and usually adjustable in firmware.

Hardware reserved memory, a small amount set aside by the system. Also normal.

A 32-bit operating system, which cannot address more than about 4 GB regardless of what is installed. Rare now and it still catches people with older machines. Check whether your system is 32 or 64-bit.

A memory limit set in the boot configuration. In Windows, a maximum memory setting can be enabled in the system configuration tool and forgotten. Worth checking — it takes a minute and it fully explains the symptom when set.

Firmware too old to support the capacity or the module type. Check the board's supported memory list and whether a firmware update is available.

The diagnostic sequence

1. Check the reported figure in firmware, not just in the operating system. If firmware sees all of it and the system does not, the problem is software — boot configuration or the 32-bit limit.

2. If firmware also sees less, it is physical. Reseat, then test each module individually in the first slot.

3. One module at a time, in the same slot, identifies a bad module. The same module in different slots identifies a bad slot.

Symptom 2: freezing and crashing

Memory can cause this, and so can several other things. Establish which before replacing anything.

Testing memory properly

Windows has a built-in memory diagnostic which runs at startup. Adequate for finding obvious faults.

Dedicated bootable testing tools run far more thorough passes and catch faults the quick test misses. A single pass is not enough — intermittent faults appear only after hours. Run overnight if you suspect memory.

Any error at all means a fault. Memory testing does not produce false positives in the way other diagnostics do.

Test one module at a time once you have an error, to identify which.

When it is not memory

Overheating — a machine that is fine for ten minutes then freezes. Check temperatures under load.

Power supply — freezes and sudden restarts under load, with no errors in a memory test. Frequently misdiagnosed as memory.

Storage — a failing drive produces freezes while the system waits for a read that never completes. Check drive health.

Drivers, particularly graphics. See graphics card problems.

Overclocking, whether yours or a factory memory speed profile. Return everything to default and retest — this alone resolves a substantial share of "faulty memory" cases.

Symptom 3: the machine will not start after adding memory

Common after an upgrade and rarely a defective module.

Not seated — the usual cause.

Wrong slots — check the manual.

Speed profile beyond what the board or processor supports. Memory rated above the supported speed usually falls back automatically, and occasionally does not. Reset firmware to default, then enable the profile afterwards if you want the rated speed.

Mixed modules. Different speeds, capacities or manufacturers may not work together. Test each alone.

Firmware too old for the memory generation.

See motherboard lights on but won't start.

Symptom 4: high memory usage without a fault

Not a problem, and frequently reported as one.

Modern systems use available memory for caching. Unused memory is wasted memory, so the system fills it with things you might need. This is deliberate and it is released when applications need it.

High memory usage is only a problem when the machine slows down as a result — when the system starts moving data to disk. That is the symptom to watch, not the percentage.

Browsers are the usual heavy consumer. Many tabs and extensions genuinely use a lot, and closing some is a valid response.

Check whether one process is growing continuously, which indicates a leak in that application rather than a memory shortage. Restarting the application, not the machine, is the fix.

When to replace

A confirmed error in testing, isolated to a specific module.

A module that is not detected in a known-good slot.

Memory is frequently covered by a long warranty, sometimes lifetime. Check before buying — manufacturers in this category honour it more readily than most.

Replace in matched pairs where possible, for dual-channel operation. See RAM explained.

The short version

Half the memory missing is usually seating, not a fault. Reseat firmly until both clips click.

Check firmware first. If firmware sees all of it and the system does not, the problem is software — the 32-bit limit or a boot configuration setting.

One module at a time in the same slot identifies a bad module; one module across slots identifies a bad slot.

Run a thorough memory test overnight, not a single quick pass — intermittent faults hide from short tests.

And return overclocking and memory speed profiles to default before concluding anything, because that alone explains a large share of suspected memory faults.

For hardware identification, repair and teardown references, see iFixit PC guides.