Blue Screens Started After Installing New RAM or SSD
New part in, blue screens start. The timing is not a coincidence, but the new part is not automatically defective either - seating, compatibility and settings cause most of these. Test in this order before returning anything.
Watch the full method in the video - identifying a blue screen cause, step-by-step
Post-upgrade blue screens have four usual explanations, and only one of them is a dead part: the RAM is not fully seated, the kit is unstable at its XMP speed on your board, the new stick does not match the old one, or - with an SSD - the clone carried problems or the drive needs a firmware or controller setting. The isolation method is simple: remove the new variable and see if the crashes leave with it. Work through the checks in order; each one takes minutes.
Task Manager - Memory after upgrade (example values)
Installed RAM32.0 GB
Speed3200 MT/s (XMP)
Slots used2 of 4
Hardware reserved2.1 GB
Example only - if Windows shows less RAM than you installed, or an odd reserved amount, a stick is not seated or not recognised properly.
Example memory view. First confirm Windows sees the full, correct amount of RAM at the expected speed.
1
Reseat the RAM - the Five Minute Fix That Works Embarrassingly Often
A stick that is a fraction of a millimetre out still boots - then corrupts memory randomly under load.
Power off, unplug, and press the case power button once to drain charge
Remove each new stick and refit it until both end clips snap in by themselves
Confirm the sticks are in the slots your motherboard manual specifies for two sticks - usually A2 and B2, not the first two slots
Boot and check Task Manager, Performance, Memory shows the full expected size
2
Turn XMP Off and Retest - New Kits Are Often Just Unstable
A new kit's advertised speed is an overclock your board and CPU may not hold, especially with four sticks or mixed kits.
Enter BIOS and disable XMP / EXPO so RAM runs at base speed
Use the PC for several days doing whatever triggered the crashes
Stable at base speed means the kit is fine but the profile is not - options: run it slower, raise it manually in small steps, update the motherboard BIOS, or exchange the kit for one on the board's QVL list
Do not accept 'it passed one memory test' while crashes continue at XMP - stability in your real use is the test that counts
3
Isolate - One Stick, One Slot at a Time
If crashes continue at base speed, find the guilty piece by elimination.
Run with only the new stick in the primary slot for a day or two, then only the old setup
Crashes that follow the new stick wherever it goes mean a faulty stick - return it with confidence
Crashes that happen only in one slot, with any stick, point at the slot or board
Mixed old-plus-new kits that crash only together are a compatibility problem - matched kits exist precisely because of this
Run MemTest86 (4+ passes) on the suspect configuration to document the failure
4
New SSD Instead - Check the Clone, the Firmware, the Cable
SSD-triggered blue screens have their own list.
Cloned system: if crashes began after cloning Windows onto the new SSD, the clone may have carried corruption - test with a clean Windows install on the new drive before blaming it
Firmware: check the SSD maker's tool (Samsung Magician, Crucial Storage Executive, WD Dashboard) for a firmware update - early firmware bugs are a known blue screen source
Connection: for SATA drives, swap the cable and port; for NVMe, reseat the drive and confirm the heatsink or thermal pad is not bending it
Health: the maker's tool also shows drive health - a brand-new drive reporting warnings goes straight back to the seller
Do not reinstall Windows as your first move after a hardware upgrade crash. If the fault is seating, XMP, or a bad stick, the reinstall inherits it - remove the new variable first and let the evidence speak.
Watch the Complete Video Guide
The full blue screen identification method - dump files, stop codes and the fix - shown live, step-by-step.
The shop says the new RAM tested fine. Can it still be my problem?
Yes. A stick can pass a quick bench test yet be unstable in your board at XMP speed, or incompatible when mixed with your old kit. Your evidence - crashes that follow that stick or that profile in your machine - is what matters for a return or exchange.
Do I need to reinstall Windows after adding RAM?
No. RAM needs no drivers and no reinstall - Windows uses whatever is installed at boot. If adding RAM seems to demand a reinstall, something else was already wrong. SSDs used as a new boot drive are the ones that involve cloning or installing.
Both sticks pass MemTest86 alone but crash together. Why?
Two sticks place more load on the memory controller than one, and mixed timings add strain. This is the classic matched-kit argument: buy RAM as a tested kit, run it at the speed the kit and board share on the QVL, or accept a lower speed for stability.
This guide is based on the Technical Anshu blue screen video - stuck on any step, ask in the video comments and you will get an answer.