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

Overclocking an i7 920

Joined
Jan 6, 2011
Messages
40
Motherboard - GA-EX58-UD3R

RAM = http://www.compusa.com/applications/SearchTools/item-details.asp?EdpNo=5507377&sku=C13-6152

I have 3 sticks of those running tripple channel.


Bios Settings.

CPU Clock Ratio 20x
CPU Frequency 4.00GHz (200x20)
QPI Clock Ratio Auto (I had it set to x36 then changed it to Auto and it has made a difference so far)
QPI Link Speed 7.2GHz
Uncore Clock Ratio x17
Uncore Frequency 3400MHz

BCLK Frequency 200
System Memory Multiplier 8.0

CPU VCore 1.325
QPI/Vtt Volts 1.315
IOH Core 1.30 (This setting I never changed until yesterday and I think it made a difference. This setting was mentioned in the article from Voicy but not in the guide provided by Gigabyte)
DRAM Volts 1.66v

CAS - somehow by default it was at 8/20 I changed it to 8/24 and tried 9/24


As of right now, I ran Prime95 for 2 hours and no errors, I also set Prime95 to test with 1 thread while setting the memory to 6100MBs and ran for over an hour with no errors.

I then Ran LinX with the default settings of 16331 for the problem size and 2048 for the memory but increased it to run 10 times and ran with no errors.. This was the program I was getting errors on earlier this week.

I then ran Memtest in windows. I ran 2 instances at the same time using 1500MB of RAM in each instance and it ran for over 200% coverage with no errors.

I ran Fraps, GPU-Z to record highest temps, Real Temps to record max temps and played MWII for well over an hour and no crashes at all.


Everything seem fine and dandy until yesterday, not even 4 rounds deep into MWII MP, it locks up, no BSOD, no hard crash like before, but a lock up with this loud repetitive sound. I had to do a hard boot and then I ran those tests again.

This time Prime95 had one out of 8 workers stopped. it ran 6 tests in 11 minutes with 1 error.. Ran 2 different tests in OCCT and they passed, then tried Prime again and the same worker stopped.

These are the 2 sources I used to help with the OC

http://www.overclockers.com/3-step-guide-overclock-core-i3-i5-i7/

http://www.tweaktown.com/news/10827/gigabyte_shows_how_to_overclock_i7_920_cpu_to_4ghz/index.html

The gigabyte link has a "grab a guide"


Can anyone tell me if my MoBo isn't meant to have the RAM OC'd? is it the IMC arguing with the RAM frequency? Does the CPU and the RAM not getting along to cause these lockups and BSODs before?

Please advise... I am at a loss.
 
I wish, I will check this evening to see if I have the latest drivers but I don't think it has anything to do with the RAM, or 1 worker in Prime erroring out..
 
Nope, run 4 ghz 24/7 on my 920. I do have different ram though.
 
I find it easier to run at 190x21 than 200x20. Also that qpi link speed is really really high. Also it seems you are running the ram at higher than rated speeds, 1600mhz vs 1333mhz while still using relatively tight timings. given all this it would be hard for me to find the problem, but it is worth mentioning that windows memtest doesn't always find what a dos boot memtest will.
 
Last edited:
His ram is 1333. I'm at work so I can't check my mobo settings.
 
I find it easier to run at 190x21 than 200x20. Also that qpi link speed is really really high. Also it seems you are running the ram at higher than rated speeds, 1600mhz vs 1333mhz while still using relatively tight timings. given all this it would be hard for me to find the problem, but it is worth mentioning that windows memtest doesn't always find what a dos boot memtest will.


Reason for the QPI link speed is because its either x36 which is 7.2Gb or x44 (I think.) or x48 (I think again.) or Auto (which will default it to 7.2 because the Bclock is at 200

however at 190x21, will I achieve 4.0GHz?

I've tried setting the CAS at 8/24 and 9/24, shall I try 9/24 again? I also left the other timing setting at 1T.

One other thing about the RAM, the guy in the Gigabyte guide from the link in the first post, he used Corsair 1333MHz and achieved 1600 OC, his was the XMS while mine is the Dominator series.. one other thing I noticed also is when he ran Memtest at boot, his timing was set to 9-9-9-25.....
 
Look on the label. You will see a code called the S-spec. If it says SLBCH, you have a C0. If it says SLBEJ, you have a D0.

CO's were the first out DO's are newer and tend to overclock easier with less voltage than the CO's.
 
Look on the label. You will see a code called the S-spec. If it says SLBCH, you have a C0. If it says SLBEJ, you have a D0.

CO's were the first out DO's are newer and tend to overclock easier with less voltage than the CO's.

Oh God again.... Label, does this mean I need to take off my LC and look at the chip? Im so slow today, what do you mean label?
 
Set your QPI settings as low as they can go. If you read this, one can see that you don't want QPI approaching or above 4GHz.

As well, there's really no reason to leave hyperthreading on. It just makes more heat and limits your overclock for no real-world performance gain.
 
Set your QPI settings as low as they can go. If you read this, one can see that you don't want QPI approaching or above 4GHz.

As well, there's really no reason to leave hyperthreading on. It just makes more heat and limits your overclock for no real-world performance gain.


I have turbo boost disabled but Im not sure about hyperthread... I will check again when I get home but I think I have multi-thread enabled...
 
Set your QPI settings as low as they can go. If you read this, one can see that you don't want QPI approaching or above 4GHz.

As well, there's really no reason to leave hyperthreading on. It just makes more heat and limits your overclock for no real-world performance gain.

There's also no real reason to turn it off either.
 
just checked bios and multi-threading is enabled.. when you highlight this setting, it says to the right that hyper-threading is on if enabled..
 
Look on the label. You will see a code called the S-spec. If it says SLBCH, you have a C0. If it says SLBEJ, you have a D0.

CO's were the first out DO's are newer and tend to overclock easier with less voltage than the CO's.


Ok, I ran CPU-Z and it says stepping = 5 Revision = D0 so I guess I have the newer one then.
 
Back
Top