Good Sunday Afternoon Everyone.
Well, with the upcoming Halloween festivities, STRANGE things appear to be happening with the latest BIOS revisions that are flowing out of the Gigabyte workshops. As we all know, most first-line memory manufacturers embed SPD timing chips into their memory sticks. However, we also learned some time ago that there were actually two (2) separate SPD levels in those sticks, one for lower voltage (usually 1.8V) and one for higher voltage (usually 2.2 to 2.3V). Therefore, in order to avail oneself of the higher level memory settings, a bump of approximately +.40V to +.50V (depending on the manufacturer) was necessary to reach the higher level.
It now appears that the memory voltage bump may be unnecessary, indeed possibly dangerous, when utilizing these latest BIOS revisions. Although I have not totally confirmed it, it seems that when you
manually set the latency values for your memory sticks, i.e. 5-5-5-15, using these latest BIOS revisions, the CMOS is then set to the higher memory voltage,
AUTOMATICALLY.
I just encountered this situation with my GA-X38-DQ6 board, and the latest F5h BIOS revision. On that X38 board, I was having a helluva time trying to obtain stability, getting repeated BSODs, and lockups when the Q6600 was set at a modest 334 x 9 = 3.0GHz, and the memory
manually set at 5-5-5-15, but with the heretofore usual voltage bump of +.40V. Out of curiosity, I then set the memory voltage to Auto, and retained the manual memory settings. The damn thing booted up just fine, and has been stable for more than an hour. Using CPU-Z (ver. 1.41), it shows the memory running just fine at 534.6MHz, thus indicating that it is being feed 2.20V automatically by the CMOS.
Obviously, if what I am seeing with the X38 board BIOS revision is indicative of what may also be happening to the N680i boards using the F5f BIOS, then the memory sticks are getting "cooked" if you add the usual bump of +.40V, etc,
IF you are also setting the memory latency values
manually. We need to check this out further, so that it can be confirmed or not.
I don't have my N680i rig up and running right now so I can't try it myself, but maybe some of the Thread members can check it out and let us know if they find the same thing.
Best regards to everyone. TheBeagle

:beer: