_mat_

@Leeghoofd @mllrkllr88 David found a method to create verified results of a 7980XE @9 GHz with BenchMate 0.8.1. As these very early versions are severely worse in terms of security and bugs, I would advise to only allow results made with BenchMate 0.9.3 and greater. (They are used 99% of the time anyway.)

Latest driver release is R302 from 2012. Also no Windows 10 support. It will work with the next release, but that will take at least another two weeks or so. We are working very hard on it.

What GPU are you currently using?

Literally one click away from a world record on air. Cheat Engine ❤️

There is without a doubt a solution for that. Please send me the log files (whole BM/logs directory as zip) so I can look into it. You can also use the BugReport.exe tool in BM's directory if the system is online. You are ditching a new take on benchmarking because of a single bug of an early beta version. If any software developer would stop working on something because of that, the world would not have a single software product. You really have to distinguish between flaws in the concept and the implementation. Ah, here wo go again. Screenshots are so great, manual input of results is really efficient, nobody is cheating, the future of overclocking is bright! I've heard it all before and watched it quietly while supporting GPUPI for many years here. HWBOT is already bending backwards to manage the situation with the tools at hand. Platform/OS matrix with has to manually checked by the mods against timer skewing? Seasonal ranking needs a text editor open or a certain version of CPU-Z? Beginner's scores are often removed due to the complexity? Benchmarks and results have to be removed when a flaw is found (if it can't be verified that it's valid, it has to be assumed it's not)? When will we realize that we at least need an alternative that's being worked on in parallel to tackle these problems FOR THE FUTURE. I'm not saying that BenchMate needs to be mandatory right now (or maybe ever) here on the bot. But I am saying that it's unwise to not explore (over-zealous) solutions, that would allow benchmarking and overclocking to reinvent itself.

I do understand it. Soon every benchmark will have a result database that is much better than the Geekbench database. Better integrity/quality, better hardware detection, nice graphs, screenshots. And it costs ... nothing. ❤️

Be my guest. A bounty to take down BenchMate's security is something I always wanted to do. It's an early beta version. You can contribute by posting your problems so I can fix them. This is pretty normal, especially with something that difficult like BenchMate. Everything that is not security-related is logged to file. Check the debug log path inside the BenchMate directory. It is well known that this doesn't work. You can thank the Geekbench dev for that, because 0.9 wouldn't even be available for download if it wasn't for his legal threat. But I didn't want to let benchers down, so I kept it online if you really need it. It was never meant to be used in parallel with other versions, so that is by design. That said, the next version already supports to run different versions of BenchMate at once. This sounds like you are mixing BenchMate 0.9 and 0.10. Don't do that! Use another clean OS to keep them separate for now. No. There is next to no impact during a run other than measuring sensors (like GPUPI does). This was optimized for the next release as well to have even less impact for the work that is done. What happened with pretesting on air? Things should work nicely before you start with cold. This is the same process as it is with any benchmark, tweak, driver or OS install in general. I'm always happy to help as quickly as possible. Sometimes BenchMate is not even the issue, but that's fine with me. I help anyways. Please do that. If it helps competitive benching, then it's a good thing. HWBOT (as it is now) and BenchMate are two very different approaches to competitive benchmarking. HWBOT uses screenshots, CPU-Z started after the benchmark, uploading with manual form entry. That was always problematic to begin with, because the data to moderate scores is simply missing. So even if you have ten paid fulltime guys, you will fail. The concept is flawed, but without any universal alternative it had to make due. BenchMate however tries to create a new workflow similiar to that of Geekbench and 3DMark, but for every benchmark out there. This even works for benchmarks that are not supported anymore. Time measurement, process memory protection, result saving and uploading - these features are hard to do and very time consuming. With BenchMate's eco system the benchmark developers can simply use the actively supported infrastructure and focus on the workload. Is that hard to do? Fuck yes. It's a nearly impossible, non-trivial task. Security alone is hard enough, but BenchMate needs to be fast as well to have no impact on benchmark performance. So the only thing I need to ask for is patience so I can make it happen. I like feedback. Good, bad, ugly, it's all fine to me as long as it helps to improve BenchMate in the long run. To me it just seems that you have mixed 0.9 and 0.10 to make Geekbench work, which is no longer officially supported. Neither is version 0.9.

The GeForce 210 was released in 2009. It is pretty normal for software to improve backwards compatibility to legacy hardware over time. And as I said above, it is already fixed and will be available with the next version.

This is well known. Old NVIDIA drivers want to inject code into the benchmark process, which is obviously a big no-no! Fixes: Use the latest NVIDIA driver if possible Use a more recent NVIDIA GPU or an AMD GPU The upcoming version has a fix for this and will not block the result, but still block the access to the process memory.

Also, Windows 10 on Ryzen is forbidden by the rules. Use https://benchmate.org or Windows 7. With BenchMate you can have overlapping windows, the resources are tracked for integrity so you can't fiddle with the rendering.

@ML_azul This indicates that something is accessing the benchmark's process memory, which is forbidden of course. The same thing could for example change/overwrite the score in the window. I've already seen this quite a few times in the past months and the problem is an old version of NVIDIA's GeForce driver for old graphics cards (like 8000 series), that tries to hook into the process for whatever reason. You have a few options: Update the driver to the latest version. I'm not sure if that works for older GPUs. Use another GPU. AMD is fine for example. This bug has been fixed in the upcoming version, I just disallow the access from the driver. It doesn't harm anything but won't trigger the error.

Want to know what's up with BenchMate? Actually a lot! So I have decided to post an update on our Patreon site. These will happen more often again from now on, but certain things will be for supporters only. I'm talking prerelease versions as well so your feedback can be part of the development process. https://www.patreon.com/posts/its-alive-thanks-37143552

Happy birthday! (guarded by BenchMate )

I haven't seen the details, but this is only a suicide run, not full load wPrime/CB. Also, was there a CPU-Z validation URL?

Same for me, I'm also a team captain. Didn't we have this bug a few months back?

Just adding some useless information: The PCI subsys ID is the card model. Classified will have another subsys ID than the KP.

No no, let him upload the result file. It is lying around in BenchMate's result folder and was automatically created when you made the screenshot. Upload that and we believe you.

Still a screenshot and shows exactly why we can't work with pixels only anymore! Please upload the result offline file into the "with BenchMate" category.

It's a screenshot. What else is there to say?

Sadly unfixable, it's a hardware detection error.

The rules of HWBOT specify what can and can't be used to create a valid result for its database. That said, the rules have already been properly updated for the possible use of BenchMate. CINEBENCHR15/R20 for example: https://hwbot.org/news/9946_application_94_rules/ Benchmarks that are not supported by BenchMate can either be benched anyway because they have proper timer validation (3DMark Timespy for example) or can only be benched using Windows 7. Again, this is defined by HWBOT and their rule set for each benchmark. You can download the latest version here: https://benchmate.org

This is already fixed and will be released with BenchMate 0.11. Intel and AMD iGPUs will be correctly measured. The lesson here is, that it's not a good idea to put any detection code or submission implementation into a specific benchmark version. There are too many moving pieces at work, it will fail eventually. That's why BenchMate's new infrastructure is so important. A benchmark should focus on its workload. GPUPI 4 will not use HWiNFO or provide any form of submission. Instead it natively integrates BenchMate. This is the way.

It is expected behaviour for now. You can close old finish windows at any time. The advantage of using a modeless message box (instead of a modal one in the original code) is, that it does not disable/block the main dialog. So you can freely move the SuperPi window, which is normally pinned down to its position. You can also close the application at any time without the need of closing message box first. The disadvantage is that it's a bit confusing. To mitigate that I could close any old message boxes when a new run is started. I've put it on the list, it sure is a better solution!

Your CPU doesn't support the AES-NI instruction set which is currently necessary to do all the security features fast enough so they have no impact. That said the upcoming version is shortly from being released and will introduce full backwards compatibility for old CPUs. As soon as I have fixed all bugs, it will be available for download.