Rauf

No need to get upset, it's just a discussion. I'm not saying you're cheating or something. Maybe saying it's "obviously bugged" was a too strong statement, sorry for that. But still, there is a reason you checked the score with FM right? As far as I know the Fire Strikes were designed to be "non tweakable" and measure "pure performance". Of course we bypass this by LOD/tesselation etc. But FS it's not like legacy benching. The thing that makes me wonder is that your score is not consistent across the tests, and not consistent with your Time Spy result. If it truly had been "all about mem", or to find some combination of temps/core/mem/volts to make the card perform better you would do better in GT1 and combined also, and in Time Spy. Of course the different subtests can scale differently, but your scaling in GT2 is a bit extreme in my opinion. With that being said, of course there could be other explanations than bugged score... When I ran for wild card qualifier I got a few bugged scores when pushing mem really high on RX460. Once I got almost 50% higher in combined for example. You would not call this bugged? Where do you draw the line, 5%, 10%, 50%??? When I have just seen these types of bugged scores, of course it makes me wonder... Also, we have this from last year's qualifier: https://community.futuremark.com/forum/showthread.php?183665-GALAX-GOC-2015-WORLDWIDE-QUALIFIER&p=1881070&viewfull=1#post1881070 Aranha got some scores removed, due to too high GT2 results. Those scores would have taken him to the finals... Maybe you can understand my point of view a little better? I'm not trashing the score, I'm discussing it. If it actually were possible to get bugged scores, would it be good to find that out?

Thanks!

I see only one other person with high GT2... but I agree it is very hard to tell for sure. Would require access to FM tools to look at frame rates through out the test. Last year FM removed a couple scores because of "bugged runs". But then again, that might not work either cause you can have consistent bugged frames through one of the subtests. Only possible explanation I see would be a specific LOD which is exceptionally good for GT2, but bad for GT1 and combined... I'll leave this be now! steponz, hope you understand this is nothing personal, I know you are a great 3D-bencher and seem like a really nice guy. Maybe there is some other tweak I just don't know... I'm just sick of bugged benchmarks, cheatable benchmarks (32M) etc... Is there any benchmark we can trust?

core and mem are exactly same freq in those runs. What differs is mostly cpu score. And diff in both GT1 and GT2 is within margin of error when benching on LN2. At 2835 core and 2650 mem i got 9493 GPU score At 2835 core and 2629 mem i got 9466 GPU score At 2835 core and 2600 mem i got 9430 GPU score This score is 2695/2727 and 9728 GPU score (with GT1 being much slower). It just doesn't make sense. You telling me it is a valid strategy to aim for bugged scores? I think I still have a bugged score with RX460 I can show...

Not sure what you mean, Stavros score is as expected from those clocks

Ok, I checked my scores. This is obviously bugged GT2, if I were you I would upload backup score. Maybe mods will allow it, but I wouldn't bet on it to have just one score... I have runs at 2835 core and mem at 2600, 2629 and 2650. There is no huge gain in GT2 from pushing just mem...

is this not bugged GT2? FS can cause textures to not render properly when pushing mem, as I'm sure you know. You have more scores consistent with this? I saw it on RX 460 as well...

Lol, i can feel banhammer incoming...

when submitting I select Galax as memory brand, but then I can't select a product. And after submitting, Galax doens't show up. (It still says Galax if I select edit result, it just doesn't show on the submitted score). Let me know if this is a problem, but I don't see how I can fix it, it is most likely hwbot issue...

Sometimes you can get timer error also. Is this allowed? It should be impossible on skylake so it should be a bug in sysinfo...

Software has a FBVDD-limit of +125mV??? Anything above that just reverts back to +125mV the next time you start the software, so I think it doesn't actually set higher...

Good work Luumi!

Not while pushing men also I hope! I'm at 2850 -160, but not that high when pushing mem also... How du you run full pot, I get cracks when going below -160? Edit: oh, and time spy is working fine.

What was wrong with the screenshot, I can not see anything wrong? It's Alvas 3543 right?

I tried the vmem tonight. Didn't have any 20k but used two 10k in serial. Anyway, when I first booted up, vmem kept rising slowly all by itself from 1.5 and somewhere between 1.55-1.6 screen froze. It then gave 0 volts when trying to turn on. Had to remove the vmod to get the card back to life again. Any ideas?

Yeah, I know they contacted me also. So I'm hoping it's not them But they shouldn't ship from Hong Kong...

You already got yours? They ship from Hong Kong right? I just got a message today that something was shipped today from Hong Kong. Let's hope it's galax and not something else... Or else time is running very short...

Nice core freq! I'm stuck at 1500...

Wow, this looks like it will be the best lineup for a comp in a long time. For sure the best I have seen since I started.

No update for me. Chinese holidays should be over now

I really like the list of participants in the wild card comp, so let's do an unofficial list here as well I'm in! (obviously) Who else?

You can see it under settings in validation link. Windowed mode... But maybe you can change exe-properties in windows to run it in window. Don't know if that is possible... Sorry for bugging you, but i just want to make sure.

Ok, how about running windowed mode? It can help to set bclk on the fly for boards that don't have oc keys or oc panel support. It doesn't really affect settings...

@Calathea Bench with internet connection and log in before saving file. Don't know if there are other ways to do it but that worked for me.