[Sammelthread] Sockel 939 / 940 / 754 - Thread

[WinstonChurchill]

4000+ San Diego

 

[Sparksnl]

This one might scale well on cold. One of my FX-55 is BG as well.

 

[WinstonChurchill]

This one might scale well on cold. One of my FX-55 is BG as well.

This is my old FX57. It reached 4GHz, but I have a sacred rule: never use a multiplier higher than x15

This one had a CB -81°.

 

[Sparksnl]

I am not sure why you won't use more then multi 15x. Because that would limit you hugely with max fsb which gets less with more cold. With a higher multi it will do better speeds.

 

[WinstonChurchill]

I am not sure why you won't use more then multi 15x. Because that would limit you hugely with max fsb which gets less with more cold. With a higher multi it will do better speeds.

Because I'm from the old school of OPB 🤗

 

[WinstonChurchill]

20 years 🙈

 

[Sparksnl]

Because I'm from the old school of OPB 🤗

QPB as Quad Pumped Bus?

I am more one of those who finds out (after years) that stock settings on a motherboard were always defective. And since I OC from the start…

 

[Tzk]

Probably OPB as in OnePageBook, the overlocker who at some point got banned from XS?

 

[WinstonChurchill]

Probably OPB as in OnePageBook, the overlocker who at some point got banned from XS?

Many years have passed, and some people know about the bad relationship between Fugger and OPB. As was typical, Fugger used his "black hand" on many occasions to discredit OPB’s results, using his influence. This happened in cases like his results with 3k06 or PcMark. People asked OPB how he did it, but he never wanted to publicly explain his tweaking process—only to please the man with the black hand. He was banned from HWBOT and insulted by some, since, because he didn't explain how he achieved his results, they labeled him a cheater.

The OCX team respects OPB decision; his long-standing work in tweaking matters remained solely within the team
For example, at the "Campus Party Valencia" event in 2010 and 2011, Massman, K404, and Joe_cool, No_name, etc... were invited. Several world records were achieved, such as in PcMark, using OPB's famous tweaks. It was verified that there was nothing illegal involved.

As of today, many former key members of Team OCX are now part of other teams, using the legacy of tweaks from Team OCX. They haven't received any warnings regarding their results.

OPB was one of the leading figures during those years, and he left us a valuable legacy of his knowledge

 

[Tzk]

I was (and still am) undecided between "he did cheat" and "he found the ultimate tweaks". I know that OCX had for example a very special windows image back then. And probably a lot of tweaks for the various benchmarks. Sadly OPB didn't want to disclose what he did. Neither in public (understandable) nor to an unrelated third party. Would've helped his case...

 

[Antinomy]

It's a very gray area and always was. Some 3DMark and many PCMark alterations were obvious cheats like repacking texture archives, changing benchmark DLLs and so on. But some fall within the "general tweak" when a certain technique doesn't speed up only the benchmark but the system as a whole and other software too (like caching, priority, drivers).
This is why I don't like the ban of wPrime dll tweak - it's an official dll and you can change it officially by using different OS versions. Why not allow to change only the dll? Pretty much like changing DirectX version or driver or Java runtime version (legit tweak back in HWBot Prime times).
OCX had some nice tools like Spi tweaker and tutorials. Too bad we can't share some things without the risk of being considered a cheat.
P.S. how I love the rev. 2 HWBot design. More than any else.

 

[Tzk]

What i don't like about this specific tweak and its ban is the fact that some old results may (or may not) use the Wprime DLL tweak. So some results are unreachable without "cheating". I'd also preferred that tweak to stay allowed and an official note on the benchmark page how that tweak works and how you apply it. So it's common knowledge and basically anyone can and will use it in the future.

 

[Sparksnl]

Interesting stuff. Although I was one of the earlier to register on HWBot but found AMDMB to be the leading site back then. After a while it became PCPER and some time later HWBot got more popular, but in those times I lost interest for OC for a while. I missed out on things like this because of that.

 

[WinstonChurchill]

Ich habe vor vielen Jahren mit dem OC aufgehört. Wenn es der Radsport zulässt (denn dieser hat in meinem Privatleben oberste Priorität), probiere ich hin und wieder etwas Hardware aus, die ich noch nicht getestet habe.
Ich habe viel zu viele Dinge, die noch ungetestet sind. Das Schlimmste ist, dass ich keine Zeit habe

Xevipiu Alias on Instagram: "La colecció més gran de SS - Cascade del món ( 1, 2 i 3 stage ) #overclocking #hwbot #intel #aorus_españa"

6 likes, 0 comments - xevipiu on October 24, 2024: "La colecció més gran de SS - Cascade del món ( 1, 2 i 3 stage ) #overclocking #hwbot #intel #aorus_españa".

www.instagram.com

 

[WinstonChurchill]

Asus A8N32-SLi, maximale FSB-Grenze bei 274fsb, stabiler Betrieb bis 270fsb

 

[McZonk]

Habe endlich mal Zeit gefunden mich durch ein paar 3 GHz Chips zu binnen. Test war auf Daily ausgerichtet und hatte das Herausfinden der minimalen Spannung für 3 GHz unter identischen Bedingungen auf gemeinsamen Nenner, das heißt 300 × 10er Multi, bei mindestens 15 Minuten Prime95 zum Ziel. [Angegeben sind jeweils die von ITE Smartguardian bzw. CPU-Z ausgelesenen Spannungswerte - die eingestellten BIOS-Werte liegen idR 25 mV höher].

Ein weiterer brauchbarer 4000er Sandi war dabei (ich hatte ihn bisher irgendwie gar nicht auf dem Schirm), aber an den goldenen Toledo mit deutlich unter 1,3 Volt kommt halt nix dran - Long live the King!

Was mir noch einfällt: Steppings sind wirklich nur grobe Indikatoren: Ich habe noch einen identischen LCBQE 0722XPMW (ein paar Seriennummern entfernt), der die 3 GHz nicht mal bei 1,5 Volt im BIOS primestable packt...

 

[WinstonChurchill]

Ich habe das BIOS von Version F2 auf F11 aktualisiert. Ergebnis: SATA-Fehler, das System hängt sich nach dem POST-Bildschirm auf

 

[digitalbath]

Ich habe das BIOS von Version F2 auf F11 aktualisiert. Ergebnis: SATA-Fehler, das System hängt sich nach dem POST-Bildschirm auf

Gigabyte hat auch noch den BIOS Chip verlötet.
Postet es ohne SATA? Da ist bestimmt eine falsche firmware für SATA drauf.