Connexion
How to Tell If Your RAM Is Failing
Short answer: RAM faults show up as freezes, random restarts, blue screens, no display, or a PC that will not boot. Work in this order: clear the CMOS to remove XMP or EXPO from the equation, reseat the modules, then test one stick at a time starting in the fourth slot. Blue screen codes like MEMORY_MANAGEMENT and PAGE_FAULT_IN_NONPAGED_AREA point straight at memory.
RAM is the most common hardware fault in a PC, and there is a reason for that. Like the tyres on a car, it is the component under constant use. Every file opened and every program loaded runs through it, so it wears in a way other parts do not.
Symptoms that point at RAM
- Applications or games freezing, hanging or crashing
- Random restarts
- Blue screens (stop codes)
- No signal to the monitor
- Not booting into Windows
- Programs failing to install
That last one is a useful tell. Installers write a lot of data through memory, so a bad module often surfaces during an install before anywhere else.
Stop codes that commonly mean memory
- MEMORY_MANAGEMENT
- PAGE_FAULT_IN_NONPAGED_AREA
- DATA_BUS_ERROR
- CRITICAL_PROCESS_DIED
- IRQL_NOT_LESS_OR_EQUAL
If there is no display at all
Use the motherboard's debug LEDs or its two-digit display. On NZXT N series boards these sit along the bottom edge near the power and reset buttons. A lit DRAM LED tells you where it stopped without any guesswork.
Step 1: Clear the CMOS first
Always start here, before touching hardware. Memory settings such as XMP, EXPO or a manual overclock can produce errors that look exactly like a failing module. You want the system on stock settings before you conclude anything.
If you can reach the BIOS, use Load Optimized Defaults. If the PC will not POST or gives no display, clear the CMOS manually. Our guide to clearing CMOS covers all three methods.
One warning before you do. If you use BitLocker or any drive encryption tied to TPM or Secure Boot, disable the encryption first or have your recovery key to hand, and back up your TPM and Secure Boot keys per your motherboard manual. A CMOS reset can wipe those keys.
Step 2: Reseat the RAM
A loose module is a genuinely common cause, and reseating costs nothing.
Before opening the case: shut down, switch the power supply off at the rear, leave the PC plugged into a grounded outlet, and touch the metal chassis to discharge static. Use an anti-static wristband if you have one.
- Open the locking clips at the top and bottom of each slot. Some boards only have a clip at the top, with the bottom slotted instead.
- Pull each module out and inspect both module and slot.
- Look for cracks in the circuit board, torn contacts or scorch marks. Any of those means the module needs replacing.
- Clear any debris in the slot with compressed air or an ESD-safe brush.
- Reinstall one matched pair into the slots your manual specifies, usually slots 2 and 4.
Line the module up and press firmly with even pressure across the whole stick. Done right, the clips close by themselves.
Keep matched pairs together
Always keep pairs together, since mixing them invites a second problem on top of the one you are chasing. On most boards, matched pairs go in slots 2 and 4, and slots 1 and 3.
If you have already mixed them, the serial numbers sort it out. Modules from a pair differ by a single digit:
- xxxx-xxxx-xx01 and xxxx-xxxx-xx02 are one pair
- xxxx-xxxx-xx03 and xxxx-xxxx-xx04 are the other
Confirm Windows sees both
If it boots, open Task Manager, go to the Performance tab, and hover over Slots used. If a slot you populated reads as empty, that module or slot has failed.
Step 3: Isolate the faulty part
If it still will not boot, test methodically. Power off, remove all RAM, and separate matched pairs. Install a single stick in the fourth slot (furthest from the CPU) and try to boot. Repeat for every module and every slot, powering off completely between each change.
Read the result like this:
- Boots with one module but not another: that module is faulty and needs replacing.
- Boots with either module alone, but not both together: points at the motherboard or CPU rather than the RAM.
- Boots with a pair in one set of slots but not the other: also points at the motherboard or CPU.
That second and third case are the useful ones, because they stop you buying RAM that was never the problem. If the trail leads to the CPU or socket, our guide to CPU and socket problems picks it up from there.
Step 4: Test in software
If the PC boots but you still get crashes, restarts or stop codes, a memory test will find errors that intermittent use does not. Run it after you have cleared the CMOS, so you are testing the hardware and not an unstable overclock.
Frequently asked questions
Which RAM slot should I test a single stick in?
The fourth slot, furthest from the CPU, unless your motherboard manual says otherwise. Power down fully between every change.
Can XMP or EXPO cause memory errors?
Yes. Both are a form of overclocking, and an unstable profile produces errors that look identical to a failing module. Always clear the CMOS and test at stock before concluding the RAM is bad.
Why does my PC only see half my RAM?
Usually a module that is not fully seated, or a dead slot. Check Task Manager's Performance tab under Slots used, then reseat and test each slot with a known good stick.
Does mixing RAM kits cause problems?
It can. XMP and EXPO profiles are validated for a single matched kit. Mixing kits, or running more modules than one kit contains, is not guaranteed to be stable. Check your motherboard's Qualified Vendor List.
Can I mix different RAM speeds?
The system will typically run everything at the slowest module's speed, and stability is not guaranteed. A single matched kit is always the safer configuration.
My RAM tests clean but I still get blue screens.
Then memory is probably not your fault. Storage, GPU drivers or power delivery are the next places to look. A clean GPU driver install rules out a large category cheaply.
Need a hand?
Tell us your stop code and which slots you have tested and our team can narrow it down. Reach them at NZXT Support.
