#Installed new RAM, now I'm underperforming and crashing
1 messages · Page 1 of 1 (latest)
Did you try to reseat the ram
Haven't cracked her open yet but you know that's gonna be my next step if disabling XMP doesn't do it
Yeah highly recommend trying that
And if just reseating doesnt help try different slots if there is any
Just reseated. Let's see how she does
Good luck
No dice
windows recovery mode?
Yep. Only thing I haven't tried is a system reset
Which I guess I can do but gosh that's a pita
Try windows memory diagnostic
Not sure if thats any better or worse than memtest but worth a shot
Resetting rn. If I still have problems I'm calling the dimms lemons and going back to 16gb
The memory diagnostic'll test if its faulty too
Can installing ram brick your OS normally? Because I got a techie buddy who says that sounds about right
Or is this windows shenanigans
You combined the new RAM with the old RAM? Are they the exact same model/speed/timings?
What about the timings? Those are not the only specs important to RAM compatibility
Also, there's a reason why lots of people here tell folks to avoid Vengeance ram
The boxes for both batches of ram are the exact same
Yeah I'm starting to understand that lol
But reset just finished we'll see if she boots now
She's posting and installing!
Okay so vengeance ram can just brick your copy of windows good to know
Idk if this is a corsair moment or a Microsoft moment
I hate to be pedantic but "the boxes are the same" means different things to different people.
There should be a series of four numbers (referred to as timings) that could look like 16-18-18-36 these should be the same on both boxes/sticks of RAM
If the timings are not the same, odds are you'll see more instability in the future
Yeah I don't pretend to be savvy in ram, but the timings are both the same
Installing new ram can do this sometimes. The BIOS needs to "re-train" the ram which can result in boot loops
I'll chalk it up to a fluke but if it gives me problems in the future I'll just get some ripjaws
Okay xmp 2 is enabled no issues. Thanks for the tips though! If anything else happens I'll just drop the vengeance and get some better ram
Yeah this happens with all kinds of ram. Sometimes when you install new sticks, you need to install them one at a time to let the motherboard train each one individually
your OS only sees the amount of RAM, it doesn't care about anything else, so it shouldn't do that
on 2016- AMD systems the CPU trains the memory automatically
I have a 5950X and have had the same thing happen. Installing ram one at a time resolved things.
I think they're misusing the term "brick" and equating it with "causing boot issues" which can definitely happen
"automatically" doesn't always mean "successfully"
Yeah let me reiterate the system is fine now, I think it was just too many system changes at once and windows pulled a windows
Nothing was bricked but when it first started giving me issues I panicked and said brick
People tend to take things very literally here
Well I used to field tech calls for AppleCare I know how important verbiage is