• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Recent content by st0ne

  1. S

    Paint

    Can anyone suggest what kind of paint I should use to paint some case trim, and possibly the tubes for the corsair h100. I have a maximus iv extreme so i'm going with a complete black/red theme, red custom braided cables, some ENERMAX MAGMA fans for the h100 in push/pull and one for rear case...
  2. S

    So many different Gentle Typhoons - Did I get the right one?

    lol.. @ 44.0dBA you could probably hear it a mile away.
  3. S

    Asus P8P67-PRO & i7-2600k questions

    Think about what you just said there on this forum :P Don't get me wrong though, I fully agree. I was originally running 4.8ghz @ 1.44v and dropped to 4.5 @ 1.325v - This dropped my load temps from 80c to upper 58/59c. Huge improvement at a 300mhz difference. What's that, a few % difference...
  4. S

    You Are In Siri-ous Trouble

    Probably just upset he couldn't get his iPhone 4s on launch day :P
  5. S

    2600k Voltage Issue

    Ahhh, understood. Thanks so much :)
  6. S

    2600k Voltage Issue

    Thanks so much spine!
  7. S

    2600k Voltage Issue

    How do I calculate what I should use as offset? Was my original post right? Do I take the voltage given by cpu-z under load and subtract it from what it states the vid is in real temp?
  8. S

    i5-2500k oc'ed to 4.5ghz voltage settings

    Not sure how you can say this since every chip is different and each chip requires different amounts of voltage to stay stable. I've seen cases where someone has a stable overclock of 5ghz @ 1.368v, and another person with 5ghz overclock @ 1.488v. I think the diminishing returns would depend...
  9. S

    i5-2500k oc'ed to 4.5ghz voltage settings

    Well, There you have it. You answered your own question. Intel spec sheet states 1.52v Most people's opinions play into things beyond that. No one is absolutely sure of what the safe vcore is for sandybridge procss. What I do know is a lot of people prefer to stay in the 1.3x region. If you're...
  10. S

    2600k Voltage Issue

    Not only stable, but able to drop core voltage down and stay stable. I'm down to 1.325 from 1.375 @ 4.5ghz.
  11. S

    Best heatsink/fan for 2500k/2600k

    The Prolimatech Armageddon with two 14cm, 1,000rpm Prolimatech Vortex fans for push/pull. Used it on my 2600k @ 4.8 for a while before I just switched to the Corsair H100. idle was mid to upper 30c full load (IBT, P95) was 80c On the other hand.. the H100 keeps this thing cool at 28c idle and...
  12. S

    2600k Voltage Issue

    Thanks! I will tell you this, for anyone else who may be interested: I decided to play with CPU PLL Voltage lastnight. It was set at auto pumping out 1.8-ish volts. I manually set the PLL voltage to 1.525 to see what would happen. Not only was I still stable, but it allowed me to move the...
  13. S

    OC'ing specifics, help?

    Also, I learned a valuable lesson too. Check your CPU PLL Voltage. It's usually set to auto humming along at 1.800v. Try setting this to 1.7v manually. The lower voltage seems to increase stability at lower vcore settings.
  14. S

    2600k Voltage Issue

    Okay... Hopefully someone can help me understand and/or fix this issue, let me get started with my system: Corsair Obsidian 650D Case Corsair Professional Series Gold AX850 850W PSU Corsair H100 Cooler Asus Maximus IV Extreme Intel Core i7-2600K 3.4GHz OC'd @ 4.5 GHz (originally at 4.8)...
  15. S

    Blue Screen Problem

    This was a known issue on earlier versions of the firmware, which I experienced myself. After updating to the latest firmware the problem seems to have disappeared.
Back
Top