Jump to content
HWBOT Community Forums

l0ud_sil3nc3

Members
  • Posts

    3543
  • Joined

  • Last visited

  • Days Won

    36

Posts posted by l0ud_sil3nc3

  1. Maybe, just saying :) , Z170 is not exactly compatible with Kabylake ( bios wise ).

    Maybe vendors try to push users to Z270.

    And maybe they are right.

    Because if all the line of Kaby's is fully compatible with Z170, what is the real reason to move to Z270 ?

     

    Maybe Apex is of interest to TOP GUNS. But to lower levels ?

     

    My final thought.

    Yes, it is a fact that Kaby's are slightly better clockers.

    And Z270 very high end boards better than Z170 very high end boards.

     

    But, as I said, besides the real TOP GUNS, who else might be really interested ?

     

    IDK but MOCF has been working fine with Kaby for many users and in fact I would say compatibility between Skylake > Kaby is perfect as in you can pop one in and they both work the same.

     

    With that being said, Apex is inbound (thanks Newegg!) and I will put it through it's paces and see how it compares to Z170. As long as it's nothing like an Impact I think I will be happy, Impact was complete garbage for me in terms of memory clocking and never have I raged as hard as using that little board.

     

    I mean the fact that you had to bin motherboards on the Impact is ridiculous, there should not be that type of difference in memory oc from board to board i.e. if you take a cpu, set of memory (same order) from one board to another they should clock fairly similarly.

     

    Regardless I think if you have an MOCF it's good enough for most users, but if you are buying a new Z270 board for Kaby it's safe to say the Apex is a no brainer. Looking forward to rebinning all my B-Die on the Apex as memory OC looks strong af :)

  2. Cracked tim ?

     

    Verstuurd vanaf mijn MotoG3 met Tapatalk

     

    Nope possibly defective sata port on the Intel controller or just some weirdness once you go cold idk. I noticed this issue on one of my particular boards and thought I had a bad SATA cable and or SSD or that my OS was possibly thrashed.

     

    But simply moving the SATA cable from the top first Intel SATA port located closest to the 24 pin to any other port seems to fix it and everything boots fine. The weird thing is that it's not reproducible easily for me and reboot usually fixes it allowing the OS to boot on that top left Intel port. Maybe something with the PCH idk I'm not an electrical engineer lol. Good thing I notice this weird shit and I am not the only one it affects.

  3. OK... This is something, my chip can't do.... You won!

     

     

    No backups here and out of LN2. I think Allen will slay us both hahaha his cpu looks super strong. Always a pleasure battling with you even though we have our differences and at a point and I may not have liked you, I have always respected you as your submissions are always quality and that's what matters at the end of the day.

×
×
  • Create New...