Jump to content
HWBOT Community Forums

websmile

Administrators
  • Posts

    5824
  • Joined

  • Last visited

  • Days Won

    58

Posts posted by websmile

  1. Howdy

    sales time, the memory kits are tested and work fine

    20190131_200518nujj5.jpg

    1. 2x8GB G.Skill Trident Z Red DDR4-4133 C19-19-19-39 1,35v

    Tested on apex x for 4200 12-12-12-28 tight 2,08v Geekbench3, XTU and X265, maxed out at 4260 GB3 2.14v. Fast test on Apex XI showed similar potential, 4266 12-12 tight worked for CB15 but not GB3. With box and sticker

    426012-12gb3214vx7kt1.jpg 20190131_200620goje4.jpg

    2. 2x8GB G.Skill Trident Z Black DDR4-4400 C19-19-19-39 1,40v

    Tested on Apex XI, due to the fact that 4200 divider does not work for me and BCLK-oc is somewhat strange I tested 4133 12-11-11-220 tight at 2,06v and 4180 12-11-11-28 tight, ran out of bclk and 4266 12-11 boots and enters windows but failed GB3 at 2,15v. These sticks have no labels anymore, so I have doubts they have warranty, but spd, pcb-print and layout show these are genuine 4400s. Bulk

    2088labllose4400f4jp7.png snaphsot0009qtkun.png 20190131_200607btkyk.jpg

    3. 2x8GB G.Skill Trident Z Black DDR4-4400 C19-19-19-39 1,40v

    Tested on Apex XI for 4133 12-11-11-28 tight Geekbench 3 at 2.01v, at 2.11v they do 4266 12-11-11-28 tight Cinebench 15 but fail GB3. Intact labels, 1734 built. Bulk

    snaphsot00122p7kc1.png snaphsot0011q5khp.png 20190131_2006153vjol.jpg

    Prices (shipping comes on top)

    1. 250 Euros

    2. 185 Euros sold

    3. 275 Euros

     

    Payment with paypal (buyer is responsible for fees or gift payment) or bank transfer at germany. Shipping is limited to european union at 12-16 Euros depending on courier, for outside of european union shipping is unaffordable because the german monopol company dhl randomly ended option to send small goods with letters. You can get a quote nontheless, but shipping might be a deal killer

    • Like 2
    • Confused 1
  2. Is there any chance the 4200 divider on memory will work c12 in the future? I tested this with two different cpus (8086k and 8600k), different settings and it did not work on apex xi, plus I talked to a couple of people using gene with same problem. Tested with bios 0231 and also latest BIOS from asus website, it worked 2 or 3 time out of 100 tries and that simply is not enough for such a good oc board

    • Like 1
  3. I don´t like playing the devils advocate, but what do we do when UL changes rules again? Delete all scores again? And what about the fact that UL has major problems to guarantee security and check for several new benchmarks (Timespyyy cough) and I do not even talk about legacies like vantage and older? We can of course stop tweaking, but will it help to stop cheaters and will it work in the future?^^

     

    Marco , the timer issue is mainly a problem if you use win 8 and 10 and pre skylake hardware, becuase there it is often a sign that rtc clock was (or could be) manipulated - the time shift effect to boost scores illegally you can find at win 8 and 10 rtc bug article.

    • Like 6
  4. 48 minutes ago, cbjaust said:

    And yet no allowance was made in the hwbot rules for changing AA.

    Still don't know if reporting non-conforming scores will be actioned. 

    Why should hwbot make an allowance for AA? The fun fact is that all results before I think 2017 which had AA changed were valid with Futuremark if I remember correctly, so it was clear this was allowed. Suddenly FM changed this for hall of fame, implemented a check on this and excludes new results from ranking. If you look at programs like nvinspector there are 100+ driver settings you can change, so each time fm is bored and changes rules we delete all old scores and start at zero? I am not sure this makes sense, but agree that this might need clarification especially for new members like you?^^

    • Like 2
    • Thanks 4
    • Haha 1
  5. Because scaling on single and multi core is not linear with frequency but explodes, geekbench 3 was not designed for frequency like this and it simply looks as if the lack of maintenancemakes calculation not work properly under certain circumstances. Your safe benchmark btw also bugs at win 10, this was tested, and as said the maxmem settings also boost the score if too low bc of above mentioned reasons. At least some plausibility checks should be done, especially when you see that other benchmarks that profitate from high memory like spi32m which have a firm calculation base are faster at 4100c12 vs around 4800c14 at tests shown here on hwbot

  6. People told you to report scores like the ones by H2ovsln2 - who has done this multiple times before even when I was still a mod, but got no time out for whatever reason. But talking about cheats when someone changes driver settings, or uses LOD where allowed is simply not leading anywhere. Benching is already much too much pay to play and soldering instead of optimzing skills. If you think that legal driver tweaking, or waza, or disabling services at os is cheating, bench prime 95 like others do and cheat on temps ;) - the gb3 desaster you talk about is constantly ignored by hwbot btw, it is not only that low maxmem bugs the score because of not enough drm-memory left to correctly run the benchmark, everyone who has eyes also sees that the results at settings like 4600-4800c14 bugs at multicore mem copy, but as long as majority rather plays this instead of reporting tons of scores, nothing will change, I am tired of messaging people on fb or talking ther about it, discussing this and see no result, It is the community who needs to change this, and if you don´t do it, don´t complain ?

     

    P.S. Lod was allowed long ago, and that aa changes are illegal to fm(UL) is not older than 2 years, while 3dm01 is now nearly 20 years old. So what sahll hwbot do, delete all scores made applying to rules?

    • Like 5
  7. What´s the problem here? Since the beginning of benching people changed driver settings and it was legit, like aa settings, you change driver from high quality to performance and settings change... The score is ok, main problem is others smartassed around, pulling cables, running black, changing bench files and rsolutions, mipmap etc. This is what kills hwbot benching, but this is definitely not the place to discuss here on a correct score ;) - topic closed

    • Like 1
×
×
  • Create New...