E6600 + Asus 680i Striker Extreme

**eva2000** · 12-20-2006, 04:53 PM

After showing the Asus 680i Striker Extreme bios and setup photos (bypass photos to Striker board info/links/downloads), it's time to get down to some testing and results

System:

Intel Core 2 Duo E6600 QPGE B1 Step 5
Scythe Infinity heatsink with mounting mod + Thermaltake 120x25mm 81cfm fan
128MB FX5200 PCI / 256MB BFG 7800GTX / Gainward 8800GTS/SLI
Asus 680i Striker Extreme rev1.0 with initial official 302 bios
1x 160GB Seagate 7200.7 SATA NCQ on SATA2 port
Pioneer DVR-05 DVD Burner
600W OCZ EvoStream Modular Power supply

Memory to be used:

2x512MB OCZ PC5400 Platinum XTC 3-3-3-12
2x512MB Corsair XMS5400ULv1.5 3-3-2-8
2x1GB G.Skill F2-6400PHU2 2GBHZ Micron D9GMH 629 batch
2x1GB Teamgroup PC6400C3 3-3-3-8 Micron D9GMH
2x1GB OCZ PC8000 Titanium Alpha VX2 Micron D9GKX

Room temp: 23.3C to 30.8C average

@3600Mhz - 9x400FSB at 1.39v
As always start of with a known stable overclock on my E6600 which is 3600Mhz at between 1.371v and 1.42v on various motherboards. On Asus 680i Striker Extreme it seems 3600Mhz handles fine at 1.39v vcore under load so far. I used 2x512MB OCZ PC5400 Platinum XTC 3-3-3-12 memory for the tests.

Settings used:

AI Tuning: Manual
Nvidia GPU Ex: Disabled
LinkBoost: Disabled

FSB - Memory Clock Mode: Unlinked
x FSB - Memory Raio: N/A
FSB (QDR), Mhz: 1600 (means 400FSB)
Actual FSB (QDR), Mhz: 1600
MEM (DDR), Mhz: 800 (means 400mhz speeds)
Actual MEM (DDR), Mhz: 880.2

Vcore Voltage: 1.525 set (1.42v bios/1.41v windows idle/1.39v windows load)
Memory Voltage: 2.100v
1.2v HT Voltage: 1.3v
NB Core Voltage: 1.4v
SB Core Voltage: 1.55v
CPU VTT Voltage: 1.4v
DDRII Controller Ref Voltage: AUTO
DDRII Channel A Ref Voltage: AUTO
DDRII Channel B Ref Voltage: AUTO

tCL (CAS Latency): 4
tRCD: 4
tRP: 4
tRAS: 12
Command Per Clock (CMD): 2 clock (2T)

Advance Memory Settings
tRRD: AUTO
tRC: AUTO
tWR: AUTO
tWTR: AUTO
tREF: AUTO
Async Latency: AUTO

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
MCP PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled
LDT Spread Spectrum: Disabled

CPU Internal Thermal Control: Disabled
Limit CPUID MaxVal: Disabled
Enhanced C1 (C1E): Disabled
Execute Disable Bit: Disabled
Virtualization Technology: Disabled
Enhanced Intel Speedstep Tech: Disabled
LDT Frequency: 5x

PCIEX16_1 Frequency (Mhz): 100
PCIEX16_2 Frequency (Mhz): 100
PCIEX16_3 Frequency (Mhz): 100
SPP<->MCP Ref Clock, Mhz: 200

Prime95 v25.1 multi-threaded dual small FFTs priming for ~1hr 18mins before I stopped it. Interesting that even coretemp reported cpu temps fluctuated alot more jumping between 59C to 68C while priming.

Post Prime idle temps:

Asus PC Probe2 reported voltages vs Digitech QM1538 Digital Multimeter measurements while under load

+3.3v rail = 3.26v vs 3.387v real
+5v rail = 4.78-4.89v vs 5.02v real
+12v rail = 11.78v vs 12.23v real

**eva2000** · 12-20-2006, 04:54 PM

Now that we have a base reference overclock to fall back on @3600Mhz at 1.39v, it's time to mess around with the memory timings within bios and within Memset v3.1 beta. Still using 2x512MB OCZ PC5400 Platinum XTC 3-3-3-12 memory for the tests initially then will try other memory as well.

Memory timings
Being the first time using a 680i platform, there's so many options in bios to play with. So I spent a couple of hours using 2x512MB OCZ PC5400 Platinum XTC 3-3-3-12 and just playing in memtest86+ v1.65 to get a feel of what the main and advance timings could or could not do. I started with 9x333FSB with unlinked memory clocked at 333mhz 3-3-3-12 with 2T and 2.1v as the base reference setting. Then proceeded to tweak each memory timing/advance timing and see how it changed performance.

I'll use the following to quickly test each setting and graph the average result after 3 runs of each test:

Super Pi v1.50 1M and 2M tests
Mbench http://www.x86-secret.com/Download/mbench.zip

Format for testing:

Super Pi v1.50
1M run #1:
1M run #2:
1M run #3:
1M average:

2M run #1:
2M run #2:
2M run #3:
2M average:

Mbench
Access latency run #1:
Access latency run #2:
Access latency run #3:
Access latency average:

Read datarate (INT) run #1:
Read datarate (INT) run #2:
Read datarate (INT) run #3:
Read datarate (INT) average:
Write datarate (INT) run #1:
Write datarate (INT) run #2:
Write datarate (INT) run #3:
Write datarate (INT) average:

Read datarate (MMX) run #1:
Read datarate (MMX) run #2:
Read datarate (MMX) run #3:
Read datarate (MMX) average:
Write datarate (MMX) run #1:
Write datarate (MMX) run #2:
Write datarate (MMX) run #3:
Write datarate (MMX) average:

Read datarate (SSE) run #1:
Read datarate (SSE) run #2:
Read datarate (SSE) run #3:
Read datarate (SSE) average:
Write datarate (SSE) run #1:
Write datarate (SSE) run #2:
Write datarate (SSE) run #3:
Write datarate (SSE) average:

Results @9x333FSB = 3000Mhz with unlinked
2x512MB OCZ PC5400 Platinum XTC 3-3-3-12@333mhz 3-3-3-12

Bios settings Used:
Will highlight bios options in bold for any subsequent tests below which have changed from the initial settings outlined directly below.

AI Tuning: Manual
Nvidia GPU Ex: Disabled
LinkBoost: Disabled

FSB - Memory Clock Mode: Unlinked
x FSB - Memory Raio: N/A
FSB (QDR), Mhz: 1333 (means 333FSB)
Actual FSB (QDR), Mhz: 1332
MEM (DDR), Mhz: 667 (means 333mhz speeds)
Actual MEM (DDR), Mhz: 666.8

Vcore Voltage: 1.3875v
Memory Voltage: 2.100v for 1T/2T stock tests and 2.200v for 1T tweaked
1.2v HT Voltage: 1.3v
NB Core Voltage: 1.4v
SB Core Voltage: 1.55v
CPU VTT Voltage: 1.4v
DDRII Controller Ref Voltage: AUTO
DDRII Channel A Ref Voltage: AUTO
DDRII Channel B Ref Voltage: AUTO

tCL (CAS Latency): 3
tRCD: 3
tRP: 3
tRAS: 12
Command Per Clock (CMD): 2 clock (2T)

Advance Memory Settings
tRRD: AUTO
tRC: AUTO
tWR: AUTO
tWTR: AUTO
tREF: AUTO
Async Latency: AUTO

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
MCP PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled
LDT Spread Spectrum: Disabled

CPU Internal Thermal Control: Disabled
Limit CPUID MaxVal: Disabled
Enhanced C1 (C1E): Disabled
Execute Disable Bit: Disabled
Virtualization Technology: Disabled
Enhanced Intel Speedstep Tech: Disabled
LDT Frequency: 5x

PCIEX16_1 Frequency (Mhz): 100
PCIEX16_2 Frequency (Mhz): 100
PCIEX16_3 Frequency (Mhz): 100
SPP<->MCP Ref Clock, Mhz: 200

2T vs 1T vs 1T Tweaked
Graphed results with actual data further below. The graph represents the average of 3 runs for each test.

tCL (CAS Latency) - tRCD - tRP - tRAS - Command Per Clock (CMD)
tRRD - tRC - tWR - tWTR - tREF - Async Latency

3-3-3-12-2T
AUTO-AUTO-AUTO-AUTO-AUTO-AUTO

Super Pi v1.50
1M run #1: 17.188s
1M run #2: 17.187s
1M run #3: 17.187s
1M average: 17.1873s

2M run #1: 44.344s
2M run #2: 44.297s
2M run #3: 44.313s
2M average: 44.318s

Mbench
Access latency run #1: 60.0 ns (180 clocks)
Access latency run #2: 60.0 ns (180 clocks)
Access latency run #3: 60.0 ns (180 clocks)
Access latency average: 60.0 ns (180 clocks)

Read datarate (INT) run #1: 6876 MB/s
Read datarate (INT) run #2: 6873
Read datarate (INT) run #3: 6840
Read datarate (INT) average: 6863 MB/s
Write datarate (INT) run #1: 2246 MB/s
Write datarate (INT) run #2: 2291
Write datarate (INT) run #3: 2123
Write datarate (INT) average: 2220 MB/s

Read datarate (MMX) run #1: 7344 MB/s
Read datarate (MMX) run #2: 7294
Read datarate (MMX) run #3: 7335
Read datarate (MMX) average: 7324.33 MB/s
Write datarate (MMX) run #1: 2226 MB/s
Write datarate (MMX) run #2: 2278
Write datarate (MMX) run #3: 2035
Write datarate (MMX) average: 2179.67 MB/s

Read datarate (SSE) run #1: 7816 MB/s
Read datarate (SSE) run #2: 7756
Read datarate (SSE) run #3: 7764
Read datarate (SSE) average: 7778.67 MB/s
Write datarate (SSE) run #1: 6005 MB/s
Write datarate (SSE) run #2: 6012
Write datarate (SSE) run #3: 5998
Write datarate (SSE) average: 6005 MB/s

Reboot system and set 1T in bios

3-3-3-12-1T
AUTO-AUTO-AUTO-AUTO-AUTO-AUTO

Super Pi v1.50
1M run #1: 17.109s
1M run #2: 17.141s
1M run #3: 17.094s
1M average: 17.1157s

2M run #1: 43.078s
2M run #2: 43.015s
2M run #3: 43.047s
2M average: 43.0467s

Mbench
Access latency run #1: 55.7 ns (167 clocks)
Access latency run #2: 55.7 ns (167 clocks)
Access latency run #3: 55.7 ns (167 clocks)
Access latency average: 55.7 ns (167 clocks)

Read datarate (INT) run #1: 7114 MB/s
Read datarate (INT) run #2: 7145
Read datarate (INT) run #3: 7138
Read datarate (INT) average: 7132.33 MB/s
Write datarate (INT) run #1: 2476 MB/s
Write datarate (INT) run #2: 2482
Write datarate (INT) run #3: 2373
Write datarate (INT) average: 2443.67 MB/s

Read datarate (MMX) run #1: 7644 MB/s
Read datarate (MMX) run #2: 7656
Read datarate (MMX) run #3: 7664
Read datarate (MMX) average: 7654.67 MB/s
Write datarate (MMX) run #1: 2473 MB/s
Write datarate (MMX) run #2: 2478
Write datarate (MMX) run #3: 2371
Write datarate (MMX) average: 2440.67 MB/s

Read datarate (SSE) run #1: 8096 MB/s
Read datarate (SSE) run #2: 8165
Read datarate (SSE) run #3: 8168
Read datarate (SSE) average: 8143 MB/s
Write datarate (SSE) run #1: 6018 MB/s
Write datarate (SSE) run #2: 5998
Write datarate (SSE) run #3: 5982
Write datarate (SSE) average: 5999.33 MB/s

Reboot system and set 1T in bios and tightened advance memory timings in bios and memset.

3-3-3-12-1T
4-12-4-5-AUTO-AUTO

Super Pi v1.50
1M run #1: 17.109s
1M run #2: 17.109s
1M run #3: 17.110s
1M average: 17.1093s

2M run #1: 42.469s
2M run #2: 42.469s
2M run #3: 42.469s
2M average: 42.469s

Mbench
Access latency run #1: 55.7 ns (167 clocks)
Access latency run #2: 55.7 ns (167 clocks)
Access latency run #3: 55.7 ns (167 clocks)
Access latency average: 55.7 ns (167 clocks)

Read datarate (INT) run #1: 7170 MB/s
Read datarate (INT) run #2: 7150
Read datarate (INT) run #3: 7095
Read datarate (INT) average: 7138.33 MB/s
Write datarate (INT) run #1: 2651 MB/s
Write datarate (INT) run #2: 2643
Write datarate (INT) run #3: 2578
Write datarate (INT) average: 2624 MB/s

Read datarate (MMX) run #1: 7676 MB/s
Read datarate (MMX) run #2: 7659
Read datarate (MMX) run #3: 7618
Read datarate (MMX) average: 7651 MB/s
Write datarate (MMX) run #1: 2643 MB/s
Write datarate (MMX) run #2: 2638
Write datarate (MMX) run #3: 2564
Write datarate (MMX) average: 2615 MB/s

Read datarate (SSE) run #1: 8178 MB/s
Read datarate (SSE) run #2: 8175
Read datarate (SSE) run #3: 8179
Read datarate (SSE) average: 8177.33 MB/s
Write datarate (SSE) run #1: 5997 MB/s
Write datarate (SSE) run #2: 6000
Write datarate (SSE) run #3: 5999
Write datarate (SSE) average: 5998.67 MB/s

**eva2000** · 12-20-2006, 04:55 PM

Before I continue any further, I decided to make use of Asus 680i Striker Extreme's 3 include onboard thermal sensors. They're 2pin header thermal sensors you can attach to the motherboard to allow another 3 thermal monitoring readings from bios as well as Asus PC Probe2.

Here you can see the additional thermal sensors labeled as follows

OPT1 Temp = Mosfet heatpipe heatsink temps (near I/O panel)
OPT2 Temp = NB heatpipe heatsink temps
OPT3 Temp = SB heatpipe heatsink temps (shoved sensor inside the tiny hole in SB heatsink so probably alot higher readings than OPT1 and OPT2 which are stuck to heatsinks.

Room temp: ~29.5-30.8C
Cooling used: Scythe Infinity with mount mod + 1x Thermaltake 120x25mm 81cfm push-pull
Bios idle: 30-31C
Windows idle: 40-41C
Windows load: 53-54C
Rise above ambient delta = 22.2-24.5C
Rise above windows idle delta = 12-14C

As you can see today's a hot day here with 29.5C room temps. But the delta temps falls inline with Scythe Infinity air testing on E6600 with Intel D975XBX done here http://i4memory.com/showthread.php?t=3218 although there's 2x 120x25mm fans instead of one for Asus 680i Striker Extreme test above.

E6600 @2400Mhz at 1.254v + Intel D975XBX Bad Axe
Scythe Infinity + 2x Thermaltake 120x25mm 81cfm push-pull

Room temp: ~27-29C
Cooling used: Scythe Infinity + 2x Thermaltake 120x25mm 81cfm push-pull
Bios idle: 40-43C
Windows idle: 35-36C
Windows load: 50-51C
Rise above ambient delta = 22-24C
Rise above windows idle delta = 15-16C

So I guess the mounting mod works fine

**eva2000** · 12-20-2006, 04:55 PM

@3811Mhz - 9x423FSB 1:1 unlinked at 1.55v

Time to push the system further @3811Mhz - 9x423FSB 1:1 unlinked at 1.55v under load on air.

AI Tuning: Manual
Nvidia GPU Ex: Disabled
LinkBoost: Disabled

FSB - Memory Clock Mode: Unlinked
x FSB - Memory Raio: N/A
FSB (QDR), Mhz: 1694 (means 423FSB)
Actual FSB (QDR), Mhz: 1694
MEM (DDR), Mhz: 847 (means 423mhz speeds)
Actual MEM (DDR), Mhz: 847

Vcore Voltage: 1.675v = 1.57v windows idle/1.55v load
Memory Voltage: 2.100v for 2T stock tests and 2.200v for 1T tweaked
1.2v HT Voltage: 1.4v
NB Core Voltage: 1.4v
SB Core Voltage: 1.55v
CPU VTT Voltage: 1.4v
DDRII Controller Ref Voltage: AUTO
DDRII Channel A Ref Voltage: AUTO
DDRII Channel B Ref Voltage: AUTO

tCL (CAS Latency): 4
tRCD: 4
tRP: 4
tRAS: 12
Command Per Clock (CMD): 2 clock (2T) vs 1 clock (1T)

Advance Memory Settings
tRRD: AUTO
tRC: AUTO
tWR: AUTO
tWTR: AUTO
tREF: AUTO
Async Latency: AUTO

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
MCP PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled
LDT Spread Spectrum: Disabled

CPU Internal Thermal Control: Disabled
Limit CPUID MaxVal: Disabled
Enhanced C1 (C1E): Disabled
Execute Disable Bit: Disabled
Virtualization Technology: Disabled
Enhanced Intel Speedstep Tech: Disabled
LDT Frequency: 5x

PCIEX16_1 Frequency (Mhz): 100
PCIEX16_2 Frequency (Mhz): 100
PCIEX16_3 Frequency (Mhz): 100
SPP<->MCP Ref Clock, Mhz: 200

Both 2T and 1T Super Pi 32M were run with 4x cpuz windows open, Asus PC Probe2 running, memset v3.1 beta open as I was also monitoring the PC Probe2 reported temps while 32M ran. 2T managed to screen capture half way mark but 1T I forgot to do the half way mark screen capture :o

Super Pi 32M
@3811Mhz - 9x423FSB 1:1

2T = 16m 01.093s
1T = 15m 20.203s
1T tweaked 4-24-6-8 = 15m 12.359s
1T tweaked 4-15-6-8 tRFC 35 = 14m 19.844s

2T half way mark

2T completed

1T completed
- extra vdimm wasn't necessary just forgot to set it back to 2.1v :heh:

Notice the advance timings when set to AUTO result in different settings for 2T vs 1T:

2T Bios set = Memset reported
tRRD: AUTO = 4
tRC: AUTO = 24
tWR: AUTO = 6
tWTR: AUTO = 8

vs

1T Bios set = Memset reported
tRRD: AUTO = 5 - loosened from 4 in 2T
tRC: AUTO = 25 - loosened from 24 in 2T
tWR: AUTO = 6
tWTR: AUTO = 9 - loosened from 8 in 2T

tRFC which isn't available as an option in bios for both 1T and 2T were set AUTO = 45.

Note, that with 2x512MB modules it will be ~20 seconds slower than same clocked/timing 2x1GB modules for Super Pi 32M.

**eva2000** · 12-20-2006, 04:56 PM

So what happens when I set it to 1T and use memset to tighten the advance timings so the match the 2T AUTO set timings of 4-24-6-8 ?

1T tweaked half way

1T tweaked completed

**eva2000** · 12-20-2006, 04:56 PM

Now to use memset to tighten the advance timings to 4-15-6-8 with tRFC = 35 and look at this nearly 102 seconds faster than stock 2T @423mhz 4-4-4-12 at AUTO advance timings! But still slower than 975x chipset at same clocks by around 25-40 seconds. If you take into account ~20s slower with 2x512MB modules, means the Striker was around 5-20 seconds slower than 975x in Super Pi 32M at those particular timings below.

1T memset tweaked

**eva2000** · 12-20-2006, 04:57 PM

Now tightened tRAS to 4 and advance timings to 4-15-5-7 and tRFC to 32.

1T @423Mhz 4-4-4-4 4-15-5-7

Interesting for the 2x512MB OCZ PC5400 Platinum XTC 3-3-3-12 memory, if advance timings are set to AUTO values in bios, tRAS of 12 is fastest followed by tRAS for 4 and 1. Other tRAS values below 12 or above are slower, until you manually set the advance timings, only then will you see improvement in tRAS below 12.

Will try my Gskill HZ next ...

**eva2000** · 12-20-2006, 04:59 PM

bios pictures

**eva2000** · 12-20-2006, 04:59 PM

Regarding SLI/Sound read http://www.xtremesystems.org/forums/...5&postcount=18

Flashed to 402 bios
2x1GB G.Skill F2-6400PHU2 2GBHZ
Micron D9GMH 629 batch
Since everyone seems to be doing well with 402 beta bios, I decided to flash from 302 to 402 bios using Asus Ez Flash from within bios using my 4GB Corsair Voyager USB flash drive. Worked flawlessly. 402 bios brought 2 new bios memory timing options to the table, tRD and tRFC. tRFC can be seen in Memset v3.1v beta but tRD can't be seen in Memset right now.

Now using 2x1GB G.Skill F2-6400PHU2 2GBHZ Micron D9GMH 629 batch memory, I decided to play with the unlinked memory option finding my footing using the 5:9 divider below at stock 266FSB and 480mhz clocked memory

As always I used memtest86+ v1.65 to test the clocks before even booting into windows. I'd highly advise doing this all the time

AI Tuning: Manual
Nvidia GPU Ex: Disabled
LinkBoost: Disabled

FSB - Memory Clock Mode: Unlinked
x FSB - Memory Raio: N/A
FSB (QDR), Mhz: 1067 (means 266FSB)
Actual FSB (QDR), Mhz: 1067
MEM (DDR), Mhz: 960 (means 480mhz speeds)
Actual MEM (DDR), Mhz: 960

Vcore Voltage: 1.4v
Memory Voltage: 2.200v
1.2v HT Voltage: 1.4v
NB Core Voltage: 1.4v
SB Core Voltage: 1.50v
CPU VTT Voltage: 1.4v
DDRII Controller Ref Voltage: AUTO
DDRII Channel A Ref Voltage: AUTO
DDRII Channel B Ref Voltage: AUTO

tCL (CAS Latency): 4
tRCD: 4 then 3
tRP: 4 then 3
tRAS: 12 then 4
Command Per Clock (CMD): 2 clock (2T)

Advance Memory Settings
tRRD: AUTO
tRC: AUTO
tWR: AUTO
tWTR: AUTO
tREF: AUTO
tRD: AUTO < new in 402 bios
tRFC: AUTO < new in 402 bios
Async Latency: AUTO

CPU Spread Spectrum: Disabled
PCIE Spread Spectrum: Disabled
MCP PCIE Spread Spectrum: Disabled
SATA Spread Spectrum: Disabled
LDT Spread Spectrum: Disabled

CPU Internal Thermal Control: Disabled
Limit CPUID MaxVal: Disabled
Enhanced C1 (C1E): Disabled
Execute Disable Bit: Disabled
Virtualization Technology: Disabled
Enhanced Intel Speedstep Tech: Disabled
LDT Frequency: 5x

PCIEX16_1 Frequency (Mhz): 100
PCIEX16_2 Frequency (Mhz): 100
PCIEX16_3 Frequency (Mhz): 100
SPP<->MCP Ref Clock, Mhz: 200

E6600@2400Mhz 9x266FSB 480Mhz 4-4-4-12 2T at 2.2v

Advance Memory Settings
The advance memory settings set as AUTO in bios @5:9 unlinked 480mhz memory clocks showed up in Memset v3.1 beta in windows as:

tRRD: AUTO = 3
tRC: AUTO = 26
tWR: AUTO = 6
tWTR: AUTO = 8
tREF: AUTO = ??
tRD: AUTO = ??
tRFC: AUTO = 37
Async Latency: ??

I then ran Super Pi 32M but tightened the timings using Memset v3.1 beta to the following:

tRRD: 3
tRC: 26 tightened to 7
tWR: 6 tightened to 5
tWTR: 8 tightened to 7
tRFC: 37 tightened to 18

Managed 32M time of 20m 24.640s at E6600@2400Mhz 9x266FSB 480Mhz 4-4-4-12 2T at 2.2v

E6600@2400Mhz 9x266FSB 480Mhz 4-3-3-4 2T at 2.2v

Then I tightened both the main and advance timings even more in same windows session and ran Super Pi 32M with the following:

tCL (CAS Latency): 4
tRCD: 4 tightened to 3
tRP: 4 tightened to 3
tRAS: 12 tightened to 4
Command Per Clock (CMD): 2 clock (2T)

tRRD: 3
tRC: 7 tightened to 5
tWR: 5
tWTR: 7
tRFC: 18

Managed 32M time of 20m 16.891s at E6600@2400Mhz 9x266FSB 480Mhz 4-3-3-4 2T at 2.2v

Still have alot of tweaking to do. The unlinked memory mode isn't as flexible as I thought it would be - basically unlinked mode gives you more sets of fixed dividers than the linked mode, so you only have set options for each FSB you set. An example just to name a few memory options you have in unlinked mode for 266FSB (1067 QDR) are:

Memory clocks in unlinked mode:

915 actual 914.3Mhz
934 actual 933.4Mhz
949 actual 948.1Mhz
960 actual 960Mhz
978 actual 977.8Mhz
991 actual 990.5Mhz
1000 actual 1000Mhz
1067 actual 1066.7Mhz

Those are just a few of the examples there's many more.

So if you typed in 960, you'll get 960 = 480Mhz memory clocks.
If you typed in 970, you'll still get 960 = 480Mhz memory clocks.
If you typed in 985, you'll get 977.8Mhz = 488.9Mhz memory clocks.

**eva2000** · 12-20-2006, 05:07 PM

for more results

**Supertim0r** · 12-20-2006, 05:34 PM

really nice review as always eva

are you going to test the Kentsfield ?

**eva2000** · 12-20-2006, 07:45 PM

Yeah will test my Q6600 after get memory/timings etc figured out

**hausner** · 12-20-2006, 07:52 PM

alot of pictures , i liked

**Iceflight** · 12-20-2006, 08:05 PM

What a job!!!! Thanks bro......

**flesheatinvirus** · 12-21-2006, 04:41 AM

That was a

load of juicy info on that board, great job as always. I may just pick one of them up.

**noobzed** · 12-21-2006, 09:44 AM

Do you have sound issue with Striker and SLi enabled, specially in games ?

**kromosto** · 12-21-2006, 11:29 AM

totally amazing review as always thanks again eva i like to read your reviews.

**eva2000** · 12-21-2006, 04:06 PM

Glad you guys like

Regarding SLI/Sound:
Still testing ram/settings etc and have yet to try SLI so no idea on sound issue yet. But Asus Striker is different from reference 680i in that it moved the sound off the motherboard to a separate daughter board card which is x1 PCI-E based and slots into the PCI-E slot. From what Andre or someone one this forum has experienced they don't have sound issues when SLI is enabled due to this difference. I can't confirm it until I run SLI later though.

The separate sound card and it's array microphone

**sdumper** · 12-21-2006, 04:09 PM

Confirmed no sound issues....
Of course your still better off using a creative sound card...

**kraggy** · 12-21-2006, 04:23 PM

Eva-bro, have you tried this mobo with a quad chip yet?

**eva2000** · 12-21-2006, 04:32 PM

only had board for 4 days and have 6GB of DDR2 memory to test first with all the settings.... so yes will get around to Q6600 but will be a while yet heh

Shamino got his Striker to push 371FSB with QX6700 http://forums.vr-zone.com/showthread.php?t=115689 though which is better than other 680i boards around 280-350FSB.

**msgclb** · 12-21-2006, 04:42 PM

Originally Posted by eva2000

After showing the Asus 680i Striker Extreme bios and setup photos, it's time to get down to some testing and results

That sure is a high tech test bench you have.

You'd be broke if you had to get all those photos developed. I can only think of one word to say about your review: amazing.

Can I steal some of your methodology to test my new Asus P5N32-E SLI? It's actually installed on a more up to date test bench!

**eva2000** · 12-21-2006, 07:24 PM

Originally Posted by msgclb

That sure is a high tech test bench you have.

You'd be broke if you had to get all those photos developed. I can only think of one word to say about your review: amazing.

Can I steal some of your methodology to test my new Asus P5N32-E SLI? It's actually installed on a more up to date test bench!

Thanks...LOL yeah photo development would be alot if it wasn't for my Nikon 5700

sure you can use my methodology to test your new board... Good luck and happy oc'ing

**eva2000** · 12-22-2006, 06:01 AM

Updated above post with some 2GB Gskill 6400PHU2 D9GMH tests http://www.xtremesystems.org/forums/...59&postcount=9

**GAR** · 12-22-2006, 10:31 AM

EVA regarding the G.SKILL you have to upgrade to the 0505 bios in order to get the most out of the ram, my limit was below 500, i updated to the 0505 bios and bam goes over 500 easily.......update to 0505 bios, stable and much better for OC.

Thread: E6600 + Asus 680i Striker Extreme

Thread Tools

Search Thread

Rate This Thread

Display

E6600 + Asus 680i Striker Extreme

Bookmarks

Bookmarks

Posting Permissions