Strunkenbold

No offense, but I dont think that a laptop can beat LN2 scores. There is probably just a mistake with hardware detection. Also you cant submit in two hardware categorys with the same hardware like you did in the Mobile Intel HD Graphics 4600 categorgy.

Looks more like a allowed tweak for me. Basically its the same like tesselation. This little trick really boosts score by 200-250points, but you cant submit this to Futuremark. Maybe someone of the mods could make a clear statement here.

1.0.1 really gives better physics score. I just found time and tested this yesterday. But for me, influence on combined score is very low. (actually this is now lower) Anyway I cant match your score with 100Mhz+ on the cores.

Ticket ID: 1928 Priority: Low As the title says, there are GDDR3 128bit, GDDR3 64bit and GDDR5 variants on the market. So there should be separate category\'s for each.\r\nGDDR3 64bit\r\nGDDR5

Insane score of the CT! Is there a trick or is this bugged?

thx guys! I think mobo can go higher but cpu hits is wall.

Congrats to XTREME OC Team Bulgaria, though Im very sad that you took our 5th place, when Im looking at your results I can only say that you really deserve it and it would be a pity if you cant compete for the champion. Outstanding AMD results, keep it up!

I remember that things worked with country cup. Shouldnt that competition which match my hardware most appear first? (instead of not at all) Attached a screenshot...

I bet those little mosfets were crying.... Great run, now lets see what the Intel dudes doing.

Ok, but still there is a bug with OC4Dodge. Since this competition appeared, competition matcher always wants to match your sub to OC4Dodge, regardless of the used benchmark. You didnt need to alter hwbot prime and add every sub by hand if users could do this on their own if they only would get the right competition proposed, which should be actually no problem as this worked before without any problem.

Nice Cache if this is able to handle 120Mhz FSB...

Any update to this? This is really a critical problem as every score has to be linked manually to the cup.

I already did some mods. Tried to raise Vnb up to 1,75V and watercooled nb. Didnt help. Maybe I really need some cold to pass 315Mhz fsb. But first wanted to compare another board before I buy some dice. thx guys anyway You really need to mod ASUS boards? Didnt have one but:

Thx But looks like mobo has reached its max. Atleast a Mobile Pentium 4 walls exactly the same at 315-317Mhz fsb.

The problem with that was not that huge list in general but for some reason competition suggestion no longer matches the used hardware of the submitted result. i.e. A HWBot Prime result gets proposal to submit in: OC4DOGE - 3DMark Fire Strike Tahiti & GK104 OC4DOGE - Intel SuperPi 32M @ <4.38 GHz Therefore especial people doing submissions with a mobile cant link them to TeamCup. btw could you move this result: http://hwbot.org/submission/2620844_

Also see: http://forum.hwbot.org/showthread.php?t=103058

Antinomy was right...

Cant delete: http://hwbot.org/submission/2324588_strunkenbold_ucbench_2011_pentium_4_3.0_ghz_prescott_91.4_mpt_score I hope the rest is ok.

Looking at the used Kernel, isnt this a Galaxy S4?

Based on available shaders and pcb, isnt this a r7 250?

There is one simple answer: You just can submit XTU scores with Sandy Bridge and up. Everything below Sandy Bridge just generates a score but cant be uploaded to HWbot. Stupid? Yes, 100% agree....

No CPU-Z screen and wrong category...

Way to go! Seems like the last "secret" of this competition is lifted now. Very nice modding!

huh that score is really some years old now. Cant say which voltage was exactly responsible. You probably just have to try and find out. Just make sure you change thermal paste on nb and always have some fan blowing at the cooler.

There seems to be some db issues. 1) Submissions with i3 3110m get constantly linked to i3 330m. This especially happens with XTU an HWBot Prime subs. 2) There is something wrong with the speed of the P3 Celeron 566Mhz, as the db says its default clock is 533Mhz but obviously should be 566Mhz.