OK - individual testing should have caught any possible hardware problems on any single stick; don't take offense, but I believe the set of parameters that I referred you to should take care of the rest, as it has worked on a few fairly identical systems already, unless you actually have a malfuntion of some sort on the MOBO itself, or have a USB devices triggering one of the panoply of bizarre troubles they can cause - see this:
http://www.tomshardware.com/forum/261902-30-gigabyte-tale
I'm going to repost the parameter set in one chunk, with both stock CPU clocking, and the 20% bump other people have working, just to be sure some critical setting's not been missed, beause the original posting is kind of diffused across a few entries:
On the "Advanced BIOS Features" page:
"CPU Enhanced Halt (C1E)" to "Disabled"
"C2/C2E State Support" to "Disabled"
"C4/C4E State Support" to "Disabled"
"CPU Thermal Monitor 2 (TM2)" to "Enabled"
"CPU EIST Function" to "Disabled"
"Virtualization Technology" to "Enabled" if using MS', Sun's, or VM_Ware's virtualization s'ware, else "Disabled"
"Full Screen LOGO Show" to "Disabled"
"Dual BIOS Recovery Source" manual doesn't show the alternative, and my BIOS don't have this feature - my guess is it's "Backup" - anyway, we want whatever else it gives other than "HPA", 'cause we haven't created an HPA yet... (whatever an HPA is?) [let me know if you have this; my manuals show it, but no one so far has actually found it in their BIOS]
On the "Integrated Peripherals" page:
Your manual shows "Legacy USB storage detect", but later BIOS say "USB Storage Function" - either way, set to "Disabled"
On the "Power Management Setup" page:
"ACPI Suspend Type" to "S1(POS)" (for now...)
"HPET Support" to "Enabled"
"HPET Mode" to whichever OS type you're running - "32-bit" if an x86 version, "64-bit" if an x64 version...
On the "MB Intelligent Tweaker(M.I.T.)" page:
"Robust Graphics Booster" to "Auto"
"CPU Clock Ratio" to "8"
"Fine CPU Clock Ratio" to ".5"
"CPU Frequency" - this one can't be set, it's calculated, and will change when we set the next few items...
******** Clock Chip Control ********
>>>>> Standard Clock Control
"CPU Host Clock Control" to "Enabled"
"CPU Host Frequency (Mhz)" to "334" for stock (2.83GHz) CPU timing, "401" for 20% 'bump' to 3.4GHz
"PCI Express Frequency (Mhz)" to "100" (not auto...)
"C.I.A.2" to "Disabled"
******** DRAM Performance Control ********
"Performance Enhance" to "Standard"
"Extreme Memory Profile (X.M.P.)" to "Disabled"
"(G)MCH Frequency Latch" to "333" for stock CPU timing, "400" for 20% 'bump' to 3.4GHz
"System Memory Multiplier (SPD)" to "3.2" (may have a 'B' or '#' after it) for stock, "2.66" (may have a 'D' after it) for 'bumped'
I think your separate "(G)MCH Frequency Latch" which we mostly refer to as a 'strap', and "Memory Multiplier" may relieve you of having to keep track of these by a cryptic letter or symbol in the multiplier table; with yours, you just tell it 'this one'! The strap is the reason we used a 334 clock instead of a nice even 333: the 'straps' are sets of northbridge timings - much like memory latencies, the faster you go, the 'looser' the timings have to be... There are four straps, corresponding to the Intel FSB ratings: 200 (800FSB), 266 (1066FSB), 333 (1333FSB), and 400 (1600FSB - Intel actually
does make a 1600 FSB CPU - the QX9775 - but, I think, it's over $1500 a pop!); each strap has it's own set of available memory multipliers (ratios). The 3.2 we used (which is actually a 8:5 bus to bus ratio) is available only on the 333 strap. Anyway, the strap latencies, for some northbridges, don't 'kick in' until one over the selected strap; so, in other words, setting the clock to 334 guarantees that we're getting the 333 latencies/timings...
"Memory Frequency (Mhz)" - again, can't be set, it's calculated...
"DRAM Timing Selectable (SPD)" to "Manual"
>>>>> Standard Timing Control
"CAS Latency Time" to "5"
"tRCD" to "5"
"tRP" to "5"
"tRAS" to "15"
>>>>> Advanced Timing Control (these should have been set by the "Load Optimized Defaults", but in case - check 'em
"tRRD" to "4"
"tWTR" to "4"
"tWR" to "13"
"tRFC" to "68" (may be able to lower later, I run mine at 1080 with 52 here...)
"tRTP" to "4"
"Command Rate (CMD)" to "2"
>>>>> Channel A/B Timings - the only thing you need to check here is:
"Static tRead Value" should be at at least 7
"Load-Line Calibration" to "Disabled" (this works differently on different boards - on mine, it's worse "enabled" than "disabled" - the function is supposed to cure a phenomenon called Vdroop - the CPU voltage regulation circuit causes the CPU core voltage to sag, or 'droop' under high loadings; hopefullt, we're going to be at a low enough voltage to just ignore this...)
"CPU Vcore" to "Auto" for standard timing, "1.3500V" for 'bumped'
>>> MCH/ICH
"MCH Core" to "1.200V" to run four sticks
>>> DRAM
"DRAM Voltage" to "2.1V" (might be expressed as "+.30V" as JEDEC spec is 1.8V, so +.3 is 2.1V)
and an <F10> to save and exit - may reboot twice, let 'er rip!
Good luck!
Bill
Facebook
Twitter
Instagram