Massman
Members-
Posts
20467 -
Joined
-
Last visited
-
Days Won
16
Content Type
Profiles
Forums
Events
Blogs
Everything posted by Massman
-
The official HWBOT DDR3 High-Clock Challenge thread.
Massman replied to Calathea's topic in HWBOT Competitions
Has to be below 4500MHz. 4500.1 > 4500 -
You are right; when we enable points for certain benchmarks there's a more obvious focus on those benchmarks. I think that limiting the amount of benchmarks that receive global points and thus making the choice to give a benchmark more focus will give those who are aiming for the top ranks maybe a bit more time to really push the system in specific benchmarks. I have the feeling we're close to the saturation point where there are too much benchmarks to focus on; adding 10 more could make everything unbalanced.
-
Hm, if I remember correctly I was able to run 2133, but not CL=6. Anyways, here's the new bios for both GD55 and GD65: http://91.121.148.119/downloads/BIOS/E7681IMS.186
-
Same like it's decided now. New benchmark -> no points - quality and security control - community likes it? If both ok => hardware points If turns out it's highly popular and solid => global?
-
Hey all, In Rev4, we will split up the HWBOT benchmark suite in three parts: 'global', 'hardware' and 'beta'. - global = global and hardware points - hardware = only hardware points - beta = no points The idea here is that we will limit the amount of benchmarks you need to run to get a high ranking in the Overclockers League. Diversity is good, but if we add another 10 benchmarks, the ranking will more and more become function of the amount of available time. Therefore, a selection of 10/15 benchmarks (~ like now) will be used for global points. The more benchmarks, the better. Especially when benching for the team, it's nice to have as much benchmarks as possible to grab hardware points. So, we have a 'new' category of benchmarks that only generate hardware points. Over time, it's possible that a highly popular and decent benchmark moves to the global category. The idea here is, for instance, to give global points to 3DMark Vantage Performance and add entry, high and extreme as hardware points. The beta section is to test new benchmarks. If possible, we would like to add some kind of GUI for overclockers to add a new benchmark. That probably won't make it in the first edition of Rev4, but just wanted to throw it into the group. Thoughts, comments, suggestions, ideas ... shoot!
-
The official GIGABYTE's AMD Highest Clock (ever) contest! thread.
Massman replied to MaJ0r's topic in HWBOT Competitions
You mean that 1 submissions? . Just quickly ran through the top-10; only found one old submission. -
I had 53x working on the UD4, IIRC. It just depends on the CPU, I think. Not so much on the board.
-
The official GIGABYTE's AMD Highest Clock (ever) contest! thread.
Massman replied to MaJ0r's topic in HWBOT Competitions
How do you mean? -
MaSell - LANParty UT nF4 SLI-DR Venus - 509.39 MHz Reference Clock
Massman replied to placid's topic in Result Discussions
Holy mozes. -
N34R - Celeron LGA775 360 @ 8242MHz - 8242 mhz CPU-Z
Massman replied to Linuxfan's topic in Result Discussions
Needless to say the user is on vacation -
Sandy Bridge 2500K/2600K Batch and Serial Numbers
Massman replied to Massman's topic in Sandy Bridge (P67/Z68) OC
So far it looks like you'd better stay clear of all the #00xx chips. None of the low numbers hit any high speeds :-/ Number on the black PCB ~ 3600? -
The official HWBOT Country Cup 2010 - stage 3: 3DMark03 thread.
Massman replied to 1Day's topic in HWBOT Competitions
This basically sums it up -
It's also pretty retarded to find out it's Wprime1024M stable at -15°C, but not screenshot stable ...
-
Why? ASUS/Intel promise 6GHz
-
As far as I've heard, it has improved the memory compatibility. I quickly tested V1.7B4 and that bios had really laggy EFI bios. With the 1.8b5 I don't have that. Try it and report your findings Nah, that's Intel's great Sandy Bridge technology Thanks, added!
-
Anyone tested Sandy with LN2 already? I'm just running a couple of tests now and it strikes me that around -50°C I get the same AE error as I get when I clock to high on air. So: 5400 on air -> stable. 5500 on air -> AE 5400 on ln2: -50°C and lower -> AE -46°C -> show OS list, but freeze while loading -40°C -> load into windows Anyone else found this?
-
Gyrock - Core i7 2600K @ 5700.7MHz - 6sec 485ms SuperPi
Massman replied to Massman's topic in Result Discussions
Oh, also thanks for sharing the info of the batch and # of the CPU. It's an example for the community! -
The official HWBOT Country Cup 2010 - stage 3: 3DMark03 thread.
Massman replied to 1Day's topic in HWBOT Competitions
Should be fine now. Any reason no one went for the new Fusion APU? The onboard IGP, the HD 6310, is pretty similar to the HD 4330. That mobility chip can already do 10k easily (http://hwbot.org/community/submission/977131_) ... with overclocking that should've been a nice score. -
The official HWBOT Country Cup 2010 - stage 3: 3DMark03 thread.
Massman replied to 1Day's topic in HWBOT Competitions
Yep. Already changed it in the database. I'm now waiting for the engine to stop being stubborn and change the overall result. -
The official HWBOT Country Cup 2010 - stage 3: 3DMark03 thread.
Massman replied to 1Day's topic in HWBOT Competitions
Yes. If only Intel would be able to use their "insane processing" technology to build a useful website where I can find that information ... -
The official HWBOT Country Cup 2010 - stage 3: 3DMark03 thread.
Massman replied to 1Day's topic in HWBOT Competitions
Changed the IGP of this submission: http://hwbot.org/community/submission/2107068_ First article stated all Core i7 2xxx series have the HD3000 on board; another article stated it's only the K-sku that has the 3000. So, changed it back -sigh-/ -
Gyrock - Core i7 2600K @ 5700.7MHz - 6sec 485ms SuperPi
Massman posted a topic in Result Discussions
Whoah! -
RoccoESA - Core i7 2600K @ 5746.8MHz - 12.87 sec PiFast
Massman replied to Linuxfan's topic in Result Discussions
Iubitel - on itself it doesn't say much, but within a specific FPO/batch it's a good idea to get a CPU close to the golden #