Jump to content
HWBOT Community Forums

All Activity

This stream auto-updates

  1. Past hour
  2. Default was 1.35 I think. I was trying to see how quickly the voltage rised when turning the pot to see what the non linear behavior was like.
  3. Today
  4. To be fair I have no idea, I haven't looked at it and I can't be arsed to.
  5. 10980XE is sold. Bump for 11700K!
  6. I don't understand what's missing. The ability to use a program to hack the bios to show hidden engineering settings doesn't work? What settings are you looking for so that maybe we can help you out.
  7. There are some subs without comp background and no rig pic
  8. What is stock ram voltage though? Normal practice is to raise it a bit at a time to check scaling, as that way you can stop when either scaling turns negative or you have reached a maximum clock.
  9. So I finally got a 560 ti modded for both core and mem, cap mods, delided, and on an aio and before running any benchmarks I raised memory voltage above 1.7 volts (I don't know exactly what it hit) and had immediate shutoff followed by artifacting and inability to get into windows outside of safe mode. The Elpida datasheets suggests that the gddr5 should tolerate 2v. Its possible that I passed this point but i'm thinking that its more likely the memory controller. At least I already had ordered another 560ti (hopefully without elpida this time). I'm hoping that somene with more experience with this can shed some light on safe memory voltages for fermi cards. I'll post a full rundown of the mods soon.
  10. no, you do not its ready but hidden, as soon as corsair gives the go it will pop up yes, everybody can participate but with ambient temps...
  11. I have 2 units I would be willing to part with if anyone is interested. 1 is a masscool unit. reach out to me email or pm me for details meankeys
  12. From what I know you are already basically describing the geekbench memory test. I think it would be better to have two seperate benchmarks rather than a legacy mode. Updating is both kinda necessary to deal with changes in architecure but also a massive problem for rules/scoring. My preference would be having algorithms change with major versions and each major version being a seperate benchmark à la geekbench.
  13. Why not to make a thing that acts like AIDA64 (measures read/write/copy/latency) with 3dmark01 like formula for final score? I was running aida on very different setups (from mendocino to haswell-e, diffferent chipsets (via/sis/intel/nvidia/amd) and it was quite informative. Problem about aida64 is that diffferent versions have different optimisations - still, you can now make a version that will cover all existing memory types from EDO to DDR4 (I think we won't see anything newer than alder lake with ddr4?). So that will be one "basic" part - which won't be updated with newer algorithms (just bugfixes). Call it "legacy mode". And all newer hardware will have different mode that you will be able to update - and changes in that part can be then covered with hwbot rules.
  1. Load more activity
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...