RAM Not Detected? 10 Ways to Fix It

A new stick invisible in BIOS, or Windows showing less memory than you installed — work through these ten checks in order.

Updated 11 Nov 2026 · 9 min read

What “not detected” actually means

“Not detected” can mean three different things. First, the BIOS total is short: the stick is invisible before Windows loads, so the cause is seating, slots, compatibility, or a dead stick. Second, the BIOS shows the full amount but Windows shows less: that is a Windows setting, a 32-bit install, or hardware reservation, and the stick is fine. Third, a game or app reports less than Windows: that usually means video memory (VRAM), not system RAM. Check the BIOS total first — that one number splits the problem in half.

How to fix RAM not detected: the 10 fixes, in order

Work through these in order and stop as soon as the stick appears.

1. Reseat the stick. Power off, unplug, press it straight down until both clips click.
2. Use the right slots. One stick goes in A2; two sticks go in A2 + B2.
3. Clean the contacts. Rub the gold fingers gently with a pencil eraser, brush away debris, reseat.
4. Test one stick at a time in A2. This separates a bad stick from a bad slot.
5. Swap slots. A stick that works in A2 but not B2 points at the slot or the CPU’s memory channel.
6. Update the BIOS. Newer BIOS versions add memory compatibility, especially on DDR5 boards.
7. Clear CMOS to wipe a bad XMP/EXPO profile, then boot at stock speeds.
8. Check for bent CPU pins or uneven cooler pressure — both can kill one memory channel.
9. Check Windows limits: run msconfig → Boot → Advanced options, and make sure ‘Maximum memory’ is unticked. Also see RAM not showing full capacity.
10. Run MemTest86 from a USB stick. A stick that errors or vanishes under test is faulty — RMA it.

BIOS sees it but Windows doesn’t (or vice versa)

If the BIOS reports the full capacity but Windows shows less, the problem is software. A 32-bit Windows install can only use around 4GB, so upgrading to 64-bit Windows is the only fix there. The msconfig memory cap from step 9 above is the next suspect, and it is surprisingly common after following bad optimisation guides. After that, look at hardware reservation — see hardware reserved RAM for the full breakdown, but the short version is that integrated graphics can reserve several gigabytes before Windows ever sees them.

How to tell a dead stick from a dead slot

Test the suspect stick alone in slot A2. If it boots and shows its full capacity, the stick is good and the problem is the slot, the channel, or the seating. If it fails in A2 while the other stick works in A2, the stick is faulty — confirm it in a second PC if you can, then claim the warranty. Next, put the known-good stick in the suspect slot. A stick that is detected but errors in MemTest86 is marginal, not dead — it causes crashes instead; see our guide to RAM causing blue screens.

iCUE not detecting RAM

iCUE is Corsair’s software for controlling RGB lighting, and “iCUE not detecting RAM” usually does not mean the RAM is broken. First check Task Manager: if Windows sees the full capacity, your RAM is fine and this is purely a software problem. iCUE only controls Corsair RAM (Vengeance, Dominator, and similar) — RAM from other brands will not appear in iCUE at all, and that is expected, not a fault.

OpenRGB not detecting RAM

OpenRGB is a free, open-source tool for controlling RGB lighting across brands, and it detects RAM over the same SMBus connection that iCUE uses — so the causes and fixes are similar. As with iCUE, check Windows first: if Task Manager shows the full capacity, the RAM is healthy and OpenRGB simply cannot reach it. The most common cause is a conflict: close iCUE, Armoury Crate, MSI Center, and any other RGB tool before starting OpenRGB, because only one program can control the SMBus at a time.

Common mistakes that make it worse

The most common mistake is forcing a stick. If it does not slide in with firm, even pressure, stop: check the notch alignment, the generation, and that the slot clips are fully open. Forcing a DDR4 stick into a DDR5 slot (or the reverse) can crack the slot and the stick. The second mistake is changing three things at once — reseating, clearing CMOS, and updating the BIOS in one go — and then having no idea which one fixed it.

Verdict: replace it or keep it?

Keep the stick if reseating, correct slots, clean contacts, or a BIOS update brings it back and it then passes four passes of MemTest86 without errors. Replace it under warranty if it fails alone in A2, fails in a second PC, or produces MemTest86 errors at stock speeds; most quality RAM carries a lifetime warranty. Replace the board, not the RAM, if the good stick fails in one specific slot after you have ruled out cooler pressure and bent pins.

Frequently asked questions