Can a member of staff please clarify which piece of hardware must be unique in this Stage?

Memory kit

On the this stage, does the score have to be triple channel or does dual/single qualify as well?

The only requirement is LGA1366

Thanks!

Now, if I can just find that submission button again

Is it correct, that this result is not valid?

http://www.hwbot.org/community/submission/2101207_ftw_maxxmem_ddr3_sdram_2030.7_marks

Missing CPU-Z SPD Window...

_

Christian

Yes, you`re right.

- Note: CPU-Z SPD and CPU-Tweaker must be included in the screenshot

So result is blocked

The result from him that comes next, has the same problem...

http://www.hwbot.org/community/submission/2098370_ftw_maxxmem_ddr3_sdram_1849_marks

_

Christian

Limitaties:

- Please attach a picture of your overclocking rig.

- A verification screenshot is required.

- Only use processors using socket LGA1366.

- Must use the 2:6 memory multiplier

- Must use the official competition background

- Note: CPU-Z SPD and CPU-Tweaker must be included in the screenshot

My screen was invalid but CPU-Z SPD and CPU-Tweaker is in the screenshot.

U can see my memory in maxxmem and in cpu-tweaker (isn't possible to change settings)

CPU-Z Memory tab is mandatory by HWBOT general rules.

I want to object. The russians have same model memory. Wasn't the memory supposed to be unique ?

Also the greek team is using the same/similar memory kit on each submission.

The germans also have the same model memory.

That's correct. I'm going over the submissions again

Is that possible? I mean the bot should automaticly select only submisions with the different unique hardware required for the stage, no?

Also the greek team is using the same/similar memory kit on each submission.

 

The germans also have the same model memory.

They are using different kits. Check out the part number

Is that possible? I mean the bot should automaticly select only submisions with the different unique hardware required for the stage, no?

Not for the memory. It was grouping based on DDR1, DDR2, DDR3 ...

Russians are also using different kits.... one has T1 in part number, second one not... (one old revision and one new revision)

But mistake is in rules - MM should sets three different manufacturers to avoid such discussions

They are using different kits. Check out the part number

 

How can you see the part numbers ?

Russians are also using different kits.... one has T1 in part number, second one not... (one old revision and one new revision)

But mistake is in rules - MM should sets three different manufacturers to avoid such discussions

It should be different models which are visibly different. For example Gskill Pi, Gskill ripjaws X.

How can you see the part numbers ?

In the CPU-Z SPD tab. You can also see it in CPU-Z Tweaker .

Guys are living far away for each other - using totally different setup but similar (not the same) memory - it is up to MM to choose block submission or not - I`m as a captain of participating team don`t wanna discuss it anymore to avoid any issues.

We will accept it.

In addition to last year's rules, the top-3 must use different (!) hardware.

What means different?

In the CPU-Z SPD tab. You can also see it in CPU-Z Tweaker .

I see, indeed they are using different memories. I rest my case.

What means different?

Different hardware based on benchmark type:

CPU benchmark = different CPU

VGA benchmark = different VGA

MEM benchmark = different memory

MB benchmark = different mainboard.

OK, explanation still doesn`t show different models, different vendors, different types or different revisions =)

OK, MM thanks, I hope fair play and true spirit of overclocking will live for a long time.

BTW, it doesn`t change positions

OK, explanation still doesn`t show different models

I think different models...

So it should be stated, no offense.

It`s a pity that it wasn`t clearly written before the start, but I`m sure that it will help during next stages and will be written next year in rules.

First two stages were a bit rough; I don't see any problems coming up with the next 4

But I agree - next year, more clear!

and finally these are models: KHX16000D3ULT1K3/6GX and KHX2000C8D3T1K3/6GX =)

and finally these are models: KHX16000D3ULT1K3/6GX and KHX2000C8D3T1K3/6GX =)

Ugh, you're right. I hate Kingston for using so similar partnumbers

9905403-039.A00LF (DFB)

9905403-067.A00LF (SV1SH)

Thanks for understanding. We will avoid such situations in future.

That is ok, but 31ns latency...

that's random, not tweakable

The scores with under 33ns latency are bugged... unless they are at 5.7GHz uncore

Gratz for Russian team! Was hard fight! Молодцы!

The scores with under 33ns latency are bugged... unless they are at 5.7GHz uncore

Oh! http://hwbot.org/community/submission/2105354_micutzu_maxxmem_ddr3_sdram_2358_marks

uncore only 5000mgz lat 31.3ns

Gratz for Russian team! Was hard fight!

Yes it was difficult. At you very good results!

Well, you guys name it. Bug or tweak. But if it is bug, all <33ns scores must go

For low latency have one tweak, no comments more, need using true benchmarks)))

That I agree, MaxxMemm is not quite reliable, and that is a problem, because if we start to check which is bugged and which not, it is definately a pain in the but.

For low latency have one tweak, no comments more, need using true benchmarks)))

I'm now playing this card: "Any special software tweaks must be explained to the HWBOT staff during the competition"

I'm now playing this card: "Any special software tweaks must be explained to the HWBOT staff during the competition"

All trick in optimal selection subtimings in CPU-Tweaker, loading windows on BLCK 250+ and lowering of BLCK frequency in windows. It is all.

It is not software tweak, it is right settings in BIOS =) need higher boot fsb frequency!

Tricky!

Guys, I think that it can be fair to remove stage with bugged benchmark or accept as it is.

I`m sure in future competitiions MaxxMemm will be updated or removed at all.

Our time, ln2, money, experience, died hardware and now remove this stage? I am disagree