You dropped 32GB into your build, Windows boots fine, and then the System panel says something like “16.0 GB (8.00 GB usable)”. Half your memory just vanished on paper. It’s one of the most common head-scratchers people run into after a memory upgrade, and the good news is that most of the time the sticks are perfectly healthy. The problem sits somewhere between a Windows checkbox, a DIMM that isn’t fully clicked in, and a slice of memory your integrated graphics quietly borrowed.
This guide walks through the real causes in the order you should check them, from the free 30-second fixes to the “yes, a stick actually died” scenarios. If your upgrade came from one of our picks in the best 32GB RAM kit 2026 roundup, or you’re pairing sticks with a fast CPU like the ones in our best RAM for gaming and video editing guide, the same logic applies. Let’s find your missing gigabytes.
First check the obvious (the 30-second check)
Open Task Manager, click the Performance tab, and select Memory. Look at two numbers: “Hardware reserved” at the bottom, and the total slots in use. If Windows sees the full amount installed (say 32GB) but only reports half as usable, that points to a software limit or reserved memory. If Windows itself only sees half the physical amount installed, that’s a hardware or seating problem instead. This one distinction tells you which half of this article to read.
While you’re here, press Windows key plus R, type msconfig, and hit Enter. Under the Boot tab, click Advanced options. There’s a “Maximum memory” checkbox that, when ticked, caps how much RAM Windows will address. It’s the single most common cause of this whole mess, and clearing it takes one click. We’ll cover it first because it costs nothing.
One more free check before you open the case: reboot into BIOS and look at the memory readout on the main screen. This tells you what the motherboard itself detects, which is the ground truth beneath whatever Windows reports. If BIOS shows the full 32GB but Windows shows half, your problem is software (the msconfig cap or a reserved-memory setting). If BIOS itself only counts half, the issue is hardware, and no amount of Windows tweaking will help. Splitting the diagnosis this early saves you an hour of chasing the wrong layer.
Cause #1: The msconfig maximum memory cap
Here’s the trap. Some folks tick “Maximum memory” in msconfig to troubleshoot an old issue, or a random guide told them to, and then they forget it’s on. Windows dutifully limits itself to whatever value sits in that box. If it reads 8192, you get 8GB usable no matter how much you installed. The physical sticks are fine. Windows just isn’t allowed to touch them.
The fix is simple. In msconfig, Boot tab, Advanced options, uncheck the “Maximum memory” box entirely (don’t just change the number, clear the checkbox). Click OK, apply, and reboot. Recheck the System panel. If your full capacity is back, you’re done and you never needed a screwdriver. If the box was already unchecked, move on. That means Windows was never the bottleneck, and the missing memory is physical or reserved.
One related gotcha lives in the BIOS. A setting called Memory Remap Feature (sometimes labeled Hardware Memory Hole or 4G Decoding) needs to be enabled so the system can address memory above the 4GB line. On most modern boards it’s on by default, but if you flashed a fresh BIOS or reset to defaults, it’s worth confirming. Disabled, it can strand everything past the first 4GB even on a healthy 64-bit install. Enable it, save, reboot, and recheck.
Cause #2: A DIMM that isn’t seated, or a dead stick
If Task Manager only counts half the sticks you installed, one module isn’t making contact. RAM slots use retention clips at both ends, and a stick can feel “in” while one corner is still lifted a millimeter. That’s enough to drop it entirely. Power down, unplug the PSU, press the case power button to drain residual charge, then press firmly on both ends of each DIMM until both clips snap up on their own. You’ll usually hear a distinct click.
Still half? Swap slots. Move the “invisible” stick into a slot that you know works, and see if it registers. If a single stick refuses to appear in any slot but its partner always works, that stick is likely dead and you’ll want a matched replacement rather than a single mismatched module. For a DDR4 board, a proven kit keeps timing and capacity consistent across both channels.
Before you condemn a stick, clean the contacts. Gold fingers pick up oxidation and skin oil, and a filmy contact reads as intermittent or absent. Rub the gold edge gently with a clean pencil eraser, blow off the crumbs, and reseat. It sounds like folklore, but it revives more “dead” sticks than people expect. Also inspect the slot itself for a bent or pushed-back contact leaf, which no amount of reseating will fix.
Pros
- DDR4-3600 XMP at 1.35V is the Ryzen AM4 sweet spot, aligning FCLK 1:1 at 1800MHz for best latency.
- Matched 2x16GB kit is factory-tested as a pair, reducing dual-channel instability compared to mixing sticks.
- Compatible with both Intel XMP and AMD DOCP/A-XMP BIOS profiles without manual sub-timing adjustments.
- Ships with JEDEC SPD fallback so the system always boots safe at default clocks before XMP is enabled.
Cons
- CL18 primary latency is mid-range; DDR4-3600 CL16 kits exist for buyers prioritizing tighter timings.
- No ECC support, so workstation or Threadripper ECC builds need a different kit entirely.
The G.SKILL RipjawsV F4-3600C18D-32GVK is a mid-range DDR4 desktop kit targeting Intel and AMD mainstream platform builders who want 32GB capacity at DDR4-3600 without overpaying for CL14 or CL16 enthusiast kits. It ships as a matched 2x16GB dual-channel pair in the standard 288-pin U-DIMM form factor.
The defining spec here is the XMP profile: DDR4-3600 at CL18-22-22-42, 1.35V. On AMD AM4 Ryzen systems, 3600MHz is the well-documented sweet spot for achieving a 1:1 FCLK ratio at 1800MHz, which keeps infinity fabric latency in check and translates to measurable gains in lightly-threaded workloads and gaming frame times compared to DDR4-3200 or lower.
CL18 is a genuine trade-off at this speed. Competing DDR4-3600 kits with CL16 or CL14 exist and offer lower absolute latency, though they typically carry a price premium. Owners report stable XMP operation across a wide range of B450, X570, and Z490/Z590 boards, but reaching rated speed on some budget AM4 boards may require manual sub-timing adjustments or AGESA microcode updates.
Buy this if you are building or upgrading an AM4 Ryzen or Intel LGA1700 desktop and want reliable 32GB DDR4-3600 dual-channel performance without tuning. Skip this if you need CL16 or tighter for competitive latency, or if your board has a limited QVL and you have not verified compatibility via G.SKILL's configurator tool first.
Platform Support: This kit uses 288-pin DDR4 U-DIMM and is compatible with Intel LGA1700 (Z690/Z790) and AMD AM4 (B450/X470/B550/X570) platforms. AM5 uses DDR5 exclusively, so this kit is not compatible with Ryzen 7000/9000 series builds on AM5 boards.
XMP and DOCP Activation: Rated speed of DDR4-3600 CL18-22-22-42 at 1.35V requires enabling XMP (Intel) or DOCP/A-XMP (AMD) in BIOS. Default JEDEC SPD boots at DDR4-2133 or DDR4-2400. On AM4, DDR4-3600 aligns FCLK at 1800MHz for a 1:1 ratio, which is the recommended operating point for Ryzen 3000 and 5000 series CPUs.
Slot Population and Mixing: Install both sticks in the recommended dual-channel slots per your motherboard manual, typically A2 and B2 in a 4-slot board. G.SKILL explicitly warns against mixing this kit with other modules; doing so voids the matched-pair guarantee and risks instability at XMP speeds.
Cooler Clearance: Exact heatspreader height is not specified in the source data, but RipjawsV modules are noted for a lower profile than Trident Z or RGB variants, reducing conflicts with wide tower coolers. Verify clearance if using a low-clearance cooler on a tight ITX board.
The G.SKILL RipjawsV DDR4 32GB (2x16GB) kit runs at 3600MT/s with CL18-22-22-42 timings at 1.35V, and it carries a 4.6 rating. Buying a matched 2x16GB pair rather than mixing a lone survivor stick with a new one avoids the flaky dual-channel behavior that causes half your RAM to disappear in the first place. Two identical modules, one XMP profile, done.
Cause #3: Integrated graphics and hardware reserved memory
On systems using an integrated GPU (a CPU with built-in graphics and no discrete card), the iGPU carves out a chunk of system RAM for video memory. That’s normal, but a misconfigured BIOS setting can hand it far more than it needs. Check “Hardware reserved” in Task Manager. A few hundred megabytes is expected. Several gigabytes means something’s wrong. In BIOS, look for a setting named UMA Frame Buffer Size, iGPU Memory, or DVMT, and set it to a sane value like 512MB or 1GB instead of Auto or a huge fixed block.
There’s also the plain 32-bit ceiling. A 32-bit copy of Windows can only address roughly 3.5GB total, so any modern kit will look brutally cut in half or worse. Verify you’re running 64-bit under Settings, System, About. If you built a DDR5 machine and one channel dropped after adding a stick, a clean matched pair often restores full capacity and stability at rated speed.
DDR5 adds one more wrinkle worth knowing. These kits run a memory training routine on the first boot after any change, and that pass can take thirty seconds to a couple of minutes with a black screen. Some folks panic, cut the power mid-train, and end up with a board that fell back to a single channel or a safe default. Let the first post finish untouched. If capacity still reads low afterward, re-enable EXPO or XMP, because a failed training run sometimes drops the profile and quietly halves your effective bandwidth even when the full capacity shows.
Pros
- AMD EXPO profile activates 5200MHz CL40-40-40-77 with a single BIOS toggle on Ryzen 7000 boards.
- Low 35mm module height clears virtually any AM5 or LGA1700 tower cooler without physical conflict.
- 1.25V operating voltage sits within DDR5 spec, reducing thermal stress on integrated PMIC under sustained load.
- Aluminum heatspreader aids passive heat dissipation in open-air cases without requiring active cooling.
Cons
- 16GB total capacity is increasingly marginal for content creation workflows and modern open-world titles running texture packs.
- 5200MHz CL40 offers modest latency compared to DDR5-6000 CL30 kits that hit the Ryzen 7000 FCLK 1:1 ratio sweet spot.
The CORSAIR Vengeance DDR5 16GB 2x8GB is a mid-range DDR5 kit targeting AMD Ryzen 7000 series and Intel 12th-generation-or-newer desktop builds. It ships with both AMD EXPO and Intel XMP 3.0 profiles, making it broadly compatible across AM5 and LGA1700 or LGA1851 platforms without manual timing configuration.
The standout feature is dual-profile support at a frequency that loads with a single BIOS toggle. At 5200MHz CL40-40-40-77 and 1.25V, it sits within DDR5 JEDEC specification territory, and onboard voltage regulation on the module itself reduces dependency on motherboard power delivery for the memory rail, which matters on budget AM5 boards with fewer VRM phases dedicated to DRAM.
The honest trade-off at this tier is frequency positioning. Ryzen 7000 performs best at DDR5-6000 with CL30 timings, where FCLK and memory controller run at a clean 1:1 ratio. This kit at 5200MHz places it below that threshold, meaning buyers on AM5 leave some CPU bandwidth on the table. The 16GB total capacity is also worth scrutinizing for any workload beyond gaming or light productivity.
Buy this if you are building a budget-to-mid AM5 or Intel DDR5 system and need reliable plug-and-play EXPO or XMP activation without manual overclocking. Skip this if your platform is AM5 and you plan to run a Ryzen 7000 CPU near its performance ceiling, where DDR5-6000 CL30 kits deliver measurably better throughput and latency at comparable pricing.
Platform Requirements: DDR5 requires AMD 600-series or newer motherboards paired with Ryzen 7000 series or newer CPUs, or Intel 600-series or 700-series boards with 12th-generation Core or newer. DDR5 is not backward compatible with DDR4 slots. Verify your motherboard QVL lists this kit before purchasing.
EXPO and XMP Activation: The rated 5200MHz speed requires enabling AMD EXPO or Intel XMP 3.0 in BIOS. Without activation, the kit defaults to DDR5-4800 JEDEC. On Ryzen 7000, DDR5-6000 is the accepted 1:1 FCLK sweet spot; this kit at 5200MHz runs below that threshold, which carries a small but measurable bandwidth and latency penalty versus a tuned DDR5-6000 kit.
Physical Clearance: Module height is 35mm, which clears nearly all air coolers without conflict. The 1.25V operating voltage and onboard PMIC mean power comes from the module itself rather than solely from the motherboard, reducing stress on budget boards with lighter DRAM power stages.
Capacity and Channel Config: The 2x8GB configuration fills two slots in dual-channel. CORSAIR explicitly advises against mixing kits, so expansion to 32GB requires replacing both modules with a validated 2x16GB kit rather than adding a second 2x8GB pair.
The Corsair Vengeance DDR5 16GB (2x8GB) kit runs up to 5200MHz at CL40 with both AMD EXPO and Intel XMP 3.0 profiles, and it holds a 4.4 rating. On a DDR5 platform, populating the correct two slots (usually A2 and B2, per your motherboard manual) with a matched pair is what gets you clean dual-channel operation. Mixing random single sticks is exactly how people end up staring at “8GB usable” again.
Preventive maintenance
Two habits prevent most repeat cases. First, always buy RAM as a matched kit rather than adding a lone stick later, since kits are binned to run together. Second, after any upgrade, enable your XMP or EXPO profile in BIOS and then run a quick memory diagnostic (Windows Memory Diagnostic or a bootable memory checker) to confirm both sticks pass before you trust the machine. A stick that boots but throws errors under load can present as intermittent capacity loss, and it’s far easier to catch it on day one than three weeks in.
Keep your BIOS reasonably current, too. Memory compatibility improves with AGESA and microcode updates, especially on AM5 and newer Intel boards, and a kit that half-registers on a launch-day BIOS sometimes runs flawlessly after a single flash. Note your working settings before you update, since a BIOS flash resets everything to defaults and you’ll want to re-enable EXPO and the memory remap option afterward. Snap a phone photo of your key BIOS screens so you can put it all back in two minutes.
When it’s not fixable: what to replace
If you’ve cleared the msconfig cap, reseated everything, swapped slots, and confirmed 64-bit Windows, and one stick still refuses to register in a known-good slot, that module has failed. Replace it. Don’t pair the survivor with a random new stick of a different speed or die revision, because mismatched modules are a classic source of the exact symptom you’re trying to escape. Buy a fresh matched pair and retire the old ones together. If multiple slots read dead across several sticks, the fault is the motherboard’s memory controller or a bent pin in the CPU socket, and that’s a board or CPU replacement rather than a RAM problem. Kits from our best budget RAM 2026 shortlist cover most DDR4 and DDR5 rebuilds without overspending.
Tools and parts needed
You need almost nothing for this. A Phillips screwdriver if you have to remove a GPU or cooler to reach the slots, an anti-static wrist strap or a grounded hand on the case, and good lighting to see the retention clips. The actual fix is usually free. Only Cause #2 and the failure scenario call for spending money, and only when a stick is genuinely dead. Keep your motherboard manual handy so you know which two slots to prioritize for dual-channel, because the correct pair is rarely slots one and two.
A few more questions
Why does Windows show installed but not usable?
That wording means Windows detects the physical RAM but isn’t addressing all of it. The cause is almost always the msconfig maximum memory cap, hardware reserved by an integrated GPU, or a 32-bit OS ceiling. Physical sticks that don’t show up at all point to seating or a dead module instead, which is a different fix.
Is a little hardware reserved memory normal?
Yes. A few hundred megabytes reserved is completely normal, since the system and any integrated graphics need working space. It only becomes a problem when several gigabytes show as reserved, which usually traces back to an aggressive iGPU frame buffer setting in BIOS that you can dial down.
Can mismatched RAM sticks cause this?
They can. Sticks with different speeds, capacities, or die revisions sometimes refuse to run in dual-channel, and the board may drop one to keep the system stable. That’s why a matched kit is the safer buy. If you’re mixing modules and seeing half your capacity, pull the odd one out and confirm the pair works alone first.
Write Your Review
No reviews yet. Be the first to share your experience!