• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

New Athlon II 635 C3 stepping - Now overclocking the NB

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.
What do you mean by that? I've bumped the NB up to X8. Is X2 > X8?
You lowered the CPU NB multi, so now he means bring it back up two notches, but keep the HT link multi as is (in effect, HT multi will be less than CPU NB multi).

EDIT: I missed the post above me, I did not refresh and this page was loaded since the last hour. We mean the same thing.
 
Ok, so I set fsb to 243, down a few points cause it was unstable.
I dropped the HT to 1000MHz which in cpuz displays as 1215 MHz.
NB has become X10 which displays as 2430 MHz.
 
I was attempting to get 2 different readings from the HT and NB as they seemed to be linked for some reason.

Just set HT to 1.6 GHz in bios; interprets to 1944 MHz in CPU-Z.
NB Freq. still set at X10; reads as 2430 in CPU-Z.

what are your CPU, CPU-NB, and NB voltages

Voltages
CPU - set in bios as +.025 to base of 1.4v for 1.425. However, status page in bios displays same as cpu-z as 1.392v. Apparently, what the bios reads from the cpu's self description is different from what the bios reads from the socket draw.
CPU-NB and NB both are unchanged (read as Normal) but don't display in either status or cpu-z so for now I just don't know.
 
Last edited:
CPU-NB and NB both are unchanged (read as Normal) but don't display in either status or cpu-z so for now I just don't know.
CPU-NB should be in the memory tab. Run through the tabs and you'll find it.

EDIT: I just saw it in one of your previous screenshots.

EDIT 2: I just realized you mean voltages. Sorry. They don't show in CPU-Z, so you have to adjust them one notch up or down to see what the default value can be. They are traditionally lower, 1.1V most likely.
 
Last edited:
Lower than vcore.

I have the same motherboard as you, GA-MA785GM-US2H, and they do display when you move from default so that it will not display "Normal". It will instead display the offset (for example, +0.125V), and right beside it (in gray, if I remember correctly) the effective setting will appear.
 
I was attempting to get 2 different readings from the HT and NB as they seemed to be linked for some reason.

Just set HT to 1.6 GHz in bios; interprets to 1944 MHz in CPU-Z.
NB Freq. still set at X10; reads as 2430 in CPU-Z.

Okay, 1.6 ghz HT in your BIOS = 8x HT multiplier, methinks. Stay with that for now.



Voltages
CPU - set in bios as +.025 to base of 1.4v for 1.425. However, status page in bios displays same as cpu-z as 1.392v. Apparently, what the bios reads from the cpu's self description is different from what the bios reads from the socket draw.

Unless you're suffering killer vdroop, I'm thinking your VID is not 1.4v. It SHOULD be 1.3v (my C2 635 was 1.3v), though you might have a "worse" chip with a 1.35v VID. What VID does CoreTemp report?

Since CPU-Z is reporting 1.392v when you have +.25v vcore set in the BIOS, my guess is that you have a 1.35v VID and that the board is overvolting a tad.

CPU-NB and NB both are unchanged (read as Normal) but don't display in either status or cpu-z so for now I just don't know.

The only way you'll know what those are is . . . hmm, I think AoD can monitor those, but I'm not sure.

The stock voltage for CPU-NB and NB should be the same for all k10.5 chips, so if you would like, I can check on that for you later when I get home from work (somebody else can do that before me if they like). Just be advised that you are getting a good NB speed for running stock CPU-NB and NB voltages, and that as you attempt to overclock your CPU more by raising HTT, you may need more CPU-NB voltage to keep your NB stable (and that NB instability may have caused you some crashes at 248 mhz HTT, for example). If I were you, I'd stop what you were doing now and go for an "isolate and consolidate" approach so that we can stretch the individual parts of your system and try to find out how far you can go with your cores, NB, and RAM individually before attempting a consolidated overclock.
 
I'm just a bit concerned about the NB temp. Like I said in an earlier post I accidentally separated the NB from its heat sink. I don't know if my patch was an improvement or not.
If it were overheating would I be getting some instability?
 
go for an "isolate and consolidate" approach
So if I want to test the NB just drop the cpu multiplier while upping the fsb. Lower the DRAM Freq. to isolate the NB and push the fsb until failure?
Once established with or without a small bump in the NB-v... but what about the cpu-nb-v?
What does that test? Do I just leave that at normal until isolation is complete?
 
I'm just a bit concerned about the NB temp. Like I said in an earlier post I accidentally separated the NB from its heat sink. I don't know if my patch was an improvement or not. If it were overheating would I be getting some instability?

Yes, overheating will cause system instability. You can measure NB temps using HWmonitor.

attachment.php


If the temps are worrying(more than 60 C when stress testing), touch the NB heat sink while stress testing your system. If the heat sink is not hot, remove it, clean and reapply thermal paste and re-seat it.

So if I want to test the NB just drop the cpu multiplier while upping the fsb. Lower the DRAM Freq. to isolate the NB and push the fsb until failure? Once established with or without a small bump in the NB-v... but what about the cpu-nb-v? What does that test? Do I just leave that at normal until isolation is complete?

1. Raise your FSB until fails, increase voltage and check for stability and repeat. Keep an eye on temps and voltages.

2. Increase your NB freq(I can do 2400 Mhz without increasing voltage) until it becomes unstable.

3. Tweak you memory. This is very tricky and gives you very little gains. Pass this one up for the time being. Run this at stock.

FSB> NB freq> Memory is the order to follow to OC.
 
Last edited:
So if I want to test the NB just drop the cpu multiplier while upping the fsb. Lower the DRAM Freq. to isolate the NB and push the fsb until failure?
Once established with or without a small bump in the NB-v... but what about the cpu-nb-v?
What does that test? Do I just leave that at normal until isolation is complete?

You've got the gist of it. The first thing you should probably stress are the cores (lower HT multi, NB multi, and RAM multi, then raise HTT while tweaking vcore as desired), then the NB (lower HT multi, CPU multi, and RAM multi, then raise HTT while tweaking CPU-NB and, to a lesser extent, NB voltages as desired), then . . . you get the idea.

Once you have figured out how far you can push each part of your system, you try to find the best combination of speeds and voltages based on what you have learned. Since you do not have a black edition processor, this can create situations where you may not be able to reach your maximum NB speed or RAM speed while running at the highest core speed you were able to achieve during the isolation portion of your testing. You may also find that attempting to run all three at or near their fastest stable speeds may be impossible. You'll have to make compromises somewhere, more likely than not.

One thing to remember is that CPU-NB voltage will affect the on-die NB's ability to operate with stability at higher clockspeeds (furthermore, keep in mind that when we talk about overclocking the NB, we're talking about the NB integrated into the die of the CPU, not a part of the motherboard). NB voltage will contribute somewhat, but it is less important. Also, it would help to know what temps you are getting at load. The temps HWmonitor shows in your pasted screenshot look good, but they also look like idle temps.
 
BioShock isn't necessarily the best stress-test in the world. It'll cover your GPU (a bit) but you might want to try something like Prime95 or LinX to work on your CPU. For memory, you CAN use Prime95 and/or LinX as well, but Memtest HCI will get down to the bottom of NB/memory instability more directly.
 
Back
Top