Jump to content
HWBOT Community Forums

_mat_

Members
  • Posts

    1003
  • Joined

  • Last visited

  • Days Won

    41

Posts posted by _mat_

  1. On 8/2/2019 at 2:19 AM, CjMitsuki said:

    Yeah, i suppose I will have to do that with R20 but during the benchmate  comp I didnt have a problem uploading from the benchmate software.  It always immediately linked to the comp.  I also found a bug with custom resolutions through the Nvidia display settings.  I have a 1920x1080 monitor and you cant fit CB R20 on it so I used nvidia settings to make a 4k resolution to fit it all on there.  Well, it seems that benchmate doesn't recognize the resolution change and benchmate cut most of the screenshot out.  Ill have to report it to Mat when Im home from work in a few hours so I can replicate it and confirm what it looks to be doing.  The bench was just a rough trial bench so not worried about losing that score.  Looks like manually uploading Cinebench runs will have to be how it is until the problem is patched.

    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. :(

    • Like 1
  2. On 8/3/2019 at 6:56 PM, Bilko said:

    From how I understand it atm Raven Ridge and Picasso are fine on 10 but Matisse isn't (outside of the usual 3DMark, x265, Benchmate)

    So Matisse, Pinnacle Ridge and Summit Ridge are all in the same boat.

    I would not count on that at all. AMD CPUs are using their LAPIC timer for the System Clock Interrupt in Windows 8+. That timer completely depends on the ref clock. The same goes for the TSC on AMD, it's basically the same timer source as the LAPIC timer. So if there is any possibility to change the ref clock, it will result in skewed benchmark results.

  3. On 8/2/2019 at 8:54 AM, GeorgeStorm said:

    @_mat_ any update on the issue @0.0 pointed out?

    The vulnerability has been fixed now and will be released with BenchMate 0.9.

    I can't say the same for all other benchmarks that either enforce HPET (GPUPI, x265) or just use QPC with "useplatformclock" enabled (Geekbench for example). I don't have the time right now, but my best guess is that even kernel tick related timer functions can be tricked with this as well. That would include 90% of all benchmarks here on HWBOT.

    0.0 did this with very little programming experience and he used a third party driver, so he didn't need kernel driver or reverse engineering skills.

    @GeorgeStorm What is HWBOT going to do about that?

  4. Thanks for pointing this out, I've simply overlooked it.

    It's certainly an interesting attack vector, that is sadly allowed by the specs of HPET made by Intel and Microsoft. It's also NOT a BenchMate specific problem, all benchmarks relying on HPET will be vulnerable by this.

    And to put this in the right perspective: A driver needs to be written, that has low-level access to HPET. So this is not everybody's cheat, some big hurdles need to be overcome to do this.

    I'm in contact with 0.0 and we are working on a solution.

  5. That should work then because the result is fetched from the integrated IE browser window. The problem with the tryout version is that it directly opens the default browser with the already uploaded online result.

    The new version fixes that by setting its hooks deeper into the benchmark. I sadly can't disclose it because everything that's done is actually a vulnerability of the existing benchmark. :D

    And thanks for your Patreon donation! You are officially the first person on this earth that donated to BenchMate. I love it, thank you very much!

    • Like 1
  6. 53 minutes ago, ajc9988 said:

    @_mat_

     As a nice to have, you could maybe add a place where people can put stock photos of their rig needed for enthusiast league and above. This will help allow people to upload not just the score and screenshot, but the other files needed to get points. Call it a point of laziness on my part and others, but having to go edit the score on hwbot to get points is a bit of a drag. I do like the automated nature of this app.

     

    So, I'm asking for up to 4 slots for images, similar to the submission page, so that we can just tuck those pics into a folder for benchmate and not have to think too much about it. Not a high priority, but something to consider.

    This is a feature request for the HWBOT submission API. BenchMate can make use of it, if it's there.

    Another great feature would be to add the submission comment to the API as well.

    @Devroush @Leeghoofd

    • Like 3
  7. Short update: In the last two days I rewrote the Geekbench support to include tryout versions as well. This was for sure a motherfucker, but it's even more stable than ever and independent of any GUI activity.

    On a more important note: I've also encountered a problem with ensuring reliable time measurement and upholding the unified security standard on Geekbench. As there is an inner benchmark executable it is not correctly set up yet to support the whole range of security vulnerabilities. I'm in the process of fixing this to make it completely compliant to BenchMate's standards. My recommendation is that Geekbench results made with all currently available versions of BenchMate should have their points disabled and remain as test results. Sorry folks, but that's why we needed this test competition!

    • Like 1
    • Thanks 1
  8. 2 hours ago, Matsglobetrotter said:

    No, i run it just like its set up ? meanwhile after 2 re-boots the behaviour is gone?! no win update in between

    i like this benchmate though. kudos to Matt ?

    I'm pretty sure that the old driver was still loaded without reboot and that's why the service failed to handle new requests.

    I will write an updater next that will take care of properly reloading everything without a reboot. It will be necessary anyways. :)

    2 hours ago, yosarianilives said:

    Does drag off screen work?

    I guess it's the same there. The problem is that I need some entry point to know when a run has been started and ends. That's easy for most benchmarks, but CINEBENCH has a custom UI so I can't capture any WIN32 API function from button inputs and the likes. We'll find a way. :)

  9. The service is needed to guard a 32 bit benchmark from a 64 bit environment. I can't overcome the WOW barrier without it, so if the service is not working, 32 bit applications will not start.

    The "BenchMate Security Service" can be found in the service list (type services.msc in the taskbar's search field). It should be running while BenchMate is active.

    A Bug Report (from the menu) would be nice after you tried to start a 32 bit application and it's not working. Otherwise it's hard for me to determine what is happening here.

  10. Thanks!

    BenchMate 0.8.2 will follow in the next few days. Will add some love for Windows 7, fixes Geekbench 3.1.5 and allows submission with Geekbench 4 Trail version.

    There is also a bug currently with Cinebench. If you run it minimized it can't capture the score. Same thing happens if you use a very high priority class on CB, the system will be so swamped that I don't receive a notification for the start and/or the end of the run. Please be aware that this could happen.

    There are also no bugs currently that invalidate a verified run. That's a good thing. :)

    • Like 1
    • Thanks 1
  11. 15 hours ago, techjesse said:

    Mat, Excellent Coding, love the GUI :)  have a prob though.. will not detect SLI :(

    Thanks, I will have a look at it. SLI/Crossfire information is determined by using the native driver libraries NVAPI (for NVIDIA) and AGS (for AMD). A bug report via the integrated "Bug Report" functionality (in the menu) might come handy to be able to see what is going on here.

  12. You need the latest version to be able to upload the files correctly. Please download 0.8.1 from here: https://www.overclockers.at/news/benchmate-beta-tester-gesucht

    It's in German but the download links are right under the first image.

    @Leeghoofd The news on the main page link to the download of version 0.8 directly. I strongly encourage to use the latest version of BenchMate, it fixes many bugs. Maybe redirect it to the site above as well? I'm working on a microsite for BenchMate that will soon be ready and in English of course.

  13. Hey, Bruno! You need to press the "Save Result" button to take a proper, BenchMate verified screenshot. It will show the full run statistics and the score. Afterwards it can be uploaded to the temporary BenchMate category for Geekbench 3 by pressing "Submit to HWBOT" (or right click on the result in the result list, you can also view your screenshot there).

  14. BenchMate shouldn't have a different rule set, I agree. It's here to make life easier for everybody (except me). That's why it should need NO rules at all. Just run your benchmarks with it and you are fine. That's by the way exactly what you always wanted, Leeghoofd ... "Just click the damn run button!" :D
    The question is what do we need to do to get there in the eyes of the HWBOT moderation team.

    @Leeghoofd I will add texture file hashing for CB in the next minor version, 0.8.2.

    When a new benchmark pops up, it should never be added without knowing what it does, which vulnerabilities it has and how reliable it is. Otherwise things can go south quickly, results have to be removed, maybe the whole benchmark. I've seen this happening too often and it leads to a lot of bad blood. So we should work together on ensuring to avoid that at any cost.
    When adding new benchmarks to BenchMate I ensure that they are in fact validatable. If they are not, we can contact the author and talk about the necessary changes. That's an important communication and verification process that HWBOT misses right now.

    Also important to note here is what happens when a benchmark is added to BenchMate. As soon as it's in a lot of well-known vulnerabilities are already handled. Timer troubles are gone instantely and results can be submitted to HWBOT without any additional work for integration.
    Do you see how easy things could be?

    About XTU, please post a screen to clarify this.

    @cbjaust I guess you are talking about all the information that's shown on results like this: https://valid.x86.fr/2xfi08
    BenchMate is currently designed to detect everything that's necessary for benchmarking. Complete system analysis will be added further down the road by adding more and more information as needed.

×
×
  • Create New...