Maximus VIII Hero won't post with 2 dimms

CRZ

Commendable
Oct 9, 2016
7
0
1,520
Hi everyone, I've been lurking these forums for a solution but haven't been able to solve the problem. Before anyone says it, I would really like to solve this without RMA anything.

Build:

- Intel core i5 6600k Skylake
- ASUS Maximus VIII Hero
- GSkill Trident Z 2x8 Gb 3000Mhz Dual Channel Kit
- OCZ Fatality 750W
- MSI GTX 560Ti

Everything is new except for the PSU and VGA.

I put everything together per manual instructions and the system posted once with 2 sticks but it frozed in Windows. Since then, I haven't been able to post with both sticks but only with one.
I've tried:

- Reseating the sticks in all combinations.
- Reducing CPU pressure a little bit
- Clearing CMOS
- MemOk button
- Updated to latest BIOS
- Pins are not bent or broken.

System only post with one stick, no matter which one. I've seen Q-codes 53 and 55 with 2 sitcks. When I put them in A2 and B2 like the manual says, I see Q-code 41 (which is not in the list) and CPU-led lit solid red. Any other combination results in Q-code 55.
Kit is on the motherboard's QVL list.

Thanks everyone in advanced.
 
Solution
It was a bad module after all. I RMA both modules and got a working pair, time to close this thread.
Thanks everyone for your responses.

CRZ

Commendable
Oct 9, 2016
7
0
1,520
1/2 is a no go.
I've reseated the CPU again, no bad pins in CPU or socket. Cooler not to tight either.

Now I get Q-41 and CPU-led with every 2 stick combination.
On the other hand I've tried stick A in every slot again and I get Q-55 while with stick B everything's fine.
I know, it seems like a bad stick but it makes no sense since it worked just fine previously.

Is there any other way to test stick A?
 

CRZ

Commendable
Oct 9, 2016
7
0
1,520
Cleaning the contacts dind't work. I stil get Q-41 and CPU led with 2 sticks.

Do you know what that code means? It's in the manual and I've seen other users experiencing it as well but I can't find what it means
 


Can you post a picture of the CPU socket?
 

CRZ

Commendable
Oct 9, 2016
7
0
1,520
It was a bad module after all. I RMA both modules and got a working pair, time to close this thread.
Thanks everyone for your responses.
 
Solution