Change Auto to Profile 1 (on XMP) to get the proper memory voltages and specification. Basically this Intel CPU can't detect your memory configuration, so this was implement to go around the problem.
Well I am getting out of ideas... I don't know if you can return everything... and buy something else. If not.. than maybe you can see (if you are lucky), if you can exchange your motherboard with Gigabyte for a better one and pay the difference of something. But then again, there is no guaranty that it will now work. :S Can you ask on gigabyte motherboard forum for people with similar setups, and see what they have?
Not really. A phone activation will be needed though. And just explain that your old motherboard had to be change with a different one based on the manufacture recommendation, due to an issue with the original one. I am sure Microsoft will give you the override code. Many got no problem. Your issue is legit.
I'll try the eraser trick mentioned in that thread but yeah, my RAM, mobo and CPU have been RMA'd twice
have you tried using slots 2+4 instead? all 4 slots at once? some boards don't care what slots are populated as long as at least one is. also i noticed that they have bios f7 with "enhanced memory compatibility" it may be worth a go to downgrade. sometimes not all bios improvements get carried on to future versions. for example on my evga p55 board i can no longer use xmp profile after update bios, which i need to make my memory work properly.
Only works if slot one is populated. Will try that, I updated from F8 so I'll give F7 and possibly F4 a go
Are you using the stock cooler or an after-market one? If after-market, Have you tried loosening off your CPU cooler mounting hardware slightly? Having the heatsink screws too tight into the CPU backplate can result in too much pressure around the socket itself. This is known to cause issues with RAM where one or more DIMM's cannot be recognised by the system. Remember, the Memory Controller is now on the CPU itself and thus, too much pressure around the CPU backplate and socket area can cause issues such as this to arise. I've seen it happen with a few 1366 configurations.