_mat_

That could pose a challenge, because the I guess your fps calculation and the internal one of the x265 encoder can be different (even without skewing), right? The BenchMate integration would fix the timing inside the x265 encoder, no doubt about that. So the value in the encoder would be the correct one afterwards. Any chance we can find a solution together to change that behaviour when the integration is active? Details about that might be better via private message.

But they will have to try A LOT harder with BenchMate. We can't eradicate the problem, but we can raise the bar to a level where it would be less effort to just make the real score. Right now you can download tool "X" and beat nearly every benchmark out there (except the latest 3DMarks). They have raised the bar high enough so you need at least programming skills.

GB itself makes the timer calls, the BenchMate integration just counts the calls and checks that they are not skewed. Intel has nothing to do with that. Maybe they sponsored the deep learning test though, because with the new instructions in Cascade Lake-X they will rock it.

The sum of donations just got boosted to 354 Euro! There was a very big donation from an HWBOT user. Wow, really amazing! Thank you! We are getting close to the 500 Euro barrier, which directly translates to one more year of an actively supported BenchMate! ❤️

BenchMate 0.9.2 should fix any timer errors. If they still occur, please file a bug report with the screenshot showing the run dialog of GB and the error dialog. If something else is not working as expected with BenchMate, but working WITHOUT it, please file a bug report within BenchMate right after the run fails and I will have a look at it.

New update: BenchMate 0.9.2 Last one for today, I promise. Download | Change Log | Donate With the help of @Bilko I've found a bug on Ryzen and Geekbench 5. Read more about it here:

And here is the update: BenchMate 0.9.2 Download | Change Log | Donate The Geekbench 5 scores are also much better now, more than 1000 points for multicore score on my 9900K@5G. That's because I'm not emulating 14 million QPC calls through the driver with HPET. So QPC uses what it is configured to use, but is regularly checked for skewing. That's the same method that is used in CINEBENCH as well as 3DMark03, 05 and 06. On a side note: Don't ever try to enable HPET on modern CPUs and run Geekbench 5. QPC will be awefully slow and your score will tell you. You will effectively bench your HPET timer latency.

I've just encountered a strange synchronization bug on Ryzen with the new Geekbench 5 integration. As I've looked further I realized that instead of using the QueryPerformanceCounter() function about 2000 to 3000 times like in Geekbench 3 and 4, it's used about 14 million times during the same duration. I really don't know what to say other than that's incredibly stupid and obviously completely unnecessary. So there is a contention bug currently showing only on AMD CPUs in BenchMate 0.9.1 + Geekbench 5. I've already fixed it and will upload an update in a few minutes or so.

Thanks for taking the time to reply here, havli. I will look into it. If it can work in a reliable way, I will use the DLL injection method to hijack everything around the x265 executable. A small question: Is the timing shown in the wrapper taken from the executable or does the wrapper do the timing itself (so the times differ)?

Interesting thread title for sure. I was pretty surprised when I clicked on the thread and suddenly read my name. Thanks to your post (and the new update) BenchMate has two new patrons! Thank you, guys! Financially BenchMate is still in a difficult position. I've just paid another yearly license cost of 500 Euros (~ 550 USD) and that's straight out of my pocket. I myself have thought that something like this is dearly needed and that we would at least got the license cost by now. That's sadly not the case. I will be very open about donations, so here is the current standing: One-Time Donations: 108.37 Euro (excl. PayPal fees) Patreon Donations: 43.38 Euro (incl. Patreon fees, excl. payout fees) So we are currently at about 150 Euro (~164 USD).

@Mysticial Sorry for the delay. I was very busy finishing BenchMate 0.9(.1). Yes, either frozen or currently "out of reach". It's still very early for BenchMate, so approaching well-known developers like Futuremark/UL or Geekbench with the new concept would be very risky (also for them). Exactly! Everything we have can be easily broken and I've done this during research for BenchMate. For example all versions of 3DMark and PCMark can be hijacked to run with unnoticed settings like LOD, different resolution and much more. I dug deep into Intel's XTU as well and written a full analysis on its security vulernabilities. For XTU they made some really horrible choices. BenchMate uses different low-level timer facilities like HPET, that are accessed via its own kernel driver (which does much more btw). These low-level timers are then either injected or tracked with BenchMate and correctly verified by multiple time sources (not API functions!). In the end BenchMate does not use any timers that are linked to the bclock/ref clock. How do you detect clock skews in y-cruncher? Which timer functions are you using? The wrapper is written in Java, so it's easily reversable and debuggable. I had a quick look just yet and although it's minimized, it's still very clear what is happening. Sadly, it would be easy to get the encryption key as well. But not as easy as it was with HWBOT Prime and the x265 wrapper - that was a matter of minutes. What I'm trying to say is, that passing data through the wrapper isn't very secure. It would be best to directly grab it from the inner benchmark executable. This way it doesn't matter what language the wrapper is written in, it's just a nice way to configure y-cruncher and display insecure, but eye-catching results. To do this I suggest some kind of one-way protocol to transfer readonly data to BenchMate. That could be done with accesses to files, that don't exist but will be caught by my hooks into the process. As for the timing functions, if you don't want to include BenchMate as a dependency to y-cruncher, they need to be "injected" in some way. Well, maybe DLL injection isn't the worst way to do this and it wouldn't break anything on your side as long as these API calls are happening (any call to QPC for example, and the CreateFile/fopen invocations for beginrun, endrun and result). Exactly! The wrapper is too transparent for this kind of tasks anyway and I guess it's best if only one of us has to struggle with the peculiarities of the HWBOT submission API.

Thank you!

BenchMate 0.9.1 is already here! It adds support for Geekbench 5 and the Big Package bundles it. For more details have check the GB5 thread: Download | Change Log | Donate

Geekbench 5 has landed today. It officially requires Windows 10 (64 bit) for the first time. I've looked into it from a technical standpoint and it doesn't fix anything related to timers or security. It uses QPC and GetSystemTime(), both highly unreliable and easily attackable, and both will skew with bclock/reference clock on Pre-Skylake and all AMD CPUs on Windows 10. The negligence seriously amazes me. BenchMate to the rescue! I've already integrated Geekbench 5 into BenchMate and released a new version: BenchMate 0.9.1 Geekbench 5 is also bundled with the "Big Package", no need to install it. I've also taken the liberty to add Geekbench 5 as a beta benchmark here on HWBOT: Geekbench5 - Single Core: https://hwbot.org/benchmark/geekbench5_-_single_core/ Geekbench5 - Multi Core: https://hwbot.org/benchmark/geekbench5_-_multi_core/ Geekbench5 - Compute: https://hwbot.org/benchmark/geekbench5_-_compute/ You can directly upload into these categories inside BenchMate or by uploading the .hwbot-file manually.

BenchMate 0.9 is here! After six weeks of (absolutely necessary) legwork I'm finally releasing the next major version of my Benchmark Verfication Software. All reported bugs have been fixed, a good part of the benchmark integration rewritten. I also put more effort into supporting Windows 7 and have extensively tested it on multiple platforms. If you like where this is going, spread the word and bench your stuff with BenchMate whenever possible. This is the most secure, reliable and trustworthy option to present your overclocking achievements. ? Download | Change Log | Donate

Spill the gossip! Was @Splave finally banned?

Is somebody actively working to fix this issue? @richba5tard @Leeghoofd

Same for me. I'm a team captain as well. But all pages on HWBOT look like that. Just white where the layout should be.

I'd like to invite all active benchmark developers to discuss integration into BenchMate. If you have any technical questions about BenchMate or the integration, please feel free to ask here. In general there are two ways of integration: 1) External Integration A DLL is injected into the benchmark's process and all of its child processes. Several WIN32 and CRT functions are hooked as needed to inject accurate timing and file integrity hashing as well as result capturing. 2) SDK integration One of the next releases will bring native BenchMate integration. The SDK will be available for C/C++ first as a static library. There will be several classes available to help you use BenchMate's features in your benchmark. Reliable timer functions, secure string classes, installation verification, file integrity hashing and much more. Additionally, the SDK integration lets BenchMate know when a run is started, ended or canceled and securely transfer results to the client for validation. No DLL injection is necessary here. Let's get this going! @Mysticial @havli

Please use the following URL in the news, it's the new, permanent place to get the latest version: https://benchmate.org

Exactly. There is also a GPUPI support thread, which would have been a better place to ask this. You're sadly not using BenchMate judging by your screen.

From what I can gather from the screen, the service executable might be missing. Please have a look at your BenchMate installation path and see if service32.exe is available in the bin subdirectory. You can also close the application and submit a bug report by starting bugreport.exe.

Thanks will have a look.

The problem seems to be related to NVAPI or AMD AGS, both are GPU driver APIs. Please submit a bug report right after the problem occurs. Just press ok and let the application close. Go to the BenchMate directory and execute bugreport.exe. Thanks!

BenchMate can't link to any competition, HWBOT doesn't support that via its submission API. Regarding the custom resolution, that's an NVIDIA feature that obviously reports the wrong parameters to the WIN32 API functions. It's neither a BenchMate nor a Windows 10 fault, that one's all on NVIDIA. I'll see if I find a way around. BenchMate already uses NVAPI to detect special NVIDIA features like SLI. There will surely be a way to detect this, but don't count on it soon. My list is pretty long.