That ends your theory
So what theory is that. Show me where in any of my post that I said you were OC your memory.
This is my theory ask: thessie what is he doing that you guys are not. He has run 4 sticks of 1333mhz 16gbs & 4 sticks of 1600mhz 32gbs
thessie
I have 4x4G 1333Mhz Crucial sticks in it, and I haven't seen any BSODs yet.
However, I have 4x8G 1600Mhz Crucial sticks on order - I wonder if I'll start seeing this when I try that. Ugh.
Just an update - I received my Crucial 4x8g sticks last night and installed them (32g total).
I ran a couple of video benchmarking programs for a few hours to see if I could trigger SOMETHING (since I figured video benchmarking would get memory and processor used quite a bit), and everything worked fine (tho' I noticed the Intel 4600 GPU isn't the fastest in the world, but I don't game so there you go).
No BSODs as yet.
What bios is he running? How does he have his bios setup? What other hardware is he running that is different than yours?
If it is all so specific to run these boards why does Gigabyte not publish this one very specific combination of hardware and config specs then? Instead we are to assume that even the published recommended RAM list they DO publish not worth consulting, according to you, and then we need to consult that one guy on the internet that managed to hit the jackpot of that one magical combination of hardware/config settings that Gigabyte themselves seem unable to enlighten us with? and unless we all follow that one particular recipe we should not expect our systems to operate as advertised?
That's just ridiculous.
If the boards only run 4 DIMMS with Crucial RAM and a whole bunch of other very specific settings like this one guy has, then Gigabyte needs to be up front about that and say so, don't publish a Corsair RAM part number on a list as compatible if it isn't.
Gigabyte need to own this and tell us, the paying customers EXACTLY what we need to use/do to run and fully utilise the product we paid for. The product does not operate as described, this has been reported by a LOT of people and it appears that Gigabyte do not know what specifics to recommend or how to fix it.