RAM Slot Problems on Asus P8Z68-V Pro

[kingpotnoodle]

OK, so I decided to build myself a new beast, ordered all the stuff, built it up... power on - nothing. Red RAM problem light stays on... RAGE!!!

CPU = i7 2600K (Thermalright Venomous X)
RAM = Corsair Vengeance DDR3 1600 CL8 (it's on the QVL)
Case = Silverstone Fortress FT02B

After much investigation I discovered neither RAM slot A1 or A2 worked, if I put the RAM in slots B1 and B2 the board posted with 8GB recognised. I tried all combinations, borrowing RAM from my HTPC and re-seating it many times over - still no change, even when I pressed Mem-OK. I made sure the defaults were loaded in the BIOS too, and XMP was off, so it was only trying to use the RAM at 1333MHz anyway.

I RMA-ed the board to Scan, but they say it works fine on their test bench.

So now I'm sending them the CPU and RAM too, so they can test as a group... is it plausible that half the memory controller on the CPU is broken or something? Anyone had that before? Or am I looking at a motherboard that works out of the case laying flat on a test bench but will break again when mounted vertically in a case?

Anyone had a similar problem?

[Sputnik]

The recommended slots to use for dual channel (2sticks) is A2 & B2 on that board.

What happens if you just put a single stick in slot A2 only? As that is the recommended slot for a single stick. If nothing try the other stick in A2.

[scaryjim]

It's not impossible that you had some issue with the contact pads on the CPU (or pins on the socket), which could mess up one of the memory channels - did you try re-seating the CPU whilst you were trying to troubleshoot the problem? One problem with so much functionality being farmed off onto one piece of silicon is that it means pretty much everything that goes wrong could potentially be down to the CPU...

I suppose it's possible you could have been really unlucky and got a CPU that slipped through QA with a faulty memory controller - not sure what the chances of that would be though. Probably best to wait and see what Scan get back to you with...

[kingpotnoodle]

The recommended slots to use for dual channel (2sticks) is A2 & B2 on that board.

What happens if you just put a single stick in slot A2 only? As that is the recommended slot for a single stick. If nothing try the other stick in A2.

Yep I know, I started with A2+B2, no joy, reseated it several times. Tried basic 1333MHz RAM from my HTPC in A1 then A2 - no joy... finally when I tried B1 alone I found it booted, which then led me to try the original RAM in B1+B2 - which worked without issue, obviously no good in the long run without the dual channel though.

Instinctively I blamed the motherboard and RMA-ed it, but like I say Scan think it's fine. I guess I'll have to see what happens when they have everything, I didn't think to reseat the CPU during the testing (idiot=me) - I'd totally forgotten the memory controller is on it until I was racking my brains once Scan said the motherboard seemed fine to them.

I'm just afraid on their test bench it will work fine, but then they'll return the stuff to me and it'll not work once mounted up the case because of a loose connection or flakey board component thats being broken by the positioning, weight of the heatsink or something.

[Sputnik]

Can't you just bench test it yourself? and see what happens? It'll save you screwing it all in the case and messing around.

Like Scaryjim said, It could be a bad connection on the CPU socket I guess.

[scaryjim]

Another possibility is that something in your case is shorting a connection on the back of the mobo - a misplaced motherboard riser or something. If Scan do reckon everything's OK, check for that.

[1stRaven]

http://forums.hexus.net/hexus-hardwa...am-issues.html

Might be the same issues as mine.

[Sputnik]

http://forums.hexus.net/hexus-hardwa...am-issues.html

Might be the same issues as mine.

I knew I'd seen this problem here before, Just could not remember who it was.

[kingpotnoodle]

Can't you just bench test it yourself? and see what happens? It'll save you screwing it all in the case and messing around.

Like Scaryjim said, It could be a bad connection on the CPU socket I guess.

I will this time, I should have last time but I had limited time before I was going to be away a few days.

I'm concerned that it will work for me too on the bench, but not in the case - which is the important one! Perhaps the weight of the cooler is breaking a loose connection, or like has been suggested a short is the problem (not a riser, I double check those, I count them in then count how many I screw through!)

I did try using slots A1 and B1, that also fails but is also not going to work with that RAM and Cooler, I had to remove the fan to use A1.

[GoNz0]

bolt through heatsinks can warp enough to lose cpu contact on ram slots.

[kingpotnoodle]

bolt through heatsinks can warp enough to lose cpu contact on ram slots.

Yeah maybe I should not crank the pressure on the Venomous so much... not that it was rock solid, it swivelled about something cronic, not what I really expected.

No updates from Scan today, they got the CPU and RAM this morning according to Royal Mail.

[GoNz0]

no matter how tight the heatsink it will wiggle about due to the paste acting as a lubricant. its a well known issue on my board if you wang it down to tight.

[kingpotnoodle]

no matter how tight the heatsink it will wiggle about due to the paste acting as a lubricant. its a well known issue on my board if you wang it down to tight.

Yeah I know, I mean I was expecting more from the mounting mechanism, poor design.

Scan got back to me - no problems. I guess I should have thought to reseat the CPU myself as it looks as it that was what was causing my issue, expensive mistake - dumbass me.

I've ordered a Corsair H60 as well, really not happy to use the Venomous X, the mechanism is crap and it may have been causing the board to warp and affect the contact of the CPU.

[GoNz0]

I could have told you scan wouldn't have found fault. shame you now have to fork out to get it back.

[kingpotnoodle]

I could have told you scan wouldn't have found fault. shame you now have to fork out to get it back.

Meh, not the money I'm so worried about, it's the 10 day delay! The price of jumping to conclusions eh... I realised myself about the memory controller being on the CPU, but only after I sent the board back and it was reported OK, should have thought about it more carefully and asked around first.