965 overclocking help

bjvanwash

Distinguished
Nov 27, 2010
33
0
18,530
I'm completely stuck. I've raised vcore, dropped vcore, rasied FSB, loosened timings, etc and I just can't seem to get past 3800MHz. I get a BSOD saying "uncorrectable hardware error" or "A clock interrupt was not received on a secondary processor within the allocated time interval." So I gave up and left it at 3.6GHz for a while.

Then yesterday, I ran prime for about an hour with no issues: 200x18.5 with vcore at 1.440, corsair dominator(CMD4GX3M2A) dual channel(currently unganged) at 1333mhz 10-10-10-24-34-2T @ 1.5v, NB and HT Link @ stock/auto

So today I raised the multiplier from 18.5 to 19 and got a rounding error within 5 minutes. So I thought I'd lower the freq a bit. I then lowered the multi back to 18.5 and then raised the FSB to 204 making it 3774mhz...BSOD "uncorrectable hardware error"

Ok, so I lowered it back down to what I had it at, tried prime again to see if I got the same results as yesterday(1 hour no errors), and within 5 minutes I got "fatal error: rounding was 0.484375, expected less than 0.4" on worker 3.

I'm just so confused as what to do now. Oh, and my temps are fine. Around 29C @ 3.6GHz and 50C on load with 1.440vcore

Thanks in advance.

CPU: AMD Phenom II x4 965 BE 3.4GHz
Motherboard: MSI NF980-G65
RAM: CORSAIR DOMINATOR 4GB (2 x 2GB) DDR3 1600 (PC3 12800) CMD4GX3M2A1600C8
PSU: Corsair TX950
GPU: Asus Radeon HD 6670 1GB
Cooling: Corsair H50 (7 toal fans including case fans, H50 fans, and GPU fan)
Case: Cooler Master Storm Sniper
 
Solution
I'd try two things to stabilize that overclock. One up the vcore a bit first, you're good up to 1.55v so long as temps stay below 55C at full load.

Second thing to try would be to overclock the Northbridge, some people have had success stabilizing high overclocks by raising the northbridge clock to something more fitting for the cpu clock. Keep the cpu/NB voltage 1.3v or less, keep watching your temps closely as raising the cpu/NB volts will bring your cpu temp up as well.

This guide dabbles into matching up northbridge and cpu clocks a bit:
http://www.overclockers.com/forums/showthread.php?t=596023

Disclaimer: When overclocking learn the risks! Everything you try is at your own risk.

bjvanwash

Distinguished
Nov 27, 2010
33
0
18,530
vcore is manually set to 1.346 and running at 1.440 on full load and 1.432 at the minimum. Northbridge voltage is on auto(I think it's between 1.124v and 1.128v) @2000mhz. I'm not sure what LLC is so probably not lol.

I'm currently running 200x18.5=3700mhz, 2000mhz NB, 2000mhz HT Link, 1333mhz RAM with 10-10-10-24-34-2T timings(stock is 9-9-9-24-1T), and I just ran prime for 5-10 minutes before receiving "A clock interrupt was not received on a secondary processor within the allocated time interval."
 

mlcaouette

Distinguished
Apr 25, 2011
1,189
0
19,460
I'd try two things to stabilize that overclock. One up the vcore a bit first, you're good up to 1.55v so long as temps stay below 55C at full load.

Second thing to try would be to overclock the Northbridge, some people have had success stabilizing high overclocks by raising the northbridge clock to something more fitting for the cpu clock. Keep the cpu/NB voltage 1.3v or less, keep watching your temps closely as raising the cpu/NB volts will bring your cpu temp up as well.

This guide dabbles into matching up northbridge and cpu clocks a bit:
http://www.overclockers.com/forums/showthread.php?t=596023

Disclaimer: When overclocking learn the risks! Everything you try is at your own risk.
 
Solution

bjvanwash

Distinguished
Nov 27, 2010
33
0
18,530
Thanks for the replies. I'm going to try messing with my cpu/nb voltage since upping the vcore didn't help in previous tests. Just raised cpu-nb to 1.135 and will see what happens from there.
 

bjvanwash

Distinguished
Nov 27, 2010
33
0
18,530
So I raised the cpu-nb more and more hoping to see some stability and got a bsod after about 6 tests in Prime95 on each voltage increase. Then I tried raising the cpu-nb one last time to 1.16v and when I saved the settings, my computer instantly shut off. Why would this happen? I've read that the cpu-nb voltage can go as high as 1.3v. I didn't bother turning on my computer to see if it would boot or not as it freaked me out, so I just reset the cmos.
 

mlcaouette

Distinguished
Apr 25, 2011
1,189
0
19,460
Some chips just don't like the voltage or it could of been the motherboard.

I recommend resetting everything back to stock than just altering the cpu multiplier and vcore. keep fiddling with those two settings until you at least reach 3.8Ghz stable with load temps >= 55C and vcore >= 1.55v.

Post back with the steps taken and the results.
 

bjvanwash

Distinguished
Nov 27, 2010
33
0
18,530
I guess my setup is a bit tricky. Even though it's a BE, I decided to raise the FSB by itself and adjust the vcore accordingly. So far, I'm running at 3796mhz(stock multiplier) with 222FSB(cpu-z shows 223.3), 1.461 cpu-vcore(HW shows min 1.448v and max 1.472v), 2233mhz HT Link and NB Freq(stock multiplier), and 744.5 DRAM Freq(dual channel) with timings of 9-9-9-24-34-1T @ auto voltage(probably 1.5)

((((((Sorry for so many (parentheses) lol))))))