Jump to content
HWBOT Community Forums

CL3P20

Members
  • Posts

    492
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by CL3P20

  1. I like the examples you brought up Bruce.. but arent those 'variations' the same reason why an efficiency ranking could be so useful? For folks tuning for a bench, it can reveal quite a bit about their relative strengths/short-comings..

     

    *Perfect example - try to input the recent top 32m submission from MOA 'A' class into the above table... it seems there would be a new leader on the efficiency table.. and with quite staggering results/settings by contrast.... .....

  2. vccin on some batch of Pentium K will help a lot.. others will hurt. Definite "sillycone"

     

    3418B7xx - CB @ -120c ;scaling under cold with 2.92v vccin, up to 1.91v vcore - 5.75ghz through R15 and XTU

    *stable at above volts and temps through rash of multi-thread bench, back/back

     

    3418B9xx - CB @ -105c ;scaling under cold with 2.4v vccin, up to 1.66v vcore - 5.65ghz through R15 and XTU

    *stable at above volts ONLY at ~ -86c through multi-thread bench.. colder = random reboots, regardless of volts

     

     

    **going back to 'Auto' for SA and IO's, when pushing for stability at next multi is proving helpful for me... if everything posts, good then try for more vcore. Clocking these little pentiums can be fun.. just need to 'slap' and 'tickle' all the right spots with finger on the GO button!

  3. in regards to Pentium K batch;

     

    3412B7xx - seem to be clocking 5.7 - 5.8ghz range and voltage tolerant.. CB's ~120

    3418B9xx - seem real 'hit or miss' batch.. general low volts, low CB .. some capable of +6ghz 2D

    3418Cxxx - needs more samples.. but looks amazing so far! First -130c CB reported !!

  4. If you want to know who/what your up against in a comp.. isnt the best strategy to go cold and post results? You have to jump out and lead for others to follow... No point on posting place holders unless they are the 'best' placeholders you have from said cooling method and session.. otherwise comp becomes compilation of bunny scores until the last week/days .. :(

  5. your score was likely removed because it is invalid..

     

    *look at the password checked column and the time column... they should steadily increase from top to bottom... If you have a larger # somewhere in the middle of your result table, using the same SSE instruction set.. your score is a bug run.

×
×
  • Create New...