790i ULTRA
Q6600 G0
OCZ 2000 OCZ3N2000SR1G
GTX250
OCZ750 POWER SUPPLY
Win XP Pro 32
no NTUNE or any other OC software ever
BIOS Version: P08
**System **
CPU Freq, MHz: 2.70GHZ
FSB Reference Clock, MHz: 1350
CPU Multiplier: [8X]
PCle x16-1 & 16-2, MHz: AUTO [100]
PCle x16-3, MHz: AUTO [100]
SPPc->MCP Ref Clock, MHz: AUTO [200]
nForce SPP --> nForce MCP: [5X]
nForce SPP c-- nForce MCP: [5X]
**Spread Spectrum**
CPU Spread Spectrum: [Disabled]
HT Spread Spectrum: [Disabled]
PCle Spread Spectrurn(SPP): [Disabled]
PCle Spread Spectrurn(MCP): [Disabled]
SATA Spread Spectrum: [Disabled]
**FSB & Memorv Config**
EPP 2.0 MEMORY [DISABLED] (?????????? Mem claims it is EPP 2.0)
FSB - Memory Clock Mode: [LINKED]
FSB - Memory Ratio: [SYNC]
FSB (QDR), MHz: [1350]
Actual FSB (QDR), MHz:1350
x MEM (DDR), MHz: 1350 * (HAS BEEN AS HIGH AS 1700 FOR FSB STABILITY TESTING)
Actual MEM (DDR), MHz: 1350
P1: [AUTO]
P2: [AUTO]
**Memory Timing Setting**
Memory Timing Setting: [EXPERT]
tCL (CAS Latency): 9
tRCD: 9
tRP: 9
tRAS: 28
Command Per Clock: [2T]
** Advanced Memory Settings **
tRRD: [Auto] 11
tRC: [Auto] 35
tWR: [Auto] 12
tWTR: [Auto] 23
tFAW: [Auto] 22
tREF: [Auto] 7.7US
tRFC: [AUTO] 61
**System Voltages**
CPU Core: [1.33125] HAS BEEN AS HIGH AS 1.35 BUT WAS STABLE AT 1.2875 BEFORE CRASH
CPU FSB: [1.250] WAS STABLE AT 1.2 BEFORE CRASH
Memory: [1.800]
nForce SPP: 1.40
nForce MCP: 1.500
GTLVREF Lane 0: [Auto] 0
GTLVREF Lane 1: [Auto] 0
GTLVREF Lane 2: [Auto] 0
GTLVREF Lane 3: [Auto] 0
**CPU Configuration**
Limit CPUlD Maxval: Disabled
Intel Speedstep: Disabled
xPPM Mode: [Native]
CPU Thermal Control: [Disabled]
C1E Enhanced Halt State: [Disabled]
Execute Disable Bit: [DISABLED]
Virtualization Technology: [Disabled]
CPU Core 0: [Enabled]
CPU Core 1: [Enabled]
CPU Core 2: [Enabled]
CPU Core 3: [Enabled]
These settings are also 20+ LinX stable but have frozen once or twice in the past 2 days
When we first built this computer, it was overclocked somewhat and was fine. A few weeks later it started to experience the dreaded video corruption bug and we struggled to solve that. We updated the BIOS more than once and changed several settings. Part of the solution was to return to near stock clocks. All has been well for over a year but I decided to take another shot at clocking this thing.
If you see anything odd, I will gladly change it and try...
post edited by chememan - Monday, December 21, 2009 11:27 PM