Jump to content
HWBOT Community Forums

websmile

Administrators
  • Posts

    5822
  • Joined

  • Last visited

  • Days Won

    58

Everything posted by websmile

  1. I guess the rules are clear, there is stated use one processor... On the second question, no idea what you mean, you can use the qx9775 in single configuration for the dogple and that´s ok, it will cover the model
  2. Hi, welcome to my thread, I offer my last excess memory kits, both are tested and in good condition. 1, 2x8GB G.Skill RipjawV DDR4-3600 C17-18-18-38 1,35v SN 1615A500xxx67/68, B-Die. The kit was tested for 3866 12-11-11-28 tight 1,85v Spi32m with Copy waza in xp, it does all benches between 1,82-1,85v real voltage also at win7x64. On top I also succeeded in running the kit at 4000 12-12-12-28 1T 220 with waza at 1,92v, and other benches like Pifast at 12-11 for example, but the mems are hard to handle, so for me stable benchable frequency especially for 32m is up to 3950 on my OCFM. It seems that one stick is not too voltage tolerant, so I decided to sell the kit quite cheap. In blister with sticker 2. 2x2GB Crucial Ballistix Tracer DDR2-800 C4-4-4-12 2,0v Tested an working, kit did 800 c4 and 1000c5 below 1,9v not minimized. If you take a look at the screenshot, you might recognize the same OS install used for 1151 - which partially explains why the times are this fast^^ Prices 1. 140 Euros shipped worldwide sold 2. 25 Euros shipped worldwide sold in germany, money donated to dimastech fraud victims The mems are located in germany, payment can be done with paypal or western union, buyer covers fees or sends as gift. I will ship with insurance and tracking with deutsche Post which is around 12 Euros for the ripjaws and 7 for the tracers(included already) Disclaimer: No returns accepted, I am selling privately and not business related. I also cannot provide warranty, but mems are at top condition and vendors warranty should work in the unlikely case you kill them and cause no physical damage
  3. Sadly no, this is what hurts me personally a bit, but no exceptions. For all stages no server hardware, only exception is Skulltrail because it was a desktop gaming concept that Intel branded this way despite socket 771 used
  4. Have you tried to vary (raise or lower) VCCSA and VCCIO? Sometimes tighter rtls at 1T need more imc volts and also sometimes more vdimm.
  5. We checked all results at sc1-4, what is left should be valid on sc3 stage 6 the fix was screwed sigh - tasked it again
  6. I tasked this, should be added shortly like the cpuz cpu/mem tab rule to make this bullet proof even if you do not read this thread or general rules. I think Leeghoofd nailed it pretty well why we want screenshots with background for all stages, and also why we want cpuz tabs for mem stage. No one would be happy if at a s.939 stage for example suddenly an old backup score by giannigt is posted to own us all . Without this rule we could make database query before the comp starts and announce a winner based on scores from the past, no matter if guys still have the hardware or not. The team cup is meant to start at zero, all provide new results, all have the same chance therefore to make a good campaign
  7. Simply add a picture of the stick(s) used, no need to rebench because of this. I will not remove sumissions because of this, you are not vendor bound for example. Generally, we cannot add tons of rules to each stage and even to the competition rules. We did this sometimes in the past and feedback was "too complicated, we overlooked some parts, etc" and had more problems than positive feedback from this. The rules for the specific benchmark always apply, and if we make add on to the rules at a competition like for example at memory stage, the general rules for validation apply.
  8. Sorry, if no one bothers to read the posts here, I will not explain all again. We have a time limit that only results made on or after start of team cup are accepted for the competition, if you do not understand this, it is not my problem anymore. It is the way it is
  9. I quote it again, these are the screenshot rules of hwbot. If we ask for a screenshort for obvious, already discussed reasons, these apply Screenshots are, next to the links, another method of providing the required verification. Please make sure your screenshot is as clear as possible! In general, this is required: CPU-Z CPU information tab CPU-Z Memory information tab GPU-Z videocard information tab (3DMark/PCMark/Aquamark) For SuperPi/Pifast: entire calculation has to be visible For 3DMark/PCMark: benchmark settings have to be visible as well as the subtest scores P.S. you can read the complete general rules here HWBOT General Rules and Guidelines
  10. No need to change it when it is neither time limited nor team bound. If we would not need proof that the sub was made for a competition and not an older score was recycled, screenshot would not be necessary. I understand you are angry, maybe you can imagine how staff feels often when we have to make rules because we know a few guys, very few, like to bend or break the rules and we have a ton more on workload because of this. We do it to protect the legit guys
  11. @Rauf First of all the general rules from 2011! last update on screenshot rules say so, and second point is to rule out (or at least make harder)screenshot sharing @ Mr.Scott I will not dig out old stuff, we draw the consequences from this to avoid stuff like this in the future
  12. We checked ourselves, this is why we went for cpu 1,76 and the screenshot - on the recycled scores, I do not think I have to give examples, everyone should have seen this especially at challenger divisions over the last 12 months. It was reason we made background mandatory
  13. Many also submitted 3ds lately without gpuz - shall we change the rules because of this?^^ P.S. Screenshots are, next to the links, another method of providing the required verification. Please make sure your screenshot is as clear as possible! In general, this is required: CPU-Z CPU information tab CPU-Z Memory information tab GPU-Z videocard information tab (3DMark/PCMark/Aquamark) For SuperPi/Pifast: entire calculation has to be visible For 3DMark/PCMark: benchmark settings have to be visible as well as the subtest scores And on the topic, if not tons of people would have cheatet last years at challengers and other comps by recycling old scores, we would gladly skip the screenshot - so it is our fault that there are people who cheat?
  14. We handled it with screenshot last year and this year at several competitions and had very good experience with this. The reason we want the screenshot should be quite clear, we checked cpuz and found it to be possible to recycle old subs... P.S. The general rules are quite clear for screenshots and what is needed, if we demand a screenshot cpuz cpu and memory tab are always needed
  15. Definitely. I created a task to add this to the screenshot rules, obviously we expected too much P.S. Good this came up quite early, so we can add to the rules before the hot phase starts.
  16. Sad to hear this , but let´s not ignore common sense - we all know the minimum requirements for 2d screenshots, this is 2x cpuz with cpu and mem tab. Please don´t make life so hard for yourself, a bit of logic and common sense are often better than making 10 pages of rules.
  17. CPU and mem tab are minimum requirements for a screenshot, xoc should be ok, no difference from validation to screenshot. Please provide a picture of the rig with mem stick visible
  18. Yes, this is a typo, on 3ds of course the vgas make the result and therefore three different gpu models have to be used P.S. Of course I scheduled a fix to end confusion^^
  19. Intel delivers the new HEDT CPUs without cooling solution, I see no warning advice that you should not use lm for TIM on the package. It is quite easy to read the FPO even on the pictures that were added by oldcomer, and a lapped cpu looks different. So, we usually agree but this time not, Ben. If I pay 1k for a highend cpu I should be allowed to apply the best thermal interface solution retail market offers unless Intel rules this out explicitly. There was no physical damage applied imho, and also no "modding". Might depend on how you see this personally, maybe you are right, maybe I am, but in the end I personally do not approve on the decision made my Intel
  20. Damien, please add a picture of the cpu - you are for sure not making my life easy^^
  21. This is a truely bad surprise. I thought they would handle things more generously, they must know that liquid metal on the heatspreader leaves marks and as long as FPO and APO are still readable, I see no reason to reject an rma claim. Disappointing from my point of view, good cooling for a highend product should be in their interest to avoid rmas, and when you use best TIM, they reject the claim, weird
  22. #2 sold, payment received, thanks . #1 reserved until wednesday morning All sold, thanks for the space, hwbot
  23. It is 3Mark11 physics according to the stage description
×
×
  • Create New...