TeamAU's Tour de Force - 7x World Record! (and one silver)

The embedded Facebook post below already hinted towards this, but now it's sort of official. On their annual meetup, TeamAU set not one, not two, not and-so-on, but seven (7!) world records. The benchmark records range from 3DMark06 over 3DMark Vantage to the latest 3DMark. There are two systems used in combination with a set of four Radeon R9 290X graphics cards: a 6.1GHz Ivy Bridge-E on Rampage IV Black, and a 6.4GHz Haswell combined with the Z87X-OC motherboard.

Althought many feel the term World Record is tossed around so much these days it loses its meaning, this is a pretty impressive achievement from the boys Down Under. Not only because these are overall benchmark records, but because there are so many of them. Remember Hipro5 or Oppainter's trifecta's from back in the day? This is exactly like that!

Congratulations goes out to the entire TeamAU: Bob(nz), Fester, Dinos22, SniperOz, Moloko, and Youngpro. Awesome benching!

Benchmark Score Hardware User
3DMark06 56366 marks GeForce GTX Titan Australia TeamAU
3DMark Vantage - Performance 97384 marks Radeon R9 290X Australia TeamAU
3DMark11 - Performance 41630 marks Radeon R9 290X Australia TeamAU
3DMark - Ice Storm 262346 marks Radeon R9 290X Australia TeamAU
3DMark - Cloud Gate 56256 marks Radeon R9 290X Australia TeamAU
3DMark - Fire Strike 34491 marks Radeon R9 290X Australia TeamAU
3DMark - Fire Strike Extreme 21792 marks Radeon R9 290X Australia TeamAU
Unigine Heaven - Xtreme Preset 8685.23 DX11 Marks Radeon R9 290X Australia TeamAU



23

Finland FM_Jarnis says:

No SystemInfo at all, no way to check for a number of potential "tweaks".

* Time measurement data not available. The validity of the result cannot be determined.
* SystemInfo scanning was not enabled for this benchmark run. Please enable SystemInfo from benchmark settings and re-run the benchmark.
* Processor is not recognized
* Graphics card is not recognized
* Graphics driver is not approved


..your call if you call a result like this a record, but I wouldn't.

United States Mikecdm says:

The irony. I got accused of being a cheater and threatened with a 12 month ban for posting a result with time measurement issues, yet the accuser posts a WR result with the same issue and even more.

websmile says:

Report him... :D

United States Gunslinger says:

FM_Jarnis said: No SystemInfo at all, no way to check for a number of potential "tweaks".

* Time measurement data not available. The validity of the result cannot be determined.
* SystemInfo scanning was not enabled for this benchmark run. Please enable SystemInfo from benchmark settings and re-run the benchmark.
* Processor is not recognized
* Graphics card is not recognized
* Graphics driver is not approved


..your call if you call a result like this a record, but I wouldn't.


What specific results? :p

United States l0ud_sil3nc3 says:

. . . and this is why I don't bench 3D :D Well that and I suck at it lol

Australia JJJC says:

What result(s) are you referring to?

Germany der8auer says:

I randomly had sh*t like "Time measurement data not available. The validity of the result cannot be determined." for no reason even tho I know everything was 100% legit. So no, just no.

United States Schmuckley says:

Oh thank goodness somebody else has spoken up about that! I get it randomly at times, too. Yet Mike gets a score yanked because of it.buuuuuu I think it might be tied to FSB OCing. As for card not recognized and drivers and all that..Futuremark hasn't gotten around to adding the newer cards/drivers to their database. also pretty weaksauce.

United States Splave says:

can we make an exception for 3dmark03 sometimes the only way I can run in light OS is -nosysteminfo in target field...

Norway knopflerbruce says:

I don't see the relevance of having the driver approved. IMO any driver is approved until it's showing signs of being bugged. We can't approve all drivers, can we? There are hundreds of older nvidia drivers, just the 169.xx series alone has like 20 I think.

Australia newlife says:

der8auer said: I randomly had sh*t like "Time measurement data not available. The validity of the result cannot be determined." for no reason even tho I know everything was 100% legit.

So no, just no.


If it's windows 7 or older then it should be allowed, I've had it happen to me no reason a number of times so I don't use the latest systeminfo anymore

Belgium Massman says:

Maybe we should have specified "HWBOT World Record" :p

says:

thanks for your input Jarvis

Over the last few years the community has moved away from HOF and towards HWBOT for rankings, HOF has been unreliable and HWBOT has a rankings system that is much more community tailored

So while we enjoy your benchmarks, the community now respects HWBOT as the only place to validate results and we will run our benchmarks within the rules of HWBOT

Australia Dinos22 says:

Hear hear

Finland FM_Jarnis says:

der8auer said: I randomly had sh*t like "Time measurement data not available. The validity of the result cannot be determined." for no reason even tho I know everything was 100% legit.

So no, just no.


That error message comes up if your SystemInfo is disabled or you are using an older SystemInfo which does not support this check.

Now if it says "Time Measurement data not accurate", then one or more of the RTC sources of your system disagree with each other more than we allow. This is essentially "the RTC cheat" that showed up with Win8.

Now if you are having issues with the "time measurement data not available" showing up even with SystemInfo 4.23, we would be VERY interested in hearing about your hardware configuration and seeing a result file. Only way I could see this error happening is if SystemInfo outright cannot query the RTC clock status during the run.

Germany der8auer says:

It was OC related. I was benching with Dancop for the Pro OC Cup Fire Strike Extreme stage. The first 10 results were valid and no problems. But our best two results were invalid but we only changed the GPU clock. Nothing else.

Finland FM_Jarnis says:

der8auer said: It was OC related. I was benching with Dancop for the Pro OC Cup Fire Strike Extreme stage. The first 10 results were valid and no problems. But our best two results were invalid but we only changed the GPU clock. Nothing else.


So system stability issues; I guess SI process crashed due to overclock, required data was not obtained for the result file and you then get that error.

I would call such a result "not valid" and FM HoF agrees with me. Up to you what HWBot holds as a standard in such cases.

Germany Moose83 says:

In Pcm05 im not allowed to upload time meassure scores :p

Germany der8auer says:

I also did not upload the "invalid" scores. But from my experience I just know that those error messages do not always indicate a real invalid score.

Finland FM_Jarnis says:

der8auer said: I also did not upload the "invalid" scores. But from my experience I just know that those error messages do not always indicate a real invalid score.


We're happy to analyze result files that 3DMark.com thinks are invalid but you think are not. Send them to info [at] futuremark.com with the details.

Naturally we'd prefer that 3dmark.com will never reject a result without a good reason, so we're more than happy to take a look at any cases where you think it is in error.

Australia Uncle Fester says:

look I've come out of a 1 year hiatus to bench and typically some twat calls possible cheat. Jarvis all scores are legit and I couldn't give a flying fuck if you think otherwise. we know we broke the records and don't require validation from FM or even HWBOT. we also broke 03 but rubbish FM won't accept the valid at all. so we didn't post it. we emailed pasi about it.

Australia t8y says:

lol FM
i thought tall poppy syndrome was uniquely aussie, cheers guys now i know better.

anyway
how many other legit scores on here (not talking WR) wouldnt be accepted by you guys anyway... no one cares about the FM HOF

surprised they even bothered to comment, wouldnt they be too busy making yet another unlimited ultra extreme preset for all the 3dmark tests?


uncle fester said:
we also broke 03 but rubbish FM won't accept the valid at all. so we didn't post it. we emailed pasi about it.


iirc, this was on the same systeminfo that worked for all the other benches right?
03 just got fussy.

anyway dw too much dude.

United States chartiet says:

To confirm,

Even after verifying running the latest SystemInfo (even though the error still says it?), the error:

"Time measurement data not available. The validity of the result cannot be determined." is overclock related (even though no overclock but maybe a weird RAM timing that Memtest didn't error out...?) and not SystemInfo related?

Is it an issue with the SI not updating due to the message even after installation of the latest?

Also, why does it say G3420 when its a G3258?

Please log in or register to comment.

Leave a Reply: (BBCODE allowed: [B], [QUOTE], [I], [URL], [IMG],...)