Jump to content
HWBOT Community Forums

ground

Members
  • Posts

    634
  • Joined

  • Last visited

  • Days Won

    10

Everything posted by ground

  1. What ram are you using btw? Looks like bbse or psc on first glance
  2. I have an dead (no boot, instant memtest errors) Kingston 2000c8 stick without heatspreader and sticker + 15 loose ICs from a stick that didn't even get to memtest that haven't been cleaned (not ripped pads though). I need 3,70€ shipping + a decent offer for the dead parts. Might have the PCB from the stick I harvested somewhere too, but I think I lost the 16th IC. Said stick failed boot all the time. Both sticks were MGH-e from different kits. The dead stick was completely dead at some point (not even posting), but after spending a day in a dewar it at least posted, but threw tons of memtest errors. Didn't test it beyond that since I have a decent amount of working sticks (no more rejects left though)
  3. I know there are way too few kits available for purchase for larger scale binning, but I would still like to know what observations others made about binning Hypers around here. I‘ve collected about a dozen sticks of 2000c8s from Corsair/Kingston over the past half year (and talked to some others who also picked up a couple), and noticed a couple things: (testing done on x58) - most 2000c8 could manage 2000 7-7-6 32m at <1.7V - 2200 7-7-6 seems to be close to impossible on non Corsair sticks. Not sure if they binned differently or if its the pcb. Triple kits seemed to do better - the bin is usually fairly consistant for voltage at 2000 7-7-6 (1.64-1.68V for the sticks that did alright) - one kit of Dom gt performed particularly bad; pretty sure it was degraded badly by its previous owner. The best stick barely managed posting 2100 7-7-6 at 1.9V, couldn‘t do spec at 1.65V. - 6-7-5 and 7-8-6 max MHz were fairly consistant (except for the kit mentioned above) across all sticks, anywhere from 2060-2080/2280-2340 - no noticable voltage requirement difference between 7-7-6/7-7-7 or 6-6-5/6-6-6 or 6-7-5/6-7-6 Can anyone see anything that appears weird / did anyone notice similar stuff / completely different behavior? Anything interesting to add? And before anyone asks, I‘ve already sold the kits I don‘t want to keep, nothing for sale.
  4. Pretty sure you can usually expect slightly worse memory clocks on x58 just due to the layout of the platform which is quite suboptimal. The decision to keep most boards 6 dimms over 3 also doesn‘t help this, at least thats how it should be in theory. I personally prefer binning ram on the platform its most likely to be used on (thus binning hyper on Haswell makes close to no sense at all to me). Regarding other Hyper (Kingston, Supertalent etc) - I‘m not sure if its just my small sample size, but I‘m pretty sure the others seem to be much weaker at tRCD on average. All 2000c8 dom Gts I‘ve had in my hands (except for one particularly garbage kit which couldn‘t even do spec) could do 2200+ 7-7-6 tight at some voltage), while others seemed to run into a wall at significantly lower clocks with same trcd. Once testing 6-7-5/7-8-6 they performed way closer to the Dom GTs. So, not to derail the whole thread (time to move this to the general hyper discussion?): Can you test the 920 on SS? You know my criteria Taking the W3680, I want a new cpu for memory testing
  5. Broke the threads? 2 of my 2000c8s have those too Don‘t screw them on too tight.
  6. I'm guessing this is said 3600+ gdie validation? https://hwbot.org/submission/3832580_noxinite_memory_frequency_ddr3_sdram_1841.2_mhz I've finally gotten around to pick up a haswell system so I'll test my sticks pretty soon edit: brainfart, 4gb won't be sr gdie
  7. Okay, anyone who runs into the ~118-122 boot limit on asus try different GPUs. I had thought my 8600 gt couldn’t be the cause since it posts 126 on msi, 136 on gigabyte x58 and 155 on gigabyte AM3. Turns out it was the limiting factor, posting 138 consistantly with an HD 5450 now. That should be enough for 306 BCLK post Edit: Nevermind, it only applies to 45nm CPUs. Apparently those can boot higher PCIe clocks for 45nm. Just confirmed with my 8600 GT
  8. Keeping ram means having less budget available for either the next time he bins more ram or the next time he quits memory binning. GL with sale web!
  9. Holding first and second on the platform now, huh?
  10. . Chip is absolutely stupid and in no way maxed. We were running >5.5 32m later but the effi sucked, probably messed the OS up. At ambient the chip does this at 1.33V: Uncore at 4.0 with 1.26V: Chip also does >5 GHz uncore (I've ran pifast at 5.5 core 5.4 uncore on Dry Ice a while back, but since it didn't scale didn't bother subbing). Stops scaling at 1.6V which we hadn't quite reached. Wouldn‘t surprise me if this chip is capable of 5.6 benchable in the right hands...
  11. ground

    Close please

    @Leeghoofd weren't you looking for a 3770k? Could that be a candidate?
  12. Doable if we find a gigabyte board that plays well with my E5640 or I find more tweaks
  13. Thanks everyone! Special thanks to Tagg and Shaggy who helped a lot during the session/did some extra binning/provided extra boards/etc, Tapakah, Jokot and T.Rex for doing some cold(-ish) testing and/or providing extra information, the r/overclocking and warp9 guys with their patience with me on my journey to this note: I think I still have a better CPU with a lower coldbug, but that would require me to get it running properly on a gigabyte board, all 4 we had during the session refused cooperating with me sadly. With the boards we had the maximum achievable due to the pcie wall would be 305-310, but I don‘t think I‘ve found that CPU yet... this is where we starting celebrating https://valid.x86.fr/hd3vw2
  14. Jup, from the session with tagg and shaggy, plenty more stuff to try today too. This score is a fairly hard board limit (both with single and dual CPU), limited by a pcie wall at 114. If I could figure out whats holding pcie back I wouldn‘t even be surprised by 260+ on ambient because this is at stock voltages and these CPUs are binned for that.
×
×
  • Create New...