Hi there everybody - this is my first post here.
I have had a BIG problem arise with my 3 x 2Gb Corsair XMS3 RAM in my GA-X58a-UD3R Mobo with i7 930 CPU. I built the system in october last year and everything has been running fine and stable...until today!
I had noticed that in the POST screen the RAM was not reporting the 1600Mhz as spec'd and came accross a forum discussing X.M.P. Long story short - I enabled XMP in the BIOS and the settings all looked good to me v 1.65, 1600Mhz, 9-9-9-24 etc. (exactly what it says on my RAM modules.)
When I rebooted, Windows loaded correctly but I immediately noticed that only 2Gb of RAM was registering. Panic!
The motherboard is now only recognising the module in Dimm slot DDR3_3. Confusingly the Memory Tab in CPUZ is reading that the Memory size is 4096Mb and the SPD Tab shows Memory modules present in Slot #1 & 2 but not in 3,4,5 or 6.
I have tried resetting everything using the Clear CMOS button. Loaded optimised config in BIOS and tried running Memtest86 which reported no problems with the 2Gb that it could see. ( I have now tried this with all three sticks of RAM - they're all OK)
I have physically removed the memory sticks and checked each on their own. All of the sticks are running fine when they are placed in Dimm slot 3 (White one in the middle) and the PC will boot properly when all 3 are in place (in white slots) It just doesn't recognise more than 2Gb. POST shows only 2Gb also - albeit at 1600Mhz now.
No other slot on the Motherboard will recognise the sticks at all and the machine will not boot if only a single stick is in any other slot than DDR3_3, it doesn't BEEP (the speaker is workingm it beeps on sucessful post) and it doesn't even show a POST screen. Just a black Screen, Fans spinning, Drives Spinning, a few LEDS on the board light up Blue & Green but nothing else will happen.
I would really appreciate any suggestions or links to other similar problems. I've read a lot of forum threads now and haven't managed to find anything close to this problem.
I'm starting to think this is an RMA situation? I really hope not!
Kind Regards,
Tim