Massman

Latest query: 5964 results. Still the same unoptimized query. Current standing: Average MHz | # unique overclockers | mainboard 5453 | 21 | P8P67 Evo 5430 | 51 | Maximus IV Extreme 5399 | 23 | P8P67 5397 | 61 | P67A-UD7 5394 | 16 | TP67XE 5382 | 10 | P67A-UD7 5358 | 23 | P67A-UD5 5356 | 54 | P8P67 Pro 5325 | 43 | P67A-GD65 5322 | 29 | P67A-UD4 5309 | 12 | P67A-GD55 5297 | 49 | P8P67 Deluxe Current standing: Average MHz | # unique overclockers | mainboard 1028 | 11 | P8P67 Evo 1020 | 10 | TP67XE 1018 | 30 | Maximus IV Extreme 1009 | 5 | P67A-UD7 1005 | 37 | P67A-UD7 994 | 13 | P67A-UD5 993 | 32 | P8P67 Pro 968 | 34 | P8P67 Deluxe 954 | 23 | P67A-UD4 942 | 28 | P67A-GD65 908 | 5 | P67A-UD3P 899 | 6 | P67A-GD55 887 | 13 | P8P67

Uploaded to HWBOT server. Thanks TASOS and Stasio! - P8P67 (1305): http://91.121.148.119/downloads/BIOS/P8P67-ASUS-1305.ROM - P8P67 Evo (1305): http://91.121.148.119/downloads/BIOS/P8P67-EVO-ASUS-1305.ROM - P8P67 Deluxe (1305): http://91.121.148.119/downloads/BIOS/P8P67-DELUXE-ASUS-1305.ROM - P8P67 Pro (1305): http://91.121.148.119/downloads/BIOS/P8P67-PRO-ASUS-1305.ROM - Sabertooth P67 (1305): http://91.121.148.119/downloads/BIOS/SABERTOOTH-P67-ASUS-1305.ROM

Yes. 6C+HT = 6C

Quit living in the past, Marc. Seriously ... I don't even get the humorous value of that post. Looks more like a direct personal attack, but pretty much 2 years too late.

H_d_

Just fixed the link for the P8P67-M

Oh, right! Thanks for the heads up.

Ooh! :-)

733MB of P67 BIOS - P8P67 WS Revolution (1007): http://91.121.148.119/downloads/BIOS/P8P67-WS-REVOLUTION-ASUS-1007-SLP.rom - P8P67-M (0503): http://91.121.148.119/downloads/BIOS/P8P67-M-ASUS-0503.ROM - P8P67-M Pro (0601): http://91.121.148.119/downloads/BIOS/P8P67-M-PRO-ASUS-0601.ROM

Thanks to TASOS and Stasio! - P8P67 (1302): http://91.121.148.119/downloads/BIOS/P8P67-ASUS-1302.ROM - P8P67 Evo (1302): http://91.121.148.119/downloads/BIOS/P8P67-EVO-ASUS-1302.ROM - P8P67 Deluxe (1302): http://91.121.148.119/downloads/BIOS/P8P67-DELUXE-ASUS-1302.ROM - P8P67 Le (1003): http://91.121.148.119/downloads/BIOS/P8P67-LE-ASUS-1003.ROM - P8P67 Pro (1302): http://91.121.148.119/downloads/BIOS/P8P67-PRO-ASUS-1302.ROM

Updated! Nice testing all. Linux: hope you find a golden one soon

Not always, the technical specifications need to match pretty well. Just asked W1zzard about the die size detection mechanism of GPU-Z and, as Sam already mentioned, the die size is indeed function of the detected device_id. This meaning: you can flash away the 55nm and turn it into a 65nm. In other words: GPU-Z does not allow a clear distinction between GTX and GTX+.

So, 9800GTX+ was supposed to be die shrink + clock increase, but manufacturers named their products GTX+ if they just had the clock increase? Haha!

Sounds like an excellent plan!

Thanks Oanvoanc! Batch L051B863 looks quite promising. Although this is just one result, that first result being 5.5G is reason enough to try other samples of that batch.

Fyi, for those who are wondering about the starting time of each stage. Since this is a WW contest, we've done it like this: Stage 1: 00.00h CET Stage 2: 06.00h CET Stage 3: 12.00h CET Stage 4: 18.00h CET Oh, that would be cool! Just edit the score with the new screenshot.

Background: http://hwbot.org/blog/wp-content//desk3.jpg

I wouldn't be completely against the idea. Whatever the opinion of the crowd is, is my opinion . //edit: threw it on twitter, maybe we can have more opinions on this matter.

Trying to get ahold of the background. Sorry for this! You won't, this is our problem.

The merge has taken place. I'll close this thread. If anything comes up in the future, Dejo or the OCForums team captain are welcome to post here. Reference - thread over at overclockers.com: http://www.overclockers.com/forums/showthread.php?t=668746

Thanks for the input guys! Binning Sandy Bridge is extremely easy. - use HS fan with easy mounting - set Vcore to 1.55V - disable HT and 2 cores (to not make it overheat with crappy HSF) - increase multiplier You just need to see the windows OS options, not actually boot into windows. If your CPU can show the different OS options, stability will just be function of Vcore and temperature. If it doesn't show the OS options, you will never get it stable anyways, so you might as well ditch the CPU. Usually, it takes about 5 minutes to see if the CPU is good or not. With some CPUs, you do have the issue that some multiplier is better than the other for stability. For instance, my current CPU can boot at 51x MAX (~ 5145MHz). When trying to run near this max speed, I have to use 49x instead of 50x multiplier because it's a lot more stable. But, that's something you don't need to test. With BCLK adjustments, you'll never get 5200MHz going or so. Multiplier binning is the best way.

Thanks! - P67A-UD3 (F7a): http://91.121.148.119/downloads/BIOS/p67aud3.f7a

I didn't code it either . Must be a bug. The 'no-point' option hasn't been updated along with the different ways to calculate points, I think. We won't fix this bug for the Rev3 as Rev4 will be completely different again (database-wise). I just removed the points manually now.

Another M4E bios - Maximus IV Extreme (1090): http://91.121.148.119/downloads/BIOS/MaximusIV-Extreme-ASUS-1090.ROM

As far as I know, it's not possible to identify a unique hardware sample. You can detect the core id, which is the same for all cores, and bios id to the level of bios version, IIRC, but not bios chip #. A while ago, Jarnis_FM posted on the forums that they can detect unique hardware (for instance for the LOC incident), but that was not based on a unique VGA card but based on other similarities. In short: as far as I know, there is no method to differentiate cards on a sample level.