Jump to content
HWBOT Community Forums


  • Posts

  • Joined

  • Last visited

  • Days Won


_mat_ last won the day on August 29 2020

_mat_ had the most liked content!

About _mat_

  • Birthday 04/11/1982


  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

_mat_'s Achievements


Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. No, sadly it was not possible for me to finish the latest maintenance release yet.
  2. Very soon. I had a very tight deadline with work and have been coding day and night. My life currently sucks, but I'm still trying to make it happen asap.
  3. Great work. Exactly how it's done.
  4. It's a bug in the latest HWiNFO version. I will contact the dev today and see if we can figure it out.
  5. Please post the wrong screenshot so we can look into it. BenchMate doesn't show any chipset information. Where is that detection and what's wrong with it?
  6. Yes, you can match as you like. The fastest card will decide the combination represented on the bot. Your example will be listed as 3x3090. As for the 6900 XT, I'm not getting support by any graphics vendor, so no, there currently is none for GPUPI as well. Yes, it goes both ways.
  7. Would fit better in the BenchMate support thread, but my guess: You are not using the bundled HWiNFO version. They have to be compatible, otherwise they don't load next to each other. It's a limitation by the SDK/HWiNFO.
  8. 25m is no longer an active category on the bot. @Leeghoofd This question arises again and again. It might be best to enable 25M but don't give any points.
  9. Where is the OpenCL.dll from? I do not distribute the OpenCL.dll with GPUPI. This DLL should be available on your system; best case is that the graphics driver deploys it according to what feature level is available. The error is from the OpenCL DLL that seems to be out of date. Remove it as Strunkenbold said. If it's not working, please install a graphics driver or one of the OpenCL Redistributables from a CPU vendor. Intel OpenCL preferred. I also advise to not run any executable from the Music folder. It may have special rights. Same with the Documents folder.
  10. BenchMate should fix these issues: https://www.patreon.com/posts/50198208
  11. Microsoft Defender detects BenchMate as a trojan that sniffs bank data. It's of course a false positive (as always). I already hunted it down. Whole Sunday gone to shit basically. Will have a new version of BM ready to "fix" this. Glad I can add a HWiNFO update as well so the release somehow makes sense.
  12. The BenchMate categories only exist for automatic uploading from within BenchMate. It's a technical issue, because some of the old categories (Super PI, wPrime, ...) do not support the HWBOT submission API. So yes, you can just take the screenshot and upload it to other (matching) categories. See BenchMate as additional proof for a valid score.
  13. Something we should think about is the definition of "maximum frequency". Right now with CPU-Z the definition is that the CPU's sensors can be read and the CPU can produce an encrypted result file (which implies disk I/O, multiple levels of drivers invoked, CPU-Z version-dependent code, ...). It's also not a very stable definition as it can change (and has changed) between different versions of CPU-Z. The right term instead of "max frequency" would actually be "CPU-Z validation stable". So before it makes sense to code anything, we should try to define what "max frequency" really should mean for us and also for the outside world. And how this value is communicated to be credible. How it's technically done is for now irrelevant. The requirements will define that.
  14. Of course. It would need to be done using BenchMate anyway because as soon as we are talking validation, security and timers, you will always end up with the same conclusion: it all sucks and needs a whole concept to make sure that it is foolproof, hard to cheat and easy to use. New BM version will also let you close the client at any point. So only a background service is running to measure sensors and the driver enables correct time measurement and that's it. That said the saving of validation files should be done differently as well. Also without the client and with a single hotkey. So new BM versions first, new suicide runs later.
  15. Maybe this is the right time to discuss that the validation of a fictional number like the CPU frequency is not a credible basis for competitive ranking. I'm thinking a small workload would be more suitable for this kind of task (idea by @mllrkllr88). Something completely independent of memory, but big enough to show the scaling (in comparison to other CPUs of this generation). This workload could even come in multiple flavors like single-threaded, multi-threaded, AVX*, each separated into their own categories here on HWBOT. Not an easy task all in all but a big improvement for the moderation and therefor the credibility of suicide runs. Edit: It also makes a lot of sense to use effective clocks instead of the fictional numbers. Much more reliable (although harder to comprehend for the overclocker when benching).
  • Create New...