Memory and CPU-Z

Soldato
Joined
25 Jun 2006
Posts
4,384
EDIT: SOLVED!!!!! After an EXTREMELY nail biting hour or so, I stripped the unit down to check the CPU socket as many sites were saying bent pins. It did have bent pins, not sure if I did that when I installed but have a lot of experience building pcs and pretty sure I didn't knock it etc. Either way, I pushed the pins back in place (albeit a little bent now though) and it now boots with the RAM in the correct channels/slots. So hopefully (fingers crossed) all is well. PHHHHHHEEEEEWWWWWWWWWW



Hey all,

So I had a problem where my unit would not post if I had all 4 of my 4x4GB DDR4 kit in a x99-SLI motherboard but would boot with 3x4gb in fine.

I put the ram in slots 1,3,5,7 like the manual described and it would not boot.

On reading through some solutions on google, I found a guy who stated he populated slots 1-4 and it works fine. Someone questioned him stating whether it was now not running quad channel to which he replied with a CPU-Z screenie showing quad in the channel box under memory.

I have copied this and I can now boot with all 4 sticks in at 16gb so it seem to have worked! What I would like to know is, is CPU-Z right and it if it says Quad then it is 100% running in quad channel mode???? Is there a way for me to check other than this?? If not then I have a faulty mobo and it needs to go back :(

thanks in advance as usual :D


EDIT:

I think I have just realized the problem after posting this. And I now feel thick.

The slots are labeled:

Left side of CPU
DDR4_1_1A
DDR4_2_2A
DDR4_3_1B
DDR4_4_2B

CPU

Right side of CPU
DDR4_8_2D
DDR4_7_1D
DDR4_6_2C
DDR4_5_1C


So firstly I had 1A, 1B, 1C, 1D populated which is the first slot in 4 channels right? It wouldn't post, but if I took one from 1C or 1D, it would post as triple channel 12gb. This is 1 on each channel right?

Secondly, if I populated 1A,1B,2A,2B which is only 2 channels?? This does post with full 16gb and as above shows Quad channel in CPU-Z??

I am confuuused!
 
Last edited:
I fixed it, was a physical fault with the pins on the cpu socket. After a very tense hour or so, I got the pins back into place (albeit bent a little) and all seems to be working fine.

Updated OP.
 
Back
Top Bottom