Leeghoofd

Plz turn on HPET!

mmmmmm interesting :)

its all about the Thermalright...

Checked with some old and new gen of Australian OCers, nobody seems to know this mystery OCer...

They have removed them, while investigating. Same principle as we apply at HWBot, removed till they check out.

if you look at the gpu clocks it detected probably the HD4600

UL removed the current scores till they have more proof. I'm checking with the Aussie OC community if they have any idea who this elite Ocer is. I emailed Escapee to provide proof via screenshot/setup rig by submitting here at HWBot.

Well what a coincidence. Me. Luumi &, Stavros were talking bout this guy this week. Why post there, but not at HWBot. I don't think it's our mutual friend, but him as well is playing his typical game. Luumi would contact Pasi from UL to find out who this Aussie is. So hopefully we will have more news soon...

Plz re-run with HPET on as stated in the competition rules

missing screenshot

love that setup!

monster CPU, time to trash the ranking!

Way to go old aged pensioner

Great comeback!!

This will be an eternal debate and to draw a line is impossible as you can't define it all in a rule set. Let alone control it. Take eg your PCmark05 benchmark. It was designed at a specific period for a specific available hardware/software set. Issue today is that with many of the 2D legacy benchmarks is that they do not include all the required software in their benchmark. For PCMark05 you were required to install seperately the Media encoder. So looking at the laid down rules and your software OC mindset: you can't change a dll or such inside the benchmark folder, but anywhere else it is allowed. So if an OCer 10 years later installs windows 7 and starts spending hours/days looking for upgraded media encoders that support eg more than 6 threads you are fine with it. Or that one finds a tool that can remove the 6 core thread limit in the foreseen Media Encoder and raise it to eg 12... You can call that overclocking, I failed to see it back then and even more now. So what happened, Christian approved & shared these "tweaks" and YoungPro was officially nominated as super mod specifically for PCMark05. Software gurus like Glucovio and such found other ways to boost eg.the txt file test, browser tests,... turning PCMark05 into a geek software battle. Nothing to do anymore with pushing hardware clocks, but analyzing and "optimizing" the benchmark. Yes you can cover your actions by: I don't make the benchmark believe it is running faster, it actually is running faster. But that was not how the benchmark was developed was it? Ask yourself this simple question: is it due to the fact that Futuremark didn't make it secure enough or thanks to lets call it the "creativity of the OCer" that PCMark05 is now labelled as a crappy, buggy benchmark? And that the effort all those people that enjoyed benching it out of the box has become bointless. Similar as what happened now, beating LN2ed scores with far less clocked setups. That because a few have an edge due to having a programmer background and that they stay within the never ever perfect rules set. The bottom line is you can't define or draw a perfect line within the rules. The easiest simple line is the ethics and moral of the overclocker. Ask yourself: Is it hard to just install the operating system, tune it by removing abundant software you don't need, install the benchmark and see how it reacts to core/uncore/mem speed and timings? What you do in the bios or such that requires skill/expertise and I know it is the thing especially for the legacy stuff. Nowadays the knowledge/expertise of the OCers, the abundant Bios settings, the cooling gear and such are at a far higher level than it was ever before. Therefore I fail to see that we need to install eg a 2015 software into a 2001 OS and to claim: hey mum look how good I am. I thrashed the global first with 500MHz less. Does that feel right to you? If it does, you will never ever grasp my point of view and we can debate endlessly. You have to think, if we continuously allow this too happen and repeat the decisions of the past, we might end up in 2022 with a truely secured benchmark suite, by tools like BenchMate. Is that what everyone wants here? no more XP support? Limited to 12 benchmarks? Some that might not even run on older hardware? Many specifically all look at it as one benchmark, you have to look at it from a wider angle. Don't we all want to battle with the same tools and be competive. Or you prefer being Indiana Jones and just shoot the guy with the swords. For me the only way to demotivate the software tinkering and that the database remains sort of intact is to remove the overkill scores and remove the global points from Wprime. As stated already so many times before, rules are rules. Rules will never be perfect, people will bend them, break them and will, in the long run spoil the fun for others. Again our own acts will lead to an abundant and probably incomprehensible rules set, making it so hard on newcomers to grasp it all. Some already give up as they have to open 2 CPUZ tabs. Imagine they have to make a distinction between this Dll can or can't be used... The concept of the upcoming HWBot version is to simplify things so it will be fun again and doesn't require an engineering degree before starting to push your hardware. It is up to you as an individual to make that work or not...

Like mentioned on discord it should have been available, but there were some small hickups Matt had to adjust. So at the moment it is still only available for Patreon contributors.

Pm'ed the user to resub and provide a proper verification screenie

Impressive!

Ow it's that time of the year again... wonder who will breach 2 secs

Check out how a verification screenshot is required to look Sean in the example below. You need to add CPUZ tab for CPU and one for Memory (mobo and SPD tab are optional) Also for Vermeer and Win10 , benchmate benchmarking tool is mandatory to check for RTC bug. Benchmark Rules can be read here

https://www.3dmark.com/pcm10eb/37481, HWBot link issue, added to the buglist

wrong benchmark category= CB2003 is not the same as CB23. Also check out the rules: BenchMate is mandatory for AMD and Win10, grab it at benchmate.org

Verification requires 2 CPUZ tabs: one for CPU , one for memory. GPUZ is required for the graphics card

Use the competition background plz

plz use competition background