Jump to content
HWBOT Community Forums

Lays

Members
  • Posts

    356
  • Joined

  • Last visited

Posts posted by Lays

  1. Thanks man, will check that out.

     

    I've been having the worst issues with the board tonight. BCLK clocking was gone. Code 8 - power off - overclocking failed even at 100.08 BLCK, with both first and backup bios. Battery out and back in, re-entering Windows XP as well as Win10 "management engine" was recognized as new device. Of all bugs I've seen, this one is ranking pretty high in the category of strange :D

     

    @Lays: I wouldn't worry about XTU, relaxed RTL seem to kill any MHz gains at least on my crappy OS :D

    xtu45001214mtczmd.png xtu45001214m2njlgc.png

     

     

    If you do find that BIOS, can you link it here? I been planning on buying a 3258 for some DICE fun.

  2. I just quickly chose the nick shih 2933 preset and tightened mostly just the main timings. I set 2.25v cause I knew it would boot and left the rest auto. Those mems can run those timings at lower volts plus setting manually the sa and io volts does help. The pic was supposed to give you a starting point for timings as the rest varies. Oh and here on Earth, we say thank you icon10.gif

     

    Thanks buddy :D

     

     

    It needed 2.287v from DMM to run R15 on realtime priority, got a pretty decent score increase (4 points extra vs 2864 mhz tight)

     

     

    But XTU refused to cooperate, even with 2.333v from DMM, I don't feel comfortable pushing any more volts, I don't have the other 2 sticks for the kit so I can't RMA.

     

    lmZje.png

  3. Instead of trying something like 9-13-13-17, try 9-12-12 but you may have to raise tRAS up to 21-24 and or tREFI as high as 128. Actually here are perfect settings to start with and tighten from here. Rtl's probably wont get to 41-42 unless u have 2 dimm board or some cold aka -35C

     

    attachment.php?attachmentid=3481&stc=1&d=1447609212

     

    I shouldn't need anywhere near those Sytem agent & IO volts I don't think, I am only using +0.125 for SA and AUTO for IOD/IOA, and 2860 was running fine

     

    I'll add more if I need though. I'll go and try all those settings shortly.

  4. Still testing some stuff, I know this is not superpi 32m, but I figured I'd take a screenshot of my timings and ask some questions.

     

    vdimm @ 2.15v, how much headroom do I have? I really want to see if I can get 2933 9-13-13 to run or something like that.

     

    I am unsure if I need to loosen RTL to get 2933 to work, I don't really know much about RTL and stuff like that.

    Also for some reason TWR is displaying as 18, but in BIOS I'm fairly sure I have it set to 10. (I'll go fiddle with this and see what's up)

     

    lmsqk.png

  5. Not sure where this fits in with xoc unless you can run 3 separate heads minimum (cpu/gpu/ram) and have independent temp control for each?

     

    Looks like a cool idea to be improved on although cost I would expect to be high. For a start certified pressurised dewars ain't cheap!

     

    Voltage read out points would be an absolute must for board (easy to do) and gpu (not so easy, would need solution for external volt. regs.).

     

    You'd also need to be able to raise temp independently for various cbb.

     

    GPU would probably be quiet easy with something like this mounted outside case with wiring going to GPU:

     

    http://forum.hwbot.org/showthread.php?t=100242&page=3

  6. Gotta be honest with you... I don't know what v-readouts are. I know the GPU temp didn't readout under 0C. But the mobo read down to -59C during extended use. The OCC cools the CPU or GPU with liquid nitrogen while the purge kit cools everything else with gaseous nitrogen and purges out all moisture from the case. Basically the case is an environmental chamber cooled by the gaseous nitrogen from the purge kit :-)

     

    v-readouts are voltage readpoints, where you could hook up a multimeter to check voltage

×
×
  • Create New...