Jump to content
HWBOT Community Forums

tiborrr

Members
  • Posts

    545
  • Joined

  • Last visited

Posts posted by tiborrr

  1. It works on retail 5820K, tried both mods. For 2nd mod I did it without external power device. Just connect it to VDDR MOSFET or coil and your VDDR = you "uncore signal voltage".

     

    MSI X99S XPOWER AC

    Before mod: 3700MHz

    After Easy 4G mod: 4100MHz

    After 4G+ mod: 4500MHz (1.6Vddr = 1.6V "uncore signal voltage")

     

    This CPU is capped at 4500, test on X99-DELUXE, will have to try with my 5960X.

  2. We can see the 3 icons in the taskbar :)

    Fixed in less than 20 seconds.

     

    aQVUzZl.jpg

     

    @mat

    I may have a solution for this screenshot issue.

     

    The solution would be to save the result in form of a file. Once the calc is done the background info is encrypted and saved into a binary file, which is then uploaded to hwbot. This way the user would have to upload both valid file (encrypted) as well as screenshot. This way the photoshop overclockers would have more issues bypassing the results.

     

    This way the benchmark submission routine would consist of:

    - valid file

    - screenshot per hwbot rules

     

    You could add a "Save" button next to OK button to "Pi Calculation is done" splash window.

     

    What do you (Genie, mat, massbo) think?

  3. Pushed Pitcairn below 1 minute for 1B: http://hwbot.org/submission/2696798_tiborrr_gpupi___1b_radeon_hd_7870_%28pitcairn_core%29_59sec_231ms?recalculate=true

     

    Also, there's an issue - you can open multiple instances of GPUPI, which is problematic:

    - you get end result whether the calculation is valid or not. it's easy to open another instance and run short 1M bench, hide it from screen and apply "Pi calculation is done" window to the invalid run.

     

    My recommendations would be:

    - locked main computing window while dialog window (Pi calculation is done) is opened.

    - only one instance of GPUPI can be run.

    - no result should be print to screen if there is an error in calculation.

    - if possible, an invalid run should halt the calculation right after it encounters rounding error or at least after each loop, like in original SuperPI (if possible by the algorithm).

    - Hwbot should add a valid checksum textbox, which should be mandatory for each submission.

     

    Regards,

    Niko

  4. Great benchmark, love it!

     

    I would vote for 2B and 32B to be accepted as 'retail' benchmarks once benchmark passes through the Hwbot validation:

     

    I would also lock down the benchmark window when splash screen "Pi Calculation is Done!" comes up. Just for the sake of nostalgia :)

     

    Here's my workstation machine with FirePro W9000:

    4b6idFG.jpg

     

    Wannabe W7000 (flashed 7870, slower DP):

    5XYHEnK.jpg

×
×
  • Create New...