Jump to content
HWBOT Community Forums

chew*

Members
  • Posts

    589
  • Joined

  • Last visited

  • Days Won

    11

Posts posted by chew*

  1. I had similar issue, but of course, I cant run it at 4500 MHz with AIO :) But If I tried 4150 MHz, I got lower score thnan at 4074 MHz, with 4100 MHz only 5 points better than at 4074 MHz. Temps are not issue in this case...So I dont know :)

     

    Of course they are...i wont even try running over 1.45v on phase change...

     

    1.6 i use for pi...single threaded...

  2. Can't go over 3300, maybe the limit of my IMC or hitting the mem hole.

     

    I did not hit a hole infra but i can say this on dual rank.

     

    At 3390 i was over 1 sec faster in 32m pi then 3420.

     

    Coincidence? Doubt it. I think its a strap or performance related memory hole. Imc was also failing just over 3400

  3. The issue with Flops was found and fixed in the beginning of february.

    The current µcode version dates to 01/27/2017, so the fix is obviously not included yet (due to the time required for validation).

    Flops is only affected when the SMT is enabled, so disabling the SMT can be used as a temporary work-around (until the actual fix arrives).

     

    Except for the fact. He already ran smt off tests and still had said issue. Least thats what he said.

  4. All ref clock boards are using an ASMEDIA chip. I could be wrong but this was for fine grain control. The cpu is actually capable without the chip.

     

    1.2v was deemed safe in reviewers guide yes.

     

    Why anyone would just jack voltages up without verifying that they are actually helping anything is beyond me however.

     

    First thing I did was lower all voltages looking for potential overlooked gains.

     

    Then I retested raising.

  5. Alright, thanks for advice. My sticks are singlesided, I pulled them out and had a look. Also thanks Infrared, that's some useful information.

    It turns out my CPU had this memory "hole" a little earlier than expected (this is described in the Asus C6H OC Guide). For me, 3100-3400MHz are a no-go, but 3500MHz booted flawlessly. *facepalm*

     

    I could even get some good latencies out of those. I ran SuperPi 32M at 3520MHz CL13-13-13-32@1,425V 1T if I remember correctly.

     

    Another thing I noticed is that with anything above 105MHz BCLK my M2 SSD stops working (960 Evo). So for testing the memory I had to install a fresh Win10 on a SATA SSD. Also, now that I have this sorted out, the M2 performance is in the bin, so the issues don't quite stop for me there ;(

    This btw also means that I can't run my memory on its specification because for 24/7 I can't go higher than 105MHz BCLK (because PCI-E 3.0 doesn't work above that) and I can't clock it between 3100 and 3400MHz. So I'll just have to stick with 2933MHz CL13. Ah well.

     

    Be advised bclk is strapped to PCI. Many devices will not like high PCI, some will corrupt some will break. Including onboard devices hard drives vga.......

     

    Best to disable all when "benching at high PCI"

     

    SOC may help stabilize IMC with 4 dims, no clue ( don't have 4 dims ) but with 2x8g single sided Samsung B die 1.0 is fine.

  6. The latest microcode that I have hates odd CL. try running even CL.

     

    I would physically look at your sticks to confirm single sided. 2T is what my Hynix was defaulting at on my double sided sticks.

     

    Double sided is almost the equivalent of running 4 single sided which also default at 2T.

     

    Not sure why everyone is obsessed with running SOC @ 1.2 I run all my chips at 1.0 just fine. less volts in less heat output.

×
×
  • Create New...