MikalCarbine
02-03-2007, 01:27 PM
After decapping my 3800+ X2 I was finally able to hit 2.9GHz stable at 1.475x104% (1.534)vcore and was very happy :banana: but had to bump it up to 1.54v for 100% stability. I then started working on getting my memory stable on the 183 divider, making my memory run at ~264MHz, I had everything prime stable and started to tighten up my memory timings one by one each night, priming each time for about 6-12 hours.
After tightening the alpha timings to their extents I began to overclock my video card and test it with overnight 3dmark. I ran 3Dmark06 and 05 for 2-3 nights without a hitch, but when I tried 3dmark03 I would awake to a frozen computer. Knowing 3dmark03 is sensitive to fsb/cpu I set my card back to stock and to my dismay 3dmark03 froze again. I set my timings back to the looser alpha ones to see if that was the problem but it wasn't. I then ran the memory on a lower divider to eliminate that as the problem, and 3dm03 will freeze on the cpu tests.
I bumped the vcore up to 1.55v to see if that helped, but it doesn't. I've also fiddled with different drive/data strengths with no avail. Heat isn't an issue because I'm loading under 40C on each core. The weird thing is that I've played endless amounts of hours of intensive games before testing with 3dmark03 without a problem. I've played hours of CS:S, HL2, BF2, SC (haha), and Oblivion.
Does anyone have any ideas/tips about this?
My settings are:
FSB Bus Frequency............................. - 297
LDT/FSB Frequency Ratio....................... - x3
CPU/FSB Frequency Ratio....................... - 10
PCI eXpress Frequency......................... - 101Mhz
CPU VID StartUp Value......................... - Auto
CPU VID Control............................... - 1.55
CPU VID Special Control....................... - Auto
LDT Voltage Control........................... - 1.20v
Chip Set Voltage Control...................... - 1.60
DRAM Voltage Control.......................... - 2.6v (+.3 enabled)
DRAM Configuration Settings:
DRAM Frequency Set............................ - 180:9:10 (and divider below this one)
Command Per Clock (CPC)....................... - Enable
CAS Latency Control (Tcl)..................... - 3
RAS# to CAS# delay (Trcd)..................... - 3
Min RAS# active time (Tras)................... - 8
Row precharge time (Trp)...................... - 3
Row Cycle time (Trc).......................... - 7 Bus Clocks
Row refresh cyc time (Trfc)................... - 14 Bus Clocks
Row to Row delay (Trrd)....................... - 3 Bus Clocks
Write recovery time (Twr)..................... - 03 Bus Clocks
Write to Read delay (Twtr).................... - 02 Bus Clocks
Read to Write delay (Trwt).................... - 03 Bus Clocks
Refresh Period (Tref)......................... - 3120 Cycles
DRAM Bank Interleave.......................... - Enabled
DQS Skew Control.............................. - Auto
DQS Skew Value................................ - 0
DRAM Drive Strength........................... - 7 (also tried 8, a known good value for my memory)
DRAM Data Drive Strength...................... - 1(also tried 2 and 3, also decent values)
Max Async Latency............................. - 8
DRAM Response Time............................ - normal
Read Preamble Time............................ - 6
IdleCycle Limit............................... - 16 Cycles
Dynamic Counter............................... - Enable
R/W Queue Bypass.............................. - 16 x
Bypass Max.................................... - 07 x
32 Byte Granularity........................... - Disable(4 Bursts)
Anyone think this could also be a memory problem despite lowering the multi?
Thanks :toast:
After tightening the alpha timings to their extents I began to overclock my video card and test it with overnight 3dmark. I ran 3Dmark06 and 05 for 2-3 nights without a hitch, but when I tried 3dmark03 I would awake to a frozen computer. Knowing 3dmark03 is sensitive to fsb/cpu I set my card back to stock and to my dismay 3dmark03 froze again. I set my timings back to the looser alpha ones to see if that was the problem but it wasn't. I then ran the memory on a lower divider to eliminate that as the problem, and 3dm03 will freeze on the cpu tests.
I bumped the vcore up to 1.55v to see if that helped, but it doesn't. I've also fiddled with different drive/data strengths with no avail. Heat isn't an issue because I'm loading under 40C on each core. The weird thing is that I've played endless amounts of hours of intensive games before testing with 3dmark03 without a problem. I've played hours of CS:S, HL2, BF2, SC (haha), and Oblivion.
Does anyone have any ideas/tips about this?
My settings are:
FSB Bus Frequency............................. - 297
LDT/FSB Frequency Ratio....................... - x3
CPU/FSB Frequency Ratio....................... - 10
PCI eXpress Frequency......................... - 101Mhz
CPU VID StartUp Value......................... - Auto
CPU VID Control............................... - 1.55
CPU VID Special Control....................... - Auto
LDT Voltage Control........................... - 1.20v
Chip Set Voltage Control...................... - 1.60
DRAM Voltage Control.......................... - 2.6v (+.3 enabled)
DRAM Configuration Settings:
DRAM Frequency Set............................ - 180:9:10 (and divider below this one)
Command Per Clock (CPC)....................... - Enable
CAS Latency Control (Tcl)..................... - 3
RAS# to CAS# delay (Trcd)..................... - 3
Min RAS# active time (Tras)................... - 8
Row precharge time (Trp)...................... - 3
Row Cycle time (Trc).......................... - 7 Bus Clocks
Row refresh cyc time (Trfc)................... - 14 Bus Clocks
Row to Row delay (Trrd)....................... - 3 Bus Clocks
Write recovery time (Twr)..................... - 03 Bus Clocks
Write to Read delay (Twtr).................... - 02 Bus Clocks
Read to Write delay (Trwt).................... - 03 Bus Clocks
Refresh Period (Tref)......................... - 3120 Cycles
DRAM Bank Interleave.......................... - Enabled
DQS Skew Control.............................. - Auto
DQS Skew Value................................ - 0
DRAM Drive Strength........................... - 7 (also tried 8, a known good value for my memory)
DRAM Data Drive Strength...................... - 1(also tried 2 and 3, also decent values)
Max Async Latency............................. - 8
DRAM Response Time............................ - normal
Read Preamble Time............................ - 6
IdleCycle Limit............................... - 16 Cycles
Dynamic Counter............................... - Enable
R/W Queue Bypass.............................. - 16 x
Bypass Max.................................... - 07 x
32 Byte Granularity........................... - Disable(4 Bursts)
Anyone think this could also be a memory problem despite lowering the multi?
Thanks :toast: