You just closed the case, powered on, and Windows loaded for about five minutes before the screen froze and you got the 0x0000001A stop code. Or maybe it happened during a game, or right when you opened Chrome. The common thread: it only started after you installed new RAM. You ran MemTest86 and it spat out errors in the double digits.
What's actually happening here is that your motherboard motherboard is applying the worst possible settings for the new memory. The sticks you bought advertise speed—say, DDR4-3600 CL18—but the motherboard defaults to the JEDEC base spec, which is usually 2133 or 2666. That part works fine. The crash happens when you enable XMP, because XMP contains a memory profile that your particular CPU memory controller can't handle at the advertised frequency.
Why XMP Isn't the Answer
XMP (eXtreme Memory Profile) is a set of overclocking parameters stored on the stick itself. It reads out timings, voltage, and frequency. Those values are tested by the module maker, but they're tested on their own board, not yours. Your CPU's integrated memory controller (IMC) might be a dud, or your motherboard's BIOS has an older version that doesn't properly handle the secondary timings. Result: instability that only appears under load, and MemTest shows errors because the data lines are marginal.
Also realize that XMP is technically a factory overclock. For DDR4-3600, the controller has to run in gear 1 mode to hit that speed. On many CPUs (especially 10th and 11th gen Intel), gear 1 tops out around 3200. If your board forces gear 2 at 3600, latency jumps and you can get random corruption.
The Fix: Manual Settings, Not XMP
- Reset your BIOS entirely. Enter the BIOS (usually
DelorF2during boot) and load defaults. This clears any leftover XMP profile or auto-OC settings. - Set frequency manually to the DDR rating minus one step. For a 3600 kit, start at 3200. For 3200, try 2933. This gives your IMC breathing room.
- Set DRAM voltage to 1.35V. Most kits rated under 4000 MT/s are fine there. If your kit is 1.2V low-voltage, bump to 1.25V instead—don't go straight to 1.35V because some LPX sticks don't like it.
- Copy the primary timings from the XMP profile, but add +1 to each. So if the kit says 18-22-22-42, set 19-23-23-43. This relaxes the timings enough to compensate for the lower frequency.
- Set Command Rate (CR) to 2T. If it's set to 1T, change it. On two single-rank sticks in dual channel, 1T is often unstable at moderate frequencies. 2T adds a clock cycle but buys huge stability.
- Save and exit. Then run MemTest86 for at least one full pass (or four passes if you're patient). If it passes, boot into Windows and stress with
TestMem5using the "1usmus" config for an hour.
If it still crashes, then the problem isn't just timings. It's slot placement or the sticks themselves.
What to Check If It Still Fails
First verify you're using the correct slots. Consumer boards typically want sticks in slots A2 and B2 (second and fourth from the CPU). If you put them in A1 and B1, dual channel mode won't engage, and that alone can cause blue screens. Pull two sticks out if you have four and run two-by-two to isolate a bad stick.
Second, update the BIOS. Manufacturers add memory compatibility updates all the time. The original release BIOS for your board probably predates the RAM kit you bought. Check the motherboard support page, flash the latest Efi (use the USB Flashback slot if you have one), then re-enter your manual settings.
Third, inspect the sticks. If you bought four sticks and you're running two, those other two might be garbage. Test each stick individually in slot A2. If one fails and the other doesn't, return the bad one. RAM is the one component where DOA or early failure is shockingly common.
Finally, if nothing works, drop frequency to the JEDEC default (2133 or 2666). That's the baseline that the memory controller must support. If you get a clean system at that speed, the kit itself is compatible, but your board can't hit the rated speed. Honestly? That's rare—most boards hit rated speed with a fresh BIOS. But if you've got a 13th gen Intel CPU on a B660 board, the memory controller might not be as strong as the 14th gen refresh. Don't be dramatic about it. Just run at 3200 and use the savings to buy a kit that's on the motherboard QVL list next time.