_mat_
-
Posts
1003 -
Joined
-
Last visited
-
Days Won
41
Content Type
Profiles
Forums
Events
Blogs
Posts posted by _mat_
-
-
What happens when you just open a browser and go to hwbot.org? If the certificate is deemed invalid, can you show the certificate properties? It should show exactly why the certificate is invalid.
As for the others, the certificate is either still valid or they don't check the certificates for uploading.
-
Yes, I think that's it. Have you tried the update? Does it work?
https://www.catalog.update.microsoft.com/search.aspx?q=kb3140245
If it works, I will add it to the install readme of the manual installer!
-
7 hours ago, wutske said:
I
Anyhow, small side note, I can't send the results from Benchmate from Windows 7 (probably due to certificate errors), but you can just copy paste the results folder to a Windows 10 PC and then send the results from there.
This should work when installing the hwbot certificate from BenchMate's manual installer. If it doesn't work, please let me know.
-
On 12/2/2023 at 9:19 AM, switch said:
I'm using BM 11.3.0.
Is it possible to add Cinebench R24 manually? I've unpacked it and moved the binaries to the a created folder under apps called Cinebench\24.1.00 and then tried to add the binary from there, but it produces an error dialog with message that the application is not supported.
Thanks you.
It's done and currently in its testing phase. I am taking my time on this because I have a lot on my plate right now and the benchmark is huge and very different from its predecessors (it uses the Redshift renderer now).
-
Does it work without BenchMate? Because that looks like an Intel OpenCL error to me.
-
1 hour ago, NATA 58 said:
benchmate error
Your BenchMate files are either not valid (a file might be missing or corrupt - happens on bluescreens, try to reinstall BM) or if the Windows has not been on the internet for a long time (the many txt files suggest that), you need to install the SSL.com certificates, that BenchMate's file have been signed with.
You can find the certificates in BM\res\certificates\install-run-as-admin.bat. You need to run that file with admin privileges.
I thought about improving that error message. It happens too often and needs to be better balanced between security and practicability.
-
1) It's just a warning, you can ignore it. As you can see in the result window CPUID and SMBIOS show two different brand strings. But they are both saying it's the same CPU, so the result is good. This is a BIOS Implementation error. Although I could loosen up the validation and allow brand strings with different postfixes. Let me think about it.
2) It's a Windows 7 bug. ACPI PM timer is hogged, no idea why. You need to wait for 2 or 3 minutes so Windows allows to query the timer properly.
-
2
-
-
BenchMate 11.3 is out now. This release shows some love for legacy platforms! ?
Intel CPUs prior to Nehalem will be benchable again if the system's hardware timers are stable. Yes, that means LGA 775 is back in the game. Thanks to @TheQuentincc for his bug report.
And Windows 7 now has a Manual Installation guide. It's basically a big zip file you can download from the website. After unpacking there is an INSTALL.txt file, that guides you manually through the more difficult steps to make BenchMate and HWBOT submission work on legacy operating systems.
Download: https://benchmate.org/
Changelog: https://benchmate.org/changelog/11.3.0
-
1
-
2
-
-
@Monabuntur I did some further testing with the new PYPrime version, but the time ran out so the new category is still using PYPrime 2.0.
-
BenchMate 11.2 is now available for download. It adds PYPrime 32b for the HWBOT Country Cup Memory Stage and fixes a couple of bugs, that have been reported.
Download: https://benchmate.org/
Changelog: https://benchmate.org/changelog/11.2.0
Donate: https://www.patreon.com/benchmate -
OpenCL runtimes in use?
-
Btw, you can see all Intel OpenCL tweaks in the result window. IOCL Vectorizer Off and AVX2 is the key here. These tweaks are possible with or without BenchMate and have been for many years. Now we have some transparency on Intel OpenCL settings.
-
I had a change of heart and tried to get the download below 600 MB.
It can be added manually with the + button. If it's often used, just let me know and I will bundle it again.
-
Let me check tomorrow. I am still sick, but tried my best to release today.
-
1
-
-
BenchMate 11.0.5 is now available to the public: https://benchmate.org/
? Supports y-cruncher 0.8.1 and 0.8.2 (bundled)
? Noctua Theme
? New CPUID verification to warn on spoofed CPUs
? Modern Radeon cards are now able to run GPUPI
? New GPUPI for CPU tweaks for latest Intels OpenCL runtimes
? New CINEBENCH R2x tweaksCheck the Changelog: https://benchmate.org/changelog/11.0.5
Please donate to keep the project alive: https://t.ly/lndkO
Have fun ❤️
-
2
-
1
-
-
I also wanted to give an update here about the launch date of BenchMate 11. I am still waiting on Microsoft to come through so they reenable my Partnernet Hardware account to be able to sign BenchMate's driver for an official release.
I also checked if there is a way around the signing by using the driver version of BM 10.12. It's sadly not possible, so we have to wait on Microsoft.
-
1
-
-
I fixed the priority setting in BenchMate and it correctly forwards that priority to y-cruncher.
In addition it is now possible to select the benchmark's priority in the CLI wrapper options. Makes it more accessible and easier to play around. It works for all CLI benchmarks (pifast, 7-Zip and y-cruncher).
-
Yes, BM could fix this. But x265 is hard to inject into due to using Java for the wrapper. It's also very big and would double the download size of BenchMate.
Adding x265 is on my list. No promises though.
-
1
-
-
HPET system-wide enabled + many cores = no performance.
It's all bottlenecked by the slow timer calls.
-
The options in the CLI wrapper are there to avoid any hassle with the command line. That ensures that only safe command line options are passed and that the benchmark is easly accessible for newcomers.
So I'd rather don't want to make it available and find myself in the predicament to whitelist or blacklist the options.
If there is the need to control the exact number of threads, I can happily make it available as an option.
The priority is already handled by BM and the CLI wrapper the same way it is handled for any other benchmark (right click on the benchmark in the benchmark list => Priority => ...).
I heard that there is a bug with y-cruncher running it as low priority. I will fix it (maybe by passing the priorty command line option). -
The driver is updated at least once per major release. Minor releases often use the same driver. That hasn't been a problem until now, but it seems like I need to question these dependencies.
-
To be precise the automatic vetting of my company for the Microsoft Partner Network has not been working for the past 3-4 weeks. So I am locked out and can not sign the new BenchMate driver for the new release.
Wrote to Microsoft Support as well, but it's a farce. Days go by without any progress.
-
OpenCL 3.0 won't work with GPUPI. New BenchMate 11 will fix this. Use Intel OpenCL runtime 18.1 for now (OpenCL 2.1).
The error is something else though. How much RAM is available on this system? It needs about 360 MB for 1B.
-
It was only reported on the 7900X so far, but it's hard to recognize unless the result is double-checked with the TD command line option.
The official BenchMate support thread
in Benchmark software
Posted · Edited by _mat_
Yes, there is a problem with the hwbot certificate on your system. It has a fairly new root or intermediate certificate from their certificate provider, iirc.
Normally this happens if the bench os has not been updated in a long time, or hasn't had an internet connection in a while. Many certificates in the Windows certificate store won't be valid anymore and that breaks the certificate chains. The easiest way is to update.
I tried to solve it in the manual BenchMate installation but failed to fix it. I will try again soon.
Easiest way to fix this is to install updates.