• 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.

I5 2500k Unstable - SOMETIMES, Help! :(

Neil79

n00b
Joined
Nov 12, 2011
Messages
32
My settings for 4.7GHZ

-i5-2500K 4.7GHZ,Gigabyte Z68XP-UD3P,HyperX 8GB,GTX 560Ti OC,Samsung 1TB+SSD CACHE,Corsair V2 600W,Win 7 64bit.

BIOS VERSION - F6

\MB - ( M.I.T )/
\Advanced Frequency Settings/

CPU CLOCK - 33X
BCLK - ( DISABLED ) left at default 100mhz
EXTREME MEMORY PROFILE XMP - ( PROFILE 1 )
SYSTEM MEMORY MULTI - ( AUTO )

\Advanced Cpu Core Features/

CPU CLOCK RATIO [33X]
PWN FREQUENCY CONTROL [ AUTO ]
INTERNAL CPU OVER CURRENT PROTECTION [ AUTO ]
INTERNAL CPU PLL OVERVOLT [ AUTO ]
RATIO CHANGES IN OS [ DISABLED ]
INTEL BOOST TECH [ AUTO ]
RATIO 1 - 4 [ 47 ]
TURBO POWER LIMIT [ 250 ]
CORE CURRENT [ 250 ]
CPU CORES ENABLED [ ALL ]
CPU ENHANCED HALT C1E [ AUTO ]
C3/C6 STATE SUPPORT [ AUTO ]
CPU THERMAL MONITOR [ DISABLED ]
BI-DIRECTIONAL PROCHOT [ AUTO ]

\Advanced Memory/

EXTREME MEMORY PROFILE X.M.P [ PROFILE 1 ]
SYSTEM MEMORY MULTI SPD [ AUTO ]
PERFORMANCE ENHANCE [ STANDARD ]
DRAM TIMING SELECT SPD [ AUTO ]
CHANNEL A - B [ AUTO ]

\Advanced Voltage Settings/
MULTI-STEPS LOAD-LINE [ LEVEL 6 ]
CPU VCORE [ 1.340V ] ( TEST WITH PRIME 95/INTEL BURN TEST AND THEN LOWER THE VOLTS UNTIL UNSTABLE TO FIND YOUR LOWEST STABLE VOLTAGE )
QPI/VTT VOLTAGE 1.050V [ AUTO ]
SYSTEM AGENT VOLTAGE 0.920V [ AUTO ]
DYNAMIC VCORE [ AUTO ]
GRAPHICS DVID [ AUTO ]
CPU PLL VOLTAGE 1.800V [ 1.800V ]
DRAM VOLTAGE 1.500V [ 1.616V ] ( LOWER OR HIGHER DEPENDING ON MEMORY REQUIREMENTS )
DRAM VREF 0.750V [ AUTO ]
DRAM TERMINATION 0.750V [ AUTO ]
CH-A/B ATA VREF 0.750V [ AUTO ]
CH-A/B ADDRESS VREF [ AUTO ]

\Misc Settings/

ISOCHRONOUS SUPPORT [ ENABLED ]
VIRTUALIZATION TECH [ ENABLED ]

\Power Management/

HPET SUPPORT [ ENABLED ]
HPET MODE [ 64BIT ] - 64bit windows versions

\Pc Health/

CPU SMART FAN CONTROL [ DISABLED ]

Sometimes it will work for a week other times boot loop, I can play hours and hours of BF3 and skyrim, do lots of photography. It's 10+hrs prime 95 stable and many many runs of Intel Burn test at both medium and high. Yet sometimes when you boot the system it will hit a boot loop, and keep getting to the bios logo and turning off, then turning back on again. You have to leave the power cable out for a bit, then reboot while pressing DEL to get to the bios setting's screen, to reset back to 4.6GHZ.

However If i then go back to the bios and set to 4.7GHZ with my above settings it will work perfectly again, any advice?
 
Also, I've been reading about a problem with this board, and all gigabyte z68 boards of an endless boot loop, which can spontaneously start happening even after a month or so of running fine. I'm a bit nervous since it appears to be the luck of the draw as to whether or not you get a faulty board. Some say the boot loop happened after they tried to overclock. Others claim it happens if you hit the restart button. I see many of you have had success overclocking with no boot loop problems. Has anyone encountered this problem?

Damn it :mad:

http://www.overclock.net/t/1034724/gigabyte-p67-z68-boot-cycling-problem
 
Last edited:

Gigabyte has these random retarded issues with their boards. I remember with my P35-DQ6 and Q6600 overclocked to 3.6ghz, cold booting was be a hassle. I had this issue where it would turn on for a second, shut off, and then attempt to turn on, except half the time everything would just flicker and go dead. For a while I thought it was just me, until a friend of mine reported an identical problem with his 45nm quad on a different board.

But a P35-DS3L had no such issues overclocking a X3380. Seems hit or miss.
 
Back
Top