Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results
This is a discussion on Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results within the Asus Intel motherboards / CPU forums, part of the Intel motherboards / CPU category; Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results After showing the Asus 680i Striker Extreme ...
![]() |
| | LinkBack | Thread Tools |
| | #1 (permalink) |
| Administrator | Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results 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:
Memory to be used:
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:
![]() 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 @2400mhz at 1.3875v bios set (1.28v vcore idle / 1.26v vcore 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 |
| Last edited by eva2000; 28-12-2006 at 05:06 AM. | |
| | |
| | #2 (permalink) |
| Administrator | Re: Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results
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:
Format for testing:
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.
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
Reboot system and set 1T in bios
|
| Last edited by eva2000; 20-12-2006 at 04:23 PM. | |
| | |
| | #3 (permalink) |
| Administrator | Re: Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results
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. Idle ![]() Prime95 Load ![]() 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 Intel Core 2 Duo E6600 - cpu air/water cooling compared although there's 2x 120x25mm fans instead of one for Asus 680i Striker Extreme test above.
|
| Last edited by eva2000; 20-12-2006 at 04:31 PM. | |
| | |
| | #4 (permalink) |
| Administrator | Re: Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results Asus 680i Striker Extreme & other downloads
Well I just updated again using USB flash drive in Asus bios' EZ Flash from 0402 to 0505 official bios and it has fixed my heavy vcore undervolting from bios set value issue! 1.3875v vcore on: 0302 official bios = 1.28v bios and 1.26v under load in windows 0402 beta bios = 1.28v bios and 1.26v under load in windows 0505 official bios = 1.36 bios and 1.34v under load in windows Lastest Official Bios: http://support.asus.com/download/dow...iker%20Extreme 1002 bios ftp://ftp.asus.com/pub/ASUS/mb/socke...treme/1002.zip
0701 bios http://dlsvr01.asus.com/pub/ASUS/mb/...eme/SE0701.zip
0505 bios http://dlsvr01.asus.com/pub/ASUS/mb/...eme/SE0505.zip
----------------------------------------------------------------- Comments and opinions: Have to put this somewhere so thought why not this post. I'll keep updating this as I go along ![]()
Bios template for 680i Striker users to report their settings:
Just compiling useful info to help me and others get started. While P5N32-E SLI is a different board from Striker Extreme, it's useful to see what bios settings/voltages folks use to achieve what overclocks they manage to pull off ![]()
Reviews: Some of the reviews online from around the world. Please pay attention to the date of the review and bioses used in these reviews as there's usually a natural progression of improvement and bug fixes as the bios matures ![]()
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 a few folks online have 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 Other notes/links: Nvidia statement on December 18, 2006 regarding 680i SATA corruption issues here
|
| Last edited by eva2000; 18-02-2007 at 02:23 AM. | |
| | |
| | #5 (permalink) |
| Administrator | Re: Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results @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.
![]() 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 ![]() ![]() 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. 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 ![]() 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 ![]() 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. |
| Last edited by eva2000; 20-12-2006 at 11:56 PM. | |
| | |
| | #6 (permalink) |
| Administrator | Re: Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results 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 ![]()
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:
|
| Last edited by eva2000; 23-12-2006 at 03:34 AM. | |
| | |
| | #7 (permalink) |
| Administrator | Re: Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results Advance Memory Timings - What does AUTO option assign ? More memory tests... This time to investigate what the bios sets the advance memory timings to when set to AUTO for each memory clock frequency. Again ALWAYS use memtest86+ v1.65 to test settings before booting windows. Quick Memtest86+ v1.65 Procedure I use a quick test first consisting of:
![]() System:
9x266FSB 4-4-4-12 2T fixed I'll be only changing the unlinked mode divider keeping FSB fixed at 266FSB and timings fixed at 4-4-4-12 2T for initial tests. These screenshots below are just to find out what AUTO responds to for advance timings in memset v3.1 beta in windows.
4:5 - 333Mhz ![]() 2:3 - 400Mhz ![]() 8:15 - 500Mhz Raised vdimm to 2.25v and NB to 1.5v ![]() 1:2 - 533Mhz Raised vdimm to 2.4v and NB to 1.6v ![]() 9x266FSB 5-4-4-12 2T fixed Changed only to CAS = 5. Findings:
1:2 - 533Mhz Raised vdimm to 2.4v and NB to 1.6v ![]() 7:15 - 571Mhz Raised vdimm to 2.45v and NB to 1.6v ![]() 6:13 - 577Mhz Raised vdimm to 2.45v and NB to 1.65v ![]() 5:11- 586Mhz Raised vdimm to 2.55v and NB to 1.65v ![]() 4:9- 600Mhz Raised vdimm to 2.575v and NB to 1.65v ![]() ![]() Raising NB from 1.65v to 1.7v allowed me to pass single 32M run @600Mhz 5-4-4-12 at 2T at 2.575v vdimm. Memset seems to have not reported the right tRC value compared to what CPUZ is reporting tRC = 33. |
| Last edited by eva2000; 29-12-2006 at 07:05 PM. | |
| | |
| | #8 (permalink) |
| Administrator | Re: Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results
The REAL reason for choosing an Asus 680i Striker Extreme SLI motherboard is of course for SLI ![]() 2x 640MB Gainward 8800GTS SLI twins with 97.44 drivers System:
3dmark06 stock @513/1584 ![]() 3dmark06 oc'd @648/2052 ![]() Yup cpu limited for 3dmark06 with E6600@2400Mhz stock ![]() Asus PC Probe2 reported PSU rail voltages: Asus PC Probe2 reported voltages vs Digitech QM1538 Digital Multimeter measurements while under load @2400mhz at 1.3875v bios set (1.28v vcore idle / 1.26v vcore 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 Now let's check out nVidia's LinkBoost technology which is available on 680i motherboards when couplied with 79xx/88xx nVidia video cards. Straight from nVidia.com web site pdf tech documents on LinkBoost:
3dmark06 Linkboost disabled in bios = 15,331 Linkboost enabled in bios = 15,361 Linkboost disabled ![]() Linkboost enabled ![]() SM2.0 Score = dropped 0.0688% HDR/SM3.0 Score = dropped 0.412% CPU Score = increased 1.28% Looks like Linkboost didn't do much for the actual GPU component tests ? Might need to test a full range of graphic benchmarks etc to find out. Notice SPP/MCP PCI-E bandwidth went from 2500Mhz to 3125Mhz exactly 25% increase ![]() LinkBoost made 3dmark benchmarks a bit unstable it seems so disabled it in bios again. Gainward Bliss 8800GTS SLI @621/2052 3dmark05 ![]() 3dmark2003 ![]() There's some improvement for 3dmark06 for higher mem clocks 400mhz 4-4-4-12 2T auto vs 533mhz 4-4-4-12 2T auto - 533mhz gained 15490 - 15361 = 129pts @621/2052 clocked 8800GTS SLI ![]() ![]() ![]() ![]() Something weird i noticed with linkboost disabled at 1.55v NB volts, ntune shows MCP/SPP PCI-E at 2500mhz.. but raise NB volts to 1.6v with linkboost still disabled, ntune shows MCP PCI-E at 3125mhz ... MCP PCI-E auto scales with NB volts ? Looks like 426Mhz 4-4-4-12 1T is faster than 533mhz 4-4-4-12 2T even for 3dmark06 426mhz 4-4-4-12 1T = 15,506 533mhz 4-4-4-12 2T = 15,490 |
| Last edited by eva2000; 31-12-2006 at 06:08 PM. | |
| | |
![]() |
| Bookmarks |
| Tags |
| 680i, asus, core, duo, e6600, extreme, intel, motherboard, results, sli, striker |
« Previous Thread
|
Next Thread »
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
Similar Threads for: Intel Core 2 Duo E6600 + Asus 680i Striker Extreme SLI motherboard Results
| ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| [hwbot] Super Pi v1.50 - 1M rankings pt2 | hwbot | HWBOT Official Rankings | 25 | 22-12-2009 07:11 AM |
| [hwbot] Super Pi v1.50 32M rankings - i4memory.com | hwbot | HWBOT Official Rankings | 437 | 14-04-2008 12:34 PM |
| Intel Core 2 Duo E6700 + Asus 680i Striker Extreme SLI | eva2000 | Asus Intel motherboards / CPU | 13 | 21-02-2007 02:35 AM |
| Asus 680i Striker Extreme SLI + Sound issues [LinkBoost/GPU EX] | eva2000 | Asus Intel motherboards / CPU | 0 | 03-01-2007 01:07 PM |
| Intel Core 2 Duo E6600 Conroe + Intel D975XBX Installed | eva2000 | General Intel Motherboards / CPU | 128 | 23-07-2006 02:56 AM |
All times are GMT +11. The time now is 03:09 PM.

































































