_mat_

This is not a valid result with BenchMate. You need to start wPrime from BenchMate's launchpad, make a score and save it to a screenshot with the "Save Result" button. If you have any questions, please let me know.

Although I don't like to be told that I'm an a$$hole, it's much more important to make BenchMate as good as possible. He had good points, but a poor choice of words. A little respect goes a long way though. We're a community for christ sakes, let's act like one.

@MrGenius Thanks to your bug reports I could fix two problems. The QPC Skew "bug" led to an improved auto detection algorithm to restrict QPC usage in benchmarks depending on the hardware platform and OS used. Additionally I've added the possibility to configure the Timer Emulation used for benchmarks. This is only available for all CINEBENCH and 3DMark versions as they depend on very fast timer facilities to avoid a negative impact on performance. Please check the changelog for more details: https://benchmate.org/changelog.html (see version 0.10.4) The skewing of QPC on Windows 7 is actually not a bug! All Intel CPUs below Skylake will show wrong benchmark results if QPC is used for timing and QPC itself just wraps the CPU's TSC. The assumption that all is safe on Windows 7 was never justified. We are just lucky that most benches are so old, that they don't use QPC. Unfortunately that is not true for Geekbench 3, Geekbench 4 and Geekbench 5. Or for example the new Intel XTU 6.5. All of these benchmarks can NOT be benched on Pre-Skylake platforms on Windows 7. Same goes for AMD of course. Regarding your statement on Geekbench 5, I've set these categories back to "Alpha" status, which hides them from HWBOT's benchmark overview page. There were only a handful of results and the whole category depends on the automatic submission by BenchMate, which is no longer supported.

BenchMate 0.10.5 is available for download. ? This is probably the last release for 2019 as I am as exhausted as one can be. It was a good year though, but as unhealthy as an out-of-control drug addiction. ? I haven't announced the last two minor releases to spare you the hassle of too many downloads. But this one is very close to what I had in mind for 0.10 and fixes all known bugs, so please redownload for the best experience. Download: https://benchmate.org Changelog: https://benchmate.org/changelog.html PayPal: https://bit.ly/2LQgc5S Patreon: https://www.patreon.com/benchmate

It's not my vendetta. It could be a pipe dream though, but I like to call it a better future. As you please, your opinion is still welcome. Are we talking latest version, BenchMate 0.10.2? It is hard to say anything without a bug report. Please submit one so I can work on it. Otherwise this is not really of much use. I can't reproduce anything you say with the latest version on any of my available test platforms. The number of submission out there in the field also tells quite a different story. And please ask anybody, I take every bug report as serious as possible and try to fix bugs as quickly as my time allows (this is still a hobby). Btw, it is NOT MANDATORY to use BenchMate on HWBOT. If you don't like it, don't use it. Use Windows 7, you'll be fine.

HWBOT can and will decide for itself what's best. My hands are tied with GB and not for the lack of trying. It was all already in there, working and as stable as it can be directly securing the inner benchmark executable and parsing its result. The problem is that whatever this goes next, if GB stays active it will always fall back to BenchMate being not able to handle it and therefore less useful as a solution to unify benchmarking. I doubt that GB decides whether the bot can be successful or not. There are many very worthwhile benchmarks out there waiting to be tortured with developers happy to see them in good use and support them long-term. I know because GPUPI has been one of my happy places since it got added here. GB is officially not one of these benchmarks (decided by the dev itself) and because of that it will end up the same having its points removed sooner or later. It will just hurt much more if it is later and without an announced transition period.

Yes. HWBOT has not managed yet to integrate BenchMate correctly, because all legacy benches are apparently hand-written and do not support the submisssion API. You can use BenchMate 0.9.3 and manually add GB. BenchMate 0.10+ does not support GB at all, as I won't get my ass sued over a benchmark that is developed by somebody who doesn't care about result validity or security to begin with. If you do use an old BenchMate version, I recommend you run it on a different OS install. Mixing two BenchMate versions with bluescreens and instable processes will at some point result in some broken pieces of the old version lying around, that the new version can't remove. You will have to manually remove the BenchMate services then to be able to start the other version. I'm looking forward to the day where Leeghoofd comes through with his promise to remove GB's points. After all this shit this has put me through, I have to answer questions like these on a daily basis. Please, enough is enough.

Is that 1.2 million uniques per year measured with Google Analytics as users? Or webstats from the server?

Splave doing all the heavy lifting to keep Intel in the 12 core race. Amazing work!

Already a bugfix release: BenchMate 0.10.2 Please redownload and use this version. It fixes an important bug where perfectly fine scores were blocked. Download: https://benchmate.org/?v0.10.2 Changelog: https://benchmate.org/changelog.html?v0.10.2

What does it do? I've wondered about that for some time now.

BenchMate 0.10 is finally here! New benchmarks, Splave's ColdbugMate, benchmark integration completely rewritten, full Windows 7 compatibility, an auto-updater, fancier result screenshots, 3DMark03/05/06 support with LOD, GODLOD, Triple Buffering, ... You will love it, I promise. There is over 3 months of full-time work in this release. I'm talking 12 hour days, next to no weekends, girlfriend pissed - the whole deal. The changelog has 53 (!) lines solely dedicated to new features, improvements and bugfixes. If you like my work, please consider to donate via PayPal or become a Patreon. Thank you! ? Don't bench unprotected. Download: https://benchmate.org/?v0.10.1 Changelog: https://benchmate.org/changelog.html?v0.10.1 Donate: https://bit.ly/2LQgc5S Patreon: https://www.patreon.com/benchmate

And I'm going to spam the benchmark list as long as it takes to make the BenchMate integration happening! (I hope so too)

This the right folder, but the prerelease version of BM 0.10 does not create .hwbot files yet for wPrime and 7-Zip. Tomorrow the new version will officially launch and I have already added the "wPrime * with BenchMate" categories and the 7-Zip category as well as 3DMark03, 05 and 06 as beta benchmarks to HWBOT. This version will produce . hwbot files, which you can upload (or submit inside the client).

Launch imminent. This time for real, no prerelease.

Crazy good! This is a great example why BenchMate should be used instead of just GPUPI + enabling HPET. The latter will perform worse because HPET is slow on these HCC chips and enabling it system-wide has a serious impact on overall benchmark performance. BenchMate just injects HPET into GPUPI, so only a few calls for time measurement inside the benchmark are using HPET while the system timer interrupt is still based on the faster LAPIC PM timer. This is how it's done! Edit: Love the Wahaha!.exe on the desktop. ?

BenchMate monitors the benchmark process and it has very strict rules on what data needs to be available and valid to show a score as successfully verified. If the benchmark process is unstable, it will most definitely crash. BenchMate recognizes that and will not let you save any result (from a process that is not even there anymore). If the benchmark doesn't crash but shows weird behaviour, there is a good chance this will show up somewhere in BenchMate's result dialog. Like for example a benchmark run that is cut short, but the benchmark itself doesn't realize that and still shows a result (very rare, but has happened in CB R15 for example). Due to the fact that we now have so much more data for this run than any screenshot could possibly show, the moderators can make a better decision if this was valid or not. A run cut short for example will show a very different runtime and less timer calls for the whole run. This is data we never had before and we can use it for good.

The driver is not signed by Microsoft yet, because it's in beta stage. So on certain preinstalled Windows installations, the driver can't be started. The BenchMate 0.10 prerelease version already has a signed driver, so that should work out of the box: https://www.overclockers.at/downloads/projects/BenchMate 0.10-big-v7.exe Sorry for any inconveniences! Be sure to let me know if you encounter any other difficulties. Any Feedback appreciated as well.

Aquamark support is currently not planned, although very much possible, so not off the table or something. But I will try to focus on the most popular benchmarks first. In general old wrappers are replaced by BenchMate's integration. This is a whole new level of wrapping because I'm not just launching a benchmark process, but I'm actually in it and replace several Windows functionality with fixed, more robust and secure alternatives. For example all timer calls a benchmark uses are either emulated securely by the driver or at least tracked and its measurements compared to several other timestamps. That's something the Aquamark wrapper can't do, it is more like a result submitter with some system setting checks.

It's not mandatory. If you don't like BenchMate or the workflow, just use Windows XP or 7. In any case, you need to follow the rules of HWBOT to participate. The real problem lies in the more and more complicated rulebook, that's necessary to keep the playing field fair and square. That's what BenchMate is here for. It makes your life as a bencher easier, lets you focus on the hardware and cooling (the fun part) and deploys the same ruleset to anybody who is participating independent on the OS used. This might sound easy, but it's actually VERY hard to do. But you don't need to care about that, just use it (or not and deal with the rules yourself like OS choice, enabling HPET, ...). As for wrapping legacy benchmarks, they are profiting the most from it. BenchMate fixes multiple bugs and inconveniences as well as ensure that they can be run on the latest versions of Windows. That's something an actively developed benchmark doesn't need, if it gets enough attention from the developer. In a way you can see the BenchMate integration of legacy benchmarks as a form of active development to keep them up-to-date. Any wishes or suggestions?

Your score is sadly not allowed as defined by HWBOT's rules. Please use BenchMate or Windows 7 + CPU-Z as stated by the rules. https://benchmate.org

If I remember this correctly from work on integrating wPrime in BenchMate, it uses the WIN32 API functions GetTickCount() and GetLocalTime() to measure time. The resulting timestamps are compared and if they differ too much, you'll get this error message. Both functions rely on the RTC to return the current time. The difference is that GetLocalTime() does depend on some synchronization to avoid time drifting, so the clock in the task bar always shows the correct time. If the PC is connected to the internet, the synchronization might come from a remote time server. If that's the case, cut if off from the web. But there are is another anti-drifting measurement available in Windows since forever. It's called "System Time Adjustment" and it can be disabled by code. A quick search showed up the following tool, although I have no clue if the executable works on XP (the technique itself does of course): https://github.com/jschicht/SystemTimeAdjustment

I'm currently rewriting a huge and important chunk of the benchmark integration code, so that future integrations will be much less painful, need less dependencies and therefor be more stable. With that handled I will finish the rewrite of the integration of 3DMark03/05/06, that uses the before-mentioned improvements as well as way better detection of GPU driver options like version and SLI/Crossfire. It would have already been done, but I had to work for a living in the last couple of days so that added to the delay. Development will go into full throttle tomorrow again, so give a few days and it will be done. If anybody needs wPrime integration for a world record that can't wait, let me know and I hook you up.

The Splave himself designed it. ? Will be available for everyone with the upcoming BenchMate release.

This isn't related to BenchMate. I didn't think I actually had to say that out loud. There is actually nothing I can do, the benchmark itself has to ensure that the work is done. I can only provide a safe surrounding like anti-tampering of files, processes and threads as well as unskewed timers. Btw: Real men never bench unprotected. You can easily catch something.