Massman

it will be

You have an advantages, but still it's just luck. We're not intended to take away every possible advantage just because others might not be so lucky. You know, some are lucky to find a 5.5G i7 with their first buy, others have to go through 50 to find one ...

No official statement yet - first development

Slow-mode qpi?

Uh-oh ...

Isn't this more interesting? Now, you have to compete at lower rankings, which means that the battle for those last points is more tight.

Fixed

Technically possible, but unmoderateable. We can never guarantee users choosing the right cooling category, so that's why the cooling information is purely informational.

I think we'll have to wait for our coding-guru RB

As far as I know, the team results are calculated based on the results of the 20 best scores. Since your team only has 11 scores, I presume the other 9 places are filled with 0-pointers, making the average really bad.

Hmm, I'd prefer the GPU-Z application for screenshots. There's just more info available.

Without to start with, but ... it will become very easy to change that decision :-)

Only RB is entitled to make new pages at Hwbot, I'm not. I think he's going to integrate this in the a new very cool upcoming feature at Hwbot

Could be a semi-dead chip, I've seen other AXP's losing half of their cache before.

His account's still there as well as his points. Must be an issue with the hwboints-engine; we'll see in 24h

Blocked and waiting for further comments.

Fixed by Demiurg

Fixed!

As you wish

Both results were in line with the other scores; there's no need to delete good entries because something small was missing. Beat your current scores and submit those ...

It's 3D stable ... it's not like were talking 6second 1M stability

I asked them what was wrong with my submission and this was the answer: It seems like the benchmark files are corrupted in your system. The benchmark checked its own files and found that some of the files have been tampered and it can not verify its own integrity, possible reasons are: you have renamed some of the files, there is some sort of virus in your system that has attached itself to the files, some program has put a run-time hook on the .dll files (similar to what 3DAnalyze used to do in the olden days). These come to mind when this error occurs. The rule with this particular error in this benchmark is that we can not reset the flag as the benchmark thinks it is invalid and 3DM03 does not send the checking data to the server like later versions of the benchmark does so we can not verify the exact reason for this flag. I only installed 3DMark03 ^^

An ORB link is mandatory for top20. It seems that FM has a lot of problems with orb validations. I have a 106k and my friend has a 160k, both are non-publishable on the orb. That's, however, very difficult for us to moderate since we have no guarantee that results are legit. I'm not saying we don't have faith that you're completely okay, it's just ... if we validate yours, we kinda have to validate everyone's. And thus possibly those of people who use illegal 'tweaks' to boost their scores. I hope you understand this a bit

Oh, wait ... now I see the problem. It's not a few bugged loops, but the end time is too fast if you compare it to the other loop results. At loop 10, he's already 1 second behind you whereas in loop 15 he's one second ahead. Blocking the result may indeed be more appropriate given the large variations in loop time.

yes they should