PC crashes after replacing memory sticks

99nirc99

Distinguished
Aug 26, 2014
22
0
18,510
Please check out my first question here: http://www.tomshardware.com/answers/id-2403269/major-memory-problems.html

So I got myself a similar 4GB stick (This one), put them both in both slots with the same color, and turnd the PC on. At first, it seemed to be working fine, but then my pc just crushed (not a BSOD or anything, just shut down). I also tried using memtest86, first time it crashed 2 seconds in, then it took aroudn 10 minutes, and then it made a complete pass with 0 errors before I stopped it myself. I tried putting the sticks on the other 2 slots, but for some reason the PC didn't recognize them (it made a long bipping sound and didn't show up anyhting, not even the Post screen). What should I do? It's clearly not a software problem, and the RAM sticks show up good when tested seperately with memtest86.

My specs are:
Intel Core i5 750 2.67GHz
Geforce GTX 570
8GB Ram (2 sticks of 4GB This one)
My PSU is 750W and is new
 

techelpr

Reputable
Dec 3, 2014
20
0
4,540
Those RAM sticks are incompatible with each other. You'll ether have to just use 1 of them or buy another stick to match. It could also be a motherboard problem but that is unlikely.
Hope this helps.
 

99nirc99

Distinguished
Aug 26, 2014
22
0
18,510


But they are the exact same brand, module and speed! Could it be that the exact same two sticks are incompatible with eachother?
 

99nirc99

Distinguished
Aug 26, 2014
22
0
18,510


I've just tested, the pc also shuts down with just one stick connected at DIMM3. Could it really be my motherboard? just yesterday my pc didn't crash with 1 faulty ram stick (check out the previous thread I created for the info). What's going on?
 

99nirc99

Distinguished
Aug 26, 2014
22
0
18,510


The thing is, I can't even get the PC to boot on the 2 blueish slots. I have 4 slots on my Gigabyte P55-UD3L mb. from left to right: blue slot-white slot-blue slot-white slot. When I put a ram stick on either of the blue slots it just makes a really long looping beep sound, not even going to POST.
 

99nirc99

Distinguished
Aug 26, 2014
22
0
18,510

http://www.newegg.com/Product/Product.aspx?Item=N82E16820231313
Those are the RAM sticks I own (for some reason G.Skill page of these won't work). How do you raise the DRAM voltage by 0.05? DRAM voltage on my bios is set to auto, and after 1.5V there's only 1.56V. Should I try that even though the label on the sticks shows 1.5V next to the model?
also, before entering the Volatge settings on the bios, there's a status screen showing that the current DRAM voltage is actually 1.584V . Also, I notice there's DDR voltage could it be that I should change that aswell?
 

99nirc99

Distinguished
Aug 26, 2014
22
0
18,510

So I tried changing DRAM voltage to 1.56V and it didn't help. I also tried moving the sticks around to any possible slot (no combination solved the problem), and for some reason when the sticks were on slots 0 and 2, the PC made a long looping beep sound and didn't even boot.
I took some pictures of my bios settings because I didn't really know what to search for (I don't have alot of knowledge about these stuff). Here they are, if you could kindly help me search for something that might cause this trouble: https://imgur.com/a/NGiuA
Thank you for the help!
 

99nirc99

Distinguished
Aug 26, 2014
22
0
18,510

I changed the QPI/Vtt voltage to 1.15v, but pc still crashes...
I'm starting to get hopeless :( PC worked a bit weird (Didn't decompress large archives and sometimes BSOD) just yesterday before I took the 2x2GB which one of them was faulty, but atleast it didn't crash everytime I did something a little bit demanding.
 

99nirc99

Distinguished
Aug 26, 2014
22
0
18,510


Sorry for the late response. I took the PC to my dad's friend who is a technician. He tried putting different working RAM sticks but the problem still happened. Since a similar problem happened to me (PC Crash) when I changed my GPU, he tried switching the GPU, but the problem still happened. So all there's left to blame is my motherboard. Thank you and techlpr for the help :)