Trouble overclocking the Venice 3200+ decently..

Chix4mat

Gawd
Joined
Aug 31, 2003
Messages
793
But maybe I'm not, I dunno. Seems my max stable overclock is 2.4GHz (from the stock 2.0GHz).

I currently run 10 * 240, and everything works great. If I try to increase it, even to 2450MHz, it will boot into Windows, and aftera few minutes, I will get a BSOD, complaining about something.

I have read that people have taken it much higher on air, so I am wondering if it's just me or not. Running currently at stock voltage, increasing it didn't really seem to help. I am only using a stock cooler for the moment, until I end up getting a better one. I also have standard Samsung ram as well (2.5-3-3-7).

Does 2.4GHz seem normal for a stock cooler, or should I be able to take it higher? Any helps appreciated, thanks!
 
Lower your RAM divider.
If it is at 1:1 set it to 5:6 or something else lower.

Yeah, check the link in my sig...
I had to use the lowest divider I could to get that.
 
What you should do is open up two copies of CPU-Z. Move one to the standard default display that shows HTT speed, multiplier, voltage, etc. Another that shows the Memory tab (your current memory speed).

Your memory speed is dictated by the memory controller within the A64 - and therefor if you up your HTT to ramp up your CPU clock speed, you'll also be 1:1 (by default ram divider ratio) increasing your RAM.

If you notch down the ram divider (5:6, 3:4, 2:3, 1:2) you can get your ram back down to a speed which it's much more capable of handling. Chances are if you're running 1:1 at 240 right now, your ram is probably also doing 240mhz or higher - and if it only really works well at stock voltage (you can also try bumping your ram voltage up) the divider will help get it back down to 200-210 which it might find more manageable.
 
Alright, I have just tried many different things, none of which seem to work. I tried the 5:6 ratio, and that didn't seem to do anything either. Here is my CPU-Z:

cpuz.jpg


Maybe someone can make more sense out of this than I can. It could be my crap ram.. even though it was bought at the same time, it's different in very minute details.

It's DDR400 ram, but only operates as DDR333. If I set it all manually to 3-3-3-8 DDR400 as it's supposed to be, the computer won't even boot.

Thanks for the help so far, I appreciate it!
 
Hmm, you're running it on stock voltage? Try bumping the cpu voltage up a little, the stock cooler should handle a slight increase in volts...
 
Chix4mat said:
It's DDR400 ram, but only operates as DDR333. If I set it all manually to 3-3-3-8 DDR400 as it's supposed to be, the computer won't even boot.

That's the thing though.... it is running at 200mhz all ready. Look at CPU-Z. You have to make sure you are in control of all aspects of your hardware when you're overclocking, otherwise there could be any number of reasons why your overclock is failing and we don't know where to start. Unfortunately you can't isolate just CPU and overclock that alone - everything has to be balanced out.

So if your RAM is default at 3-3-3-8 200mhz, then you'll notice by looking at CPU-Z that it is all ready overclocked. It's running 2.5-3-3-7 at 200mhz. Its no surprise that if you up your HTT to say 250mhz, your RAM gives errors and causes a BSOD because now it is running at 208mhz 2.5-3-3-7 (250mhz * 5 / 6 = 208mhz)

Your options now are the same as any overclocking guide will tell you. Loosen the timings or apply a larger divider. Lets just say for a second that your chip will reach 2.7ghz. The settings for that would be 270mhz, and if you then apply a divider of 2/3 you will have 180mhz RAM. This will then obviously run fine at 2.5-3-3-7, or perhaps even 2.5-2-2-7 or 2-3-3-7, or whatever. Thats where you tweak.

Of course you have other options as well. If you run 300mhz HTT, you can lower your multiplier to 9x and still be running a 2.7ghz CPU. Then, by running a 2/3 divider, your RAM will be at 200mhz and you can run 2.5-3-3-7 again.

But at this point its up to you.

edit: I wanted to clarify something because I might know where you are confused. In your memory config area in your BIOS, if you see a place to set your memory at 200mhz, 166mhz, 133mhz, and 100mhz, then that is actually your divider. I don't know why they are labeled this way because its misleading, but 200mhz = 1:1, 166mhz = 5:6, etc. Its always correct if you run at STOCK settings. I.E. at stock 200mhz, setting it to 200mhz(1:1) will give you exactly that: 200mhz, because thats what your chip is at.
In other words, if you went into the memory config page and tried to, as you say, set your RAM to 200mhz, then you are indeed setting a 1:1 divider which means you were trying to run your RAM at 240mhz like your CPU is.
 
Yeah, still confused a little. How exactly does setting the memory at 200MHz make it operate at 240MHz? It's *because* my FSB is at 240? If I set it at 200, which appears to be 1:1, it actually *not* 1:1?

My mobo has these settings:

DRAM Frequency Set:
120 (DRAM/FSB: 3/05)
133 (DRAM/FSB: 2/03)
140 (DRAM/FSB: 7/10)
150 (DRAM/FSB: 3/04)
166 (DRAM/FSB: 5/06)
180 (DRAM/FSB: 9/10)
200 (DRAM/FSB: 1/01)
Auto

I gotta run out for now, but I'll play with it more when I get back. Thanks a ton for the help, that's great info. Couple beers may clear my head and make me clue in :)
 
Chix4mat said:
Yeah, still confused a little. How exactly does setting the memory at 200MHz make it operate at 240MHz? It's *because* my FSB is at 240? If I set it at 200, which appears to be 1:1, it actually *not* 1:1?

My mobo has these settings:

DRAM Frequency Set:
120 (DRAM/FSB: 3/05)
133 (DRAM/FSB: 2/03)
140 (DRAM/FSB: 7/10)
150 (DRAM/FSB: 3/04)
166 (DRAM/FSB: 5/06)
180 (DRAM/FSB: 9/10)
200 (DRAM/FSB: 1/01)
Auto

I gotta run out for now, but I'll play with it more when I get back. Thanks a ton for the help, that's great info. Couple beers may clear my head and make me clue in :)

The reason that even through your ram (by the bios settings) may show 200mhz, or even 166mhz yet be running at higher is because the speed of the HTT (when overclocking the CPU) also increases the speed of the ram. Your ram divider does look to be set lower (it would by default be 1:1 would it not?). Looks to me like you've got it set at 1:2 (100) right now. The first option in your list.

And it WOULD be 1:1. Meaning if your HTT was 200, your ram would be 200. If your HTT was 240, your ram would be 240. Not exactly like that (as the equation factors in more than just HTT:RAM) but it's an example.
 
yes, I agree..it's probably his ram..and that would be a bummer if yor venice can only get 2.4 ;(

my clawhammer 3200+ with 1mb cache can get 2.3 :) woot woot!
 
Try that 133 (2:3) divider then keep raising the HTT till you get your ram to 200mhz again.
That cpu should handle it fine, I can get this thing up to 2.4ghz easily but the RAM can't handle that very well...
 
Borgschulze said:
Try that 133 (2:3) divider then keep raising the HTT till you get your ram to 200mhz again.
That cpu should handle it fine, I can get this thing up to 2.4ghz easily but the RAM can't handle that very well...

As far as I can figure, 2:3 would be the FSB at 300, that would make the ram 200MHz. Here's what I mean about the minute differences in my RAM, maybe someone can tell me if this matters. I bought these two sticks at the same time.

wataf_ram.jpg


I've tried everything that everyones said, but I BSOD no matter what. I tried numerous configurations, from 2.5GHz - 2.6GHz specifically. It will always seem to load Windows fine, but will always BSOD relatively quickly.. or even quicker if I load some type of test.

Not sure if it's my cooler, my memory, or what. PITA though :-/
 
did you try increasing your dram voltage?

I'm relatively new at this and didnt want to mess with dividers.

I'm running the same cpu and mobo with the following specs

htt 250mhz
cpu 1.45v
ldt 1.16v
nb 1.48
dram 2.68
crucial ballistix pc3200(some of the worst ram for the ultra-d) at 2-3-3-7
 
Chix4mat said:
I've tried everything that everyones said, but I BSOD no matter what. I tried numerous configurations, from 2.5GHz - 2.6GHz specifically. It will always seem to load Windows fine, but will always BSOD relatively quickly.. or even quicker if I load some type of test.

Yeah.... without some data its hard to troubleshoot. If possible, maybe you could boot in at an unstable 2.5 or 2.6 and quickly save two CPU-Z shots just like you did before. And I never thought about temps before now, but, yeah... we should have an idea where those are at.

And the differences in your two sticks of RAM won't be a problem. You just have to watch your speeds in relation to the slower stick (200mhz 3-3-3-8). Meaning if they go over that, one of your sticks is still being overclocked even if the other isn't.

edit: This might help you. If you create a new shortcut to CPU-Z, and edit the properties of it, you can add the parameter "-file=C:\system" or something like that to the 'Target' line. What it will do, when you run it, is create a text file called 'system' in your C:\ directory containing all the data we need. Then when you reboot and are stable, you can copy the 'CPUID Output' and 'Chipset' data to us here. I'm only suggesting it cause its a single click solution and in a couple seconds its saved to your hard drive. Might be easier to get it before you BSOD.
 
RawsonDR said:
edit: This might help you. If you create a new shortcut to CPU-Z, and edit the properties of it, you can add the parameter "-file=C:\system" or something like that to the 'Target' line. What it will do, when you run it, is create a text file called 'system' in your C:\ directory containing all the data we need. Then when you reboot and are stable, you can copy the 'CPUID Output' and 'Chipset' data to us here. I'm only suggesting it cause its a single click solution and in a couple seconds its saved to your hard drive. Might be easier to get it before you BSOD.

Neat! I didn't know that. I'll do that later today infact.
 
Rawson, thanks for the great advice. Luckily, I've been able to at least boot, but will keep that in mind for the future. Now, I have a new OC, and it seems stable.. but this was done without modifying the RAM voltages or properties at all.



The hottest the CPU got was 50deg Celcius, so I am impressed with that alone. Course, I didn't run any tests for longer than 15 minutes, but even so.

Is there anything else I should change, or try out, or should I just leave it at that?
 
Chix4mat said:
Rawson, thanks for the great advice. Luckily, I've been able to at least boot, but will keep that in mind for the future. Now, I have a new OC, and it seems stable.. but this was done without modifying the RAM voltages or properties at all.



The hottest the CPU got was 50deg Celcius, so I am impressed with that alone. Course, I didn't run any tests for longer than 15 minutes, but even so.

Is there anything else I should change, or try out, or should I just leave it at that?

That looks really good to me. The ram timings are tight enough to max the most of your mismatche ram, but tight enough that they're still going to perform - as far as I can see. Nice clock speed, looks to be stable.

If I were you, I'd bench and stress the snot out of it now, perhaps with both higher and lower voltages. Maybe a bit of "warm up" time and you can even push it a wee bit higher than 2.7 - but you've gotten yourself pretty close to the air-cooled ceiling with the ram that you have.

Nice work.
 
Cool, thanks.

I also just realized that I haven't flashed my BIOS to latest version yet, which apparently adds better Venice support. I doubt it came with the latest version already, so I'll also take a look at that.
 
Back
Top