When a desktop shows less RAM than you installed, or won't detect a new stick at all, four causes explain almost every case: the stick isn't fully seated, it's incompatible with the motherboard's supported list, the BIOS needs updating to recognize higher-capacity modules, or one stick has failed. Checking Task Manager's Performance tab tells you immediately how much the system currently sees versus what's physically installed.
Confirm What Windows Actually Sees First
Open Task Manager with Ctrl+Shift+Esc and go to the Performance tab, then Memory. It lists total installed capacity and how much is "usable." If usable is lower than installed, Windows sees the hardware but isn't using all of it, a different issue than a stick not appearing in BIOS at all. Note the exact numbers before you start swapping anything.
Reseat Every Stick, One Slot at a Time
Power down, unplug the PC, and touch a grounded metal surface before handling any stick. Remove all modules, then reinstall one at a time, pressing straight down until both clips click. A stick that isn't fully seated, often because the notch wasn't aligned correctly, is the single most common cause of a "no RAM detected" boot.
Does Your Motherboard's BIOS Need an Update?
Older motherboards shipped before certain high-capacity RAM kits existed, so they simply don't recognize anything above an older per-slot limit until the BIOS is updated. Check your motherboard manufacturer's support page for a BIOS revision released after your RAM kit's release date. If the board won't even boot to update the BIOS normally, a failing CMOS battery can also cause settings to reset and memory to misread on every startup.
Test Each Stick Individually to Isolate a Bad Module
Move one stick at a time into the same known-good slot. If the fault follows a specific stick wherever it goes, that module has failed. If the same slot keeps rejecting whichever stick you put in it, suspect the slot or the motherboard itself rather than the RAM. A RAM upgrade or replacement service can confirm which side of that is true with a known-good test kit.
Rule Out a Windows-Side Memory Limit
Sometimes the hardware is fine and Windows is capping it. Type msconfig into the Start menu, open the Boot tab, click Advanced options, and check whether "Maximum memory" is ticked with a low value left over from a previous troubleshooting session. Unchecking it restores full access immediately on reboot, no hardware work needed.
A Deeper Check: Channel Configuration and XMP Profiles
Populating RAM slots in the wrong pairing drops you to single-channel mode, which roughly halves memory bandwidth without throwing any visible error, it just runs slower in a way Task Manager won't flag. Check your motherboard manual for the correct slot pairing for dual-channel. Enabling XMP or EXPO in BIOS for the kit's rated speed can also occasionally push an unstable kit into intermittent detection failures, so testing at default JEDEC speed is worth it if problems started right after enabling it. If none of the above resolves things, the issue is likely a failed memory controller or physical slot damage, which a motherboard diagnostic can confirm before you assume the RAM itself is at fault.
