(noob) Can only post with 1 ram stick in after motherboard replacement

jmflu

Distinguished
Jun 5, 2012
128
0
18,690
New (used) motherboard:
i5-3570k
DZ77SL50K
GPU: Gigabyte 1070

I had been using these RAM sticks for the past few years with no issue.
Recently, I had a problem recently with my PC being unable to post whatsoever after cleaning it out with canned air. So I bought a new motherboard upon rebuilding I am getting some RAM errors.

So my RAM modules

Black Blue Black Blue

Let's call them stick A and Stick B

So here is what happens in each situation:

Stick A in the first black slot: Memory errors 3 beeps.
Stick B in the first black slot: Memory error 3 beeps

Stick A in first BLUE slot: Memory Error 3 Beeps
Stick B in first BLUE slot: Memory error 3 beeps

Stick A in the 2nd BLACK slot: POSTS
Stick B in the 2nd BLACK slot: Memory Error 3 Beeps

Stick A in the 2nd BLUE slot: POSTS
Stick B in the 2nd BLUE slot: Memory Error 3 Beeps

Both Sticks in BLACK: Memory Error Beep
Both Sticks in BLACK: Memory Error Beep
 

Tumeden

Honorable
Oct 15, 2016
449
0
11,160
Bent CPU pins can cause this, but it's more likely a defective motherboard which would suck for sure. If you have some thermal paste around i suggest checking the pins on your CPU and to make sure they arent bent or broken
 

jmflu

Distinguished
Jun 5, 2012
128
0
18,690


CPU pins look completely fine.

I am going to try a friends RAM tomorrow.

If that doesn't do anything then I am going to assume it is the motherboard and I think I could get a replacement from seller because I just bought it it a week ago.
 

jmflu

Distinguished
Jun 5, 2012
128
0
18,690
So pretty much one of my Ram sticks doesn't work in Any of the 4 ram slots.

My other Ram stick works in slots 3 and 4 but not 1 and 2.

If my first stick was just bad, then my other stick should still work in slots 1 and 2 right? Unless it is both a bad stick and bad slots? And it seems there is possibility of it being CPU even though I don't see any bent pins, but I have no other computers to test CPU with...

ugh so frustrating :(