Problem with MOBO RAM SLOT???

[dreamhacking]

I have been running 4x4GB Kingston Fury HyperX with a Gigabyte Z87X mobo all the time and never experience any problem.

However, couple days ago. My system won't boot. Then I was doing some test with each ram slot. 

with ram in slot 1-3, boots perfectly. Never fail. 

with ram in slot 2-4, sometimes it boots, sometimes it doesn't.

I also tested each slot with 1 ram stick, and each time the system will boot.

I tried re-seating them, tried to clean the ram slot with canned air duster, but that doesn't help.

I cleared CMOS, but with 4x4GB installed, it still won't boot until i remove 2 ram.

 

Does this problem seems to relate to the mobo? 

Thanks.

[Windows7ge]

Since your motherboard is dual channel inserting RAM in both 2 & 4 which results in issues makes sense. Occupying specific slots causing issues sounds like a fault with the motherboard. If you switch out the sticks used in 2&4 for the sticks used in 1&3 if the same issue persists I think that's your motherboard.

[dreamhacking]

8 minutes ago, Windows7ge said:

Since your motherboard is dual channel inserting RAM in both 2 & 4 which results in issues makes sense. Occupying specific slots causing issues sounds like a fault with the motherboard. If you switch out the sticks used in 2&4 for the sticks used in 1&3 if the same issue persists I think that's your motherboard.

Yeah, when i am doing the test.

I used the working sticks in slot 1-3, and bring them to 2-4 to carry out the test. 

 

I am thinking to RMA the mobo, but i am afraid that when Gigabyte tests the mobo it will boot normally and they will not test it until it shows failure. That will be wasting my money right? If i don't get the mobo fixed or replaced.

because like i said, sometimes with ram in 2-4 it will also boot. but sometimes it doesn't.

[Windows7ge]

1 minute ago, dreamhacking said:

Yeah, when i am doing the test.

I used the working sticks in slot 1-3, and bring them to 2-4 to carry out the test. 

I see, it sounds like a motherboard issue, either that or CPU but I doubt that.