TerraRaptor

Yup, differentSLIauto software to patch nvlddmkm.sys and force Control Panel to display SLI submenu. Will actually allow 560+580 - any combo within generation.

screenshot with 427.7 uploaded

Me too. But i will try to meet 2% difference.

Will do it today

They are running SLI, see gpuz. That is mixed cards SLI, submitted into SLI category of stronger card.

Looking how great pcmark is in scaling with greater core count, I would doubt it. Both cpus will share just 2 channels of ddr2 (that sould also be a challenge to overclock). Though, I'm curious of the result.

That vcore!

Should be 1c/1t in task manager then.

Count any cores as classic cores. not caring if they are P or E. Any other approach will make it unfair for users of previous generations. Besides, if we allow disbaling E-cores to allow P-cores to participate in lower core count ranking shouldn't then we allow disabling cores on any other cpu to stop L3014/phenomx2 domination in x1/x3/x5 rankings?)

Stop forcing me to fry that poor memory:) Gonna try to improve in September, this was done within 1h after OS install - need to make htt mod, vdimm mod and choose better cpu. My hope is for 410-420 range.

Not the reason for fullpot I think - my e6400 was happy fullpot with 2.5-2.7 vpll.

Won't really help. I knew of that change and still was surprised today when my teammate dm'ed me with WTF - I just forgot of that change in rules as Geek was never my passion (yet I confirm to know that new rule before and I know the reasons/drama behind that change). So, as Leeg writes, RTFM check rules before you bench. Actually, had an issue of not reading rules 2 days ago - wasn't careful submitting for mem stage of teamcup and forgot SPD tab. But rules are rules.

Monster

Sweet silver. Waiting 32m from you!

Stage rule says "2 videocard cores total". So we need crossfire or x2 card for this stage. PS. I'm stupid:) was looking wrong gpuz window.

Nice one TAGG. Also noted cpuz is more heavy than wprime:)

Great platform clock. Hope we see maximum of 300.7 from you:)

Why not to make a thing that acts like AIDA64 (measures read/write/copy/latency) with 3dmark01 like formula for final score? I was running aida on very different setups (from mendocino to haswell-e, diffferent chipsets (via/sis/intel/nvidia/amd) and it was quite informative. Problem about aida64 is that diffferent versions have different optimisations - still, you can now make a version that will cover all existing memory types from EDO to DDR4 (I think we won't see anything newer than alder lake with ddr4?). So that will be one "basic" part - which won't be updated with newer algorithms (just bugfixes). Call it "legacy mode". And all newer hardware will have different mode that you will be able to update - and changes in that part can be then covered with hwbot rules.

Seems like Gorod was right saying that PCIE may influence the clocks on nv43 (http://www.xtremesystems.org/forums/showthread.php?248552-6600GT-834MHz-gt-03-05-06-WR&p=4321051&viewfull=1#post4321051) - I did a quick test myself dropping bclk with 2500K from 104 to 100 and card lost stability. Probably nv43 needs a combo of temperature, voltage and pcie clock to show good gains. For me, going cold gained at least 100MHz.

Data in your table displays just a normal variance imho. I think after 100 runs both datasets will average to the same values.

I estimate power consumption as 100W here, vdrop is not big (i actually did a pretest with single pair of wires, then soldered another pair - no magic difference even with single pair of wires). Capmod didn't help either. These cards seem to prefer cold a lot. Tested a total of 3 cards (2 asus with infineon 2ns, 1 giga with samsung 1.6ns). Important note on 6600GT (and other cards with ISL6534) - you better epower both vgpu and vmem as ISL6534 controls them both and likes to trigger protection if only single section is epowered. ISL6534 also controls PCIE 1.2v voltage but epowering it or changing it didn't help at all - so can be left at stock.

Should have MMX only option for oldest platforms (sdram/ddr). Run time of around 50-60 seconds maximum no matter what speed is (so it is not "how much time it took to finish job" but "how much of the job was done"). Probably a separate workload for different DRAM technologies - to be able to address specific platform issues more easily? SDRAM+DDR (MMX only available)/DDR2+RDRAM (SSE2)/DDR3 (SSE3)/DDR4 (AVX+)/DDR5/DDR6. Anyway, the most valuable thing should be consistency, repeatability and coverage of most hardware.

Great action!

Great one. Old school asrock rocks.

right, not the best one - wasn't able to quickly boot 540x7. Batch L734A770, Malay