Jump to content
HWBOT Community Forums

Bilko

Crew
  • Posts

    283
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Bilko

  1. The rules for this have been clear since 1st generation Ryzen launched.

    https://hwbot.org/newsflash/4335_ryzen_platform_affected_by_rtc_bias_w88.110_not_allowed_on_select_benchmarks

    Check the date on the article first, then check the benchmark rules, looking over your history it's all Cinebench R15 and R20 so let's use those benchmarks as an example
    image.png.7a14265d429539dd9a49755c33f8e238.png

    Now if you read the rules then you'd see that Windows 8, 8.1, 10 and their server variants aren't allowed here but to help illustrate that further there's a nice chart if you click on the link

    image.thumb.png.aad749d2a8e230622fafe5dfb96b475a.png

    Does this help clear it up?

    I've no doubt these rules and chart will get updated going forward especially with the inclusion of benchmate being a requirement but really the fact is this was never allowed and as Mat has proven not all platforms are safe from this even with HPET enabled.

  2. Don't think I would have seen this without the bump ? (thanks Allen!)

    I'm all for it, so far Benchmate has been pretty reliable and if there's been issues Mat has addressed them in a timely fashion, I personally would love to be able to sub with Win 10 simply for ease of use and I'm sure there's quite a few others who would feel the same.

    The supported benches list is growing and probably most importantly it provides people with an easy way to submit a score :)

  3. 7 hours ago, unityofsaints said:

    Any idea why my FS sub got pulled from the comp?

    https://hwbot.org/submission/4213802_unityofsaints_3dmark___fire_strike_radeon_rx_vega_8_mobile_2657_marks

    Systeminfo is up to date, rigpic attached. I don't see any issues. Easy to rebench, just wanna know for next time. 

    Quote

    A VALID Futuremark verification link is required (systeminfo 5.17 or newer)

    Your link has unknown hardware and Tess off.

  4. 30 minutes ago, cbjaust said:

    @Bilko try earlier versions of SytemInfo. 3DMark11 seems to recover and run even after SytemInfo fails. You can try the DIAG executable in the SytemInfo directory to pinpoint the faulting module, in this case it will likely be GPUZ.dll.

    Cheers, It's on my list to come back around to at some point, First step is a clean OS and trying an older version of sysinfo to see if that fixes it up.

  5. On 8/20/2019 at 6:15 PM, Leeghoofd said:

    Anyone else have issues with Systeminfo with 3D11 Entry stage?

    I had a couple of issues with it not being able to detect the GPU used for some reason
    image.thumb.png.9012b9e6d5cdf9445658c5ba747c170f.png
    https://www.3dmark.com/3dm11/13442091
    image.thumb.png.62b25bbb6a076f09b7016175cff7a8b3.png

    Tried it on several cards, drivers etc but always the same error, I also set the time correctly as well but even then nothing helped so for now I'm leaving that stage alone and might come back to it later.

     

     

×
×
  • Create New...