Overclock.net banner
1 - 12 of 12 Posts

·
Registered
Joined
·
2,591 Posts
Discussion Starter · #1 ·
SO currently stable I'm at 4.01ghz with 1.3 vcore. VTT on auto which results in 1.23v and Dram at 1.5v. Been this way for a couple months.

I put in my tests hdd loaded windows and aida64 with the hopes of going a bit higher but I am absolutely stuck at 4.0ghz. I keep getting a 124 bsod the instant I start a stress test at anything higher. Even raising the bclk by more than 2 results in a bsod at any voltage. Now I know bsod 124 means more vtt. I tried raising it by +25mv increments as high as +175 which results in 1.39v. No change. I know large amounts of ram can be an issue I attempted (just as a test) removing one stick for 8gb in dual channel and no change. Tried vcore up to 1.35 no change.

I understand that my chip doesn't seem to be one of the best oc'ers but it seems like I should be able to get a little higher.

I want this to last a long time so I'm not going over 1.35 but is it too much to expect anymore?
 

·
Registered
Joined
·
229 Posts
Are you using 6 sticks or 3 sticks of RAM? It might also help to post your complete BIOS template. I have a similar setup so I could provide you with plenty of help. For starters, move your clocks to something stable and start stress-testing with LinX. If you pass 10 minutes, raise your multi/BCLK. If it BSoD's, refer to the following list for the proper procedures. Note that it's much easier to OC with the multi as opposed to the BCLK on the 980x.

0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
 

·
Registered
Joined
·
2,591 Posts
Discussion Starter · #3 ·
Ok currently stable settings are:

Mother Board ( EVGA X58 FTW3)
Bios version ( 76 )
CPU ( 980x )
CPU Cooler (Corsair H70)
Memory ( Corsair Vengeance 3x4gb 9-9-9-24 )
PSU (Antec TPQ 850 )
Operating System ( Windows 7 64 Ultimate )

Frequency Control
CPU Clock Ratio ( 30X )
CPU Host Frequency (Mhz) ( 134 )
MCH Strap ( Auto )
CPU Uncore Frequency (Mhz) (Auto 2406Mhz { 18X } )
Spread Spectrum ( Disabled )

Voltage Control
EVGA VDroop Control ( enabled)
CPU VCore (1.3 )
CPU VTT Voltage (Auto 1.28v)
CPU PLL VCore (Auto 1.8v)
QPI PLL Auto 1.1v
DIMM Voltage ( 1.5 )

Ok I think thats everything important.
 

·
Registered
Joined
·
229 Posts
I'd suggest raising your Uncore to ~3000MHz. I know Gulftown can run at 1.5x RAM, but I've found much greater stability at one or two steps below 2x. You might also try tossing 1.65v into your RAM, regardless of what they're rated at. 0x124 refers to IMC errors, so those adjustments may help.
 

·
Registered
Joined
·
2,591 Posts
Discussion Starter · #5 ·
Quote:
Originally Posted by mymlan;12977838
I'd suggest raising your Uncore to ~3000MHz. I know Gulftown can run at 1.5x RAM, but I've found much greater stability at one or two steps below 2x. You might also try tossing 1.65v into your RAM, regardless of what they're rated at. 0x124 refers to IMC errors, so those adjustments may help.
I tried 1.6 on the dram and there was 0 improvement but I'll try 1.65 and try raising uncore I was wondering about that but I assumed that lower frequency would only be better/less stress. I just have it on the auto setting right now which puts it at 1.5x ram
 

·
Registered
Joined
·
583 Posts
@OP This is kind of basic as I am still kind of new to overlocking, but maybe it could help!

I had trouble finding a stable OC over 4ghz with speedstep/turboboost on. I opted to turn them off and I was running 4.27 @ 25x171 with 1.32v HT on, speedstep off. My QPI is actually set to around 1.22 iirc.

For summertime, I am sticking at 4.03 @ 1.26v.

(I realize we don't have the exact same chip, but my buddy has a 980x with my mobo and we are able to use very similar settings)
PS: my 2nd 6870 is coming on Monday
smile.gif
 

·
Registered
Joined
·
2,591 Posts
Discussion Starter · #9 ·
Ok I was able to hit 4.2 with

vcore 1.34
vtt +125mv which shows ~1.33 in aida64
dimm voltage to 1.575 which shows ~ 1.599 in aida64
speedstep C1E etc on.

I think this will be it everything is just under the safe 1.35 intel spec.

On a side note I'm now on an odd multiplier (31x136) and I was noticing that speedstep seems to be working better and is now down clocking correctly. Before it wasn't always hitting the minimum value at idle.
 

·
Registered
Joined
·
2,591 Posts
Discussion Starter · #11 ·
Quote:
Originally Posted by mymlan;12986041
Sounds good, but can it stress? Give it a few hours in LinX. I know it may seem overkill, but it is essential for a 24/7 clock.
It passed 30 minutes running prime95 and aida64 stress test simultaneously and 3 hours of prime95. This is my usual testing system and I've never had problems after it passed.
 

·
Registered
Joined
·
2,591 Posts
Discussion Starter · #12 ·
After further tests I think I'm going to stay at 4.1. The benchmarks between 4.0 and 4.1 were more substantial than 4.1 to 4.2. All three were stable with their respective voltages but 4.1 is a happy medium with 1.33v vcore 1.34v vtt 1.611 dimm. Speedstep works best at 4.1 too.
 
1 - 12 of 12 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top