EVGA 750i FTW Overclock Thread

[PizzaMan]

Originally Posted by xguntherc

Anyone with the 750i FTW have any idea's or tips with setting up Raid on it. I just bought my second 640GB AALS

By a raid controller. It will be much faster then the onboard raid.

[RapidFireGT]

Ever since I overclock my Q6600 to 3.0GHz, I've been getting semi-frequent, yet seemingly random BSOD's. Information of interest:

CPU Frequency: 3001.6 MHz
Multiplier: 9x
FSB - Memory-Clock Mode: Linked
FSB - Memory Ratio: Auto
FSB Frequency - 1334
Actual Mem: 1000.5 MHz
Timings: 5-5-5-15-2T

CPU Core: 1.35v
CPU FSB: 1.3v
Memory: 2.1v
nForce SPP: 1.4v
NF200: Auto (1.2v)

BIOS: SZ17

I've already upped the memory voltage to spec, it's running at spec'd speed, although I'm running at 5-5-5-15 instead of 5-5-5-18. Is that the problem?

I've also tried upping the nForce voltage with no success. I've run Prime95 for several hours with no problems, and according to other 750i + Q6600 owners, 1.35v is enough voltage for 3.0GHz.

Anyone else have any ideas as to why I'm getting these BSOD's? I'm gonna try loosening the memory timings to see if that works. Also, here was the last BSOD I got:

*** Hardware Malfunction
Call your hardware vendor for support
NMI: Channel Check / IOCHK
*** The system has been halted ***

[twisted_58]

Originally Posted by RapidFireGT

Ever since I overclock my Q6600 to 3.0GHz, I've been getting semi-frequent, yet seemingly random BSOD's. Information of interest:

CPU Frequency: 3001.6 MHz
Multiplier: 9x
FSB - Memory-Clock Mode: Linked
FSB - Memory Ratio: Auto
FSB Frequency - 1334
Actual Mem: 1000.5 MHz
Timings: 5-5-5-15-2T

CPU Core: 1.35v
CPU FSB: 1.3v
Memory: 2.1v
nForce SPP: 1.4v
NF200: Auto (1.2v)

BIOS: SZ17

I've already upped the memory voltage to spec, it's running at spec'd speed, although I'm running at 5-5-5-15 instead of 5-5-5-18. Is that the problem?

I've also tried upping the nForce voltage with no success. I've run Prime95 for several hours with no problems, and according to other 750i + Q6600 owners, 1.35v is enough voltage for 3.0GHz.

Anyone else have any ideas as to why I'm getting these BSOD's? I'm gonna try loosening the memory timings to see if that works. Also, here was the last BSOD I got:

volts look fine. i would try flashing to the latest bios and see if that helps. theres a link to on the op of this thread, its the SZ1I bios. and if that doesn't work you could maybe need a tad more vcore but only like 1 notch or so.

[icecake]

First off let me say sorry if i did a double post.

Gents i need your help.

I can run Prime 95 for 45 Mins +-6 mins at temps of 46,54,54,55 degrees Cel respectively across the 4 cores@ 100% CPU usage. However, after that the system just freezes.

Below are my current specs and setup. Any advise would be greatly appreciated.


I have the following config and test results:

System:
OS: Windows 7 64bit
Q9650 445x9 VID: 1.250V Lapped
OCZ DDR2 1066 Gold Edition @ 5-5-5-15 2T 2.20V
EVGA nforce 750i FTW
BIOS V SZ1I
EVGA Geforce 9800 GTX+ SLI
Cooler: True 120 Black Lapped
PSU: NZXT 600W

Multiplier : x9
Mem (DDR) MHz : 1066
FSB-Memory Clock mode: Unlinked
Vcore: 1.3750V
CPU FSB: 1.40
Memory: 2.20V
nForce SPP : 1.50v
nf200 Volt Level : 1.50V
CPU Fast Read: Auto
CPU Clock Ratio Unlock: Unlocked
CPU N/2 Ratio : Disabled
LDT Frequency : 5x

GTLVREF Lane 0:+25mv, 1:+35mv, 2:+15mv, 3:+10mv

Thanks Guys for you continued assistance.

Icecake

[twisted_58]

Originally Posted by icecake

First off let me say sorry if i did a double post.

Gents i need your help.

I can run Prime 95 for 45 Mins +-6 mins at temps of 46,54,54,55 degrees Cel respectively across the 4 cores@ 100% CPU usage. However, after that the system just freezes.

Below are my current specs and setup. Any advise would be greatly appreciated.


I have the following config and test results:

System:
OS: Windows 7 64bit
Q9650 445x9 VID: 1.250V Lapped
OCZ DDR2 1066 Gold Edition @ 5-5-5-15 2T 2.20V
EVGA nforce 750i FTW
BIOS V SZ1I
EVGA Geforce 9800 GTX+ SLI
Cooler: True 120 Black Lapped
PSU: NZXT 600W

Multiplier : x9
Mem (DDR) MHz : 1066
FSB-Memory Clock mode: Unlinked
Vcore: 1.3750V
CPU FSB: 1.40
Memory: 2.20V
nForce SPP : 1.50v
nf200 Volt Level : 1.50V
CPU Fast Read: Auto
CPU Clock Ratio Unlock: Unlocked
CPU N/2 Ratio : Disabled
LDT Frequency : 5x

GTLVREF Lane 0:+25mv, 1:+35mv, 2:+15mv, 3:+10mv

Thanks Guys for you continued assistance.

Icecake

you could try kickin the fsbv up to 1.45 but i doubt that will be needed. i'd say keep messing with the gtlvref lanes. they were the key to getting my q9550 rock solid. here is a link that will tell you all you need to know about gtlvref:
http://www.evga.com/forums/tm.asp?m=...1&key=&#476249
it helped me imensly. it also might be possible that you are giving the vcore too much volts as too much can also cause instability. what i would do is try for stability with the gtlvref lanes (it will take a lot of work and restarts) then once you have it stable try lowering vcore if you can. if all that doesn't work you could downclock your ram to 1:1 @890, get stable, then tighten the hell out of your timings to make up for the loss in ram speed. see if any of that works.

[icecake]

Originally Posted by twisted_58

you could try kickin the fsbv up to 1.45 but i doubt that will be needed. i'd say keep messing with the gtlvref lanes. they were the key to getting my q9550 rock solid. here is a link that will tell you all you need to know about gtlvref:
http://www.evga.com/forums/tm.asp?m=...65533;�
it helped me imensly. it also might be possible that you are giving the vcore too much volts as too much can also cause instability. what i would do is try for stability with the gtlvref lanes (it will take a lot of work and restarts) then once you have it stable try lowering vcore if you can. if all that doesn't work you could downclock your ram to 1:1 @890, get stable, then tighten the hell out of your timings to make up for the loss in ram speed. see if any of that works.

to twisted_58

here are the settings i hanged:

Vcore: 1.3750V up one notch to 1.38125V
GTLVREF Lane 0:+25mv, 1:+35mv, 2:+15mv, 3:+10mv
to this:
GTLVREF Lane 0:+25mv, 1:+40mv, 2:+15mv, 3:+15mv
nf200 Volt Level : 1.50V to 1.25V (thought this really is not for OC'ing but SLI)


I have tried these settings in the bois. This time i tried intel burn test 2.1 and did 20 passes on the standard settings and completed 5 passes on the maximum settings. I have not testes prime95 as yet. What do you think of this?


Update: Tested prime95 and the system hung within 3 mins. Now I will try the lover memory speeds that you suggested.

Update 2: down-clocked the ram to 1:1 @890 with the same settings as everything above from your reply and ran prime95 for 3hrs 3 mins without any errors or problems

[twisted_58]

Originally Posted by icecake

to twisted_58

here are the settings i hanged:

Vcore: 1.3750V up one notch to 1.38125V
GTLVREF Lane 0:+25mv, 1:+35mv, 2:+15mv, 3:+10mv
to this:
GTLVREF Lane 0:+25mv, 1:+40mv, 2:+15mv, 3:+15mv
nf200 Volt Level : 1.50V to 1.25V (thought this really is not for OC'ing but SLI)


I have tried these settings in the bois. This time i tried intel burn test 2.1 and did 20 passes on the standard settings and completed 5 passes on the maximum settings. I have not testes prime95 as yet. What do you think of this?


Update: Tested prime95 and the system hung within 3 mins. Now I will try the lover memory speeds that you suggested.

yeah try the memory thing first also try stressing with this:
http://www.ocbase.com/perestroika_en/index.php?Download
its occt and is what i use. when trying for stable you only need to test 2hrs. get that to pass and you are stable then tweak setttings to get it to pass 6hrs and you are pretty solid. it will also tell you which core fails. that way you can adjust the gtlref volts. lanes 0/2 are for cores 0/1, and lanes 1/3 are for cores 2/3. each lane group should be added to when one of itsrespective cores fails occt. when you pass the 2hr test bump up lanes 0/1 a couple notches and lanes 2/3 one notch then go for 6hrs. see if that helps.

Originally Posted by icecake

Update 2: down-clocked the ram to 1:1 @890 with the same settings as everything above from your reply and ran prime95 for 3hrs 3 mins without any errors or problems.

didn't see the update. did you down clock the ram unlinked or at the 1:1 divider? cause you want the 1:1 divder set by linking the fsb/ram and choosing the 1:1 divider. but if you did that way then awesome. try running occt, pass 6hrs, then tighten the hell out of your timings as much as you can. then pass another 6hrs when done getting the timings stable. but way to go getting through 3+ hrs on prime!

[icecake]

Would you believe it? With the computer sitting there IDLE after all that time of testing and no errors / problems, it just hung up again.

I am suspecting memory problems?? What do you think?

[twisted_58]

Originally Posted by icecake

Would you believe it? With the computer sitting there IDLE after all that time of testing and no errors / problems, it just hung up again.

I am suspecting memory problems?? What do you think?

try running memtest one stick at a time in slot 1 for 5 or so passes each, then test a known good stick in each slot for 5 or so passes. that way you can find out if its memory or one of the memory lanes. try getting stable on occt first though cause it still may be an unstable overclock.

EDIT: also if you haven't done this already do the pencil mod. there is a picture on the op of this thread. it will help stabalize your vcore during sress tests by lowering vdroop, plus its 100% removable with a eraser if the need to rma arises.

[icecake]

Here's a quick update for you.

I did 4 passes each on the ram modules. No Errors. Tried different memory PC6400 memory and also set in the bois "linked and syncked". SAME Resulls of random freezes and i could only get about 5 mins OCCT with both sets of memory.

So i changed the memory settings to "unlinked" and i have passed 1 hr OCCT (no time for 6 hrs yet . Also uped the voltage to 1.39 in the bois as i saw in OCCT's report that the CPU max vcore used was borderline to 1.39V.

This have me thinking if thinking if my memory settings are or was the culprit. I will test for a longer period when i get some time to.

Thanks for your assistance dude. Much Appreciated.