Jump to content
HWBOT Community Forums

cagej

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by cagej

  1. Lets just say you are right...... but

    You are mistaken, HW sharing is not allowed and it is banned...

     

    Sorry I just do not believe that 0.576V is not under LN2 or some ICE..... cos Ryzen is super-sensitive with low TEMP... lower temp = much higher clock.. how big believer I am I don't believe it.

     

    CPU-Z is reading CORRECTLY Vcore for months... not now in June... OK I was not able to correctly tune H265 bench (much harder to tune) with Ryzen (new platform), but I have much much much faster GPU PI with very same clock... and do not tell me, that when he reaches more then 4200 MHz with H265 he was not able to run 4300+ on GPU PI... I just cannot believe this bunnyextraction.. And his Vcore is out of thing air 1,49V@4250 MHz what I believe is true. He has slow mem timings, so low score...

     

    Well guys we had this setup running in the shop (hence the same background) were we had a small workshop with the rookies (people from the shop itself).

     

    For your info the same mobo to clock the memory (CH VI), mem, gpu and OS was used (as we had no clue how to get them temp readouts working.) The clocking itself was done by these persons (not that Ryzen is difficult on air).

     

    If you look at the earlier submissions by eg Jastas you can see he was running his daily 6700K( XTU score), though this score was not be enough to compete in Stage 1 nor 2. So we organized a session at the shop to get up with the other Ryzen scores. Heck I even drove off to a few members to help them to get it all dialed in and working right before Computex.

     

    During Computex we constantly checked our scores and ranking, motivating people to rebench. Admirably 12AX was still benching his X48 with Oldscarface a few hours before the deadline.

     

    edit: Ow yes maybe I forget too reply too the 0.576 Voltage... really guys... Maybe the slow pi time explains he is still a real Rookie that relies mainly on clocks than tweaks...

     

    quote :)

  2. You see, the issue with new-blo0od-only-stages is that, one can be a rookie, then become another and another.

     

    At least 3 results look hideously the same sans the CPU from 3 different new guys which I believe is technically done by a single guy..

     

     

    Well, at least he's a new guy :D

     

    P.S.

    rookie mistake SS and rig pics

     

    which one?

     

    Im afraid hwbot cannot guarantee that someone will make new account to become rookie.

     

    EDIT: See that - STAGE 2

     

    JASTAS & Dressed4succes = 100% the same.. white background, same GPU and cooler D15... Really ??

     

    Tibom2000 is also cheating my guess, 0,567V on air Noctua fan and 4200+ MHz core FQ! No bunnying way! Even temp is hidden.... God knows what temp is showing... And GPU PI super slow I cannot believe it as proper submit.

    Guys open your eyes, I have already reported this submit.. this is not air cooling...

  3. Little disappointed to say that Hwbot is ignoring the H265 issue, which is not supported on newer than Skylake CPUs. This means H265 bench cannot be properly used with Ryzen, SKX, KBX and KabyLake CPUs. Integrated Hwmonitor does not support these CPUs while H265 is sometimes giving back error : bad ambient cooling.

    According to developer these CPUs are really not supported and ambient cooling is ignored due to bad reading. This means potential cheating during contest, when you can use much better cooling during test then after test..

     

    I was contacting personally Christian Ney and 0 feedback as well as it was mentioned in diff (ROG TEAM contest) thread.

     

    I am asking when we get proper answer what to do or stop using integrated ambient cooling or entire bench until newer version is published.

  4. Nice,

     

    by the way guys.. you need to reconsider to use H265 with Kaby Lake, Ryzen and SKX a KBX and ambient monitoring, because it is not officially supported and according to developer the temp reading in H265 is ignored due to bad reading :).. just for info :).

     

    I must say I did not understand Ryzen and H265... was not able to tune it @Max FPS.. getting always about 11FPS like something is really bugged here.

×
×
  • Create New...