First A64 OC Attempt only 2070Mhz???

[BALISTX]

Well I decided to start my A64 OC. Here is what I did.

First went into the BIOS and set the the mem timing from auto to stock settings, saved and rebooted, ran good.

Next went in upped the FSB to 210 and set the memory divider to 1/02 saved rebooted and go to Windows logon screen and rebooted itselfs, so then I went back into the BIOS set the FSB to 205, loaded into Windows, ran Super PI worked. Then upped the FSB to 207, booted into Windows ran Super PI worked. Upped the FSB to 208, got to Windows login screen crashed. went back in set the FSB to 207, set the mem divider to 9/10, loaded into Windows ran Super PI worked, that is where I am currnetly at.

Any ideas on why it wouldn't go to 208?

[Eldonko]

Try 1:1, sometimes a few of the dividers work weird and cause instability. U sure all your mem settings are good? Did you change LDT to 4x?

[BALISTX]

Yep mem settings are good. Set the LDT to 4x

current mem divider i'm on now is 9/10 running at 188

[Amon]

Locking up, crashing, or restarting when loading or using Windows is an obvious sign of memory limitation.

Loosen up your memory timings. I would recommend to simply dock them back to your BIOS' "AUTO", or loosen them manually to something like 3-3-3-6 or 3-3-3-7. You can also reduce your HyperTransport link down to 800MHz or less, then set the Bus:RAM divider to 5:3 or 4:3.

If that boots stably, raise the memory voltage to 2.8v (you can keep it at 2.8v 24/7 for all speeds for the Platinum editions). Finally, you can proceed to increase the system bus.

Your Venice should be able to pull 215MHz at stock 1.4v Vcore. 1.4750v Vcore is the highest I recommend going, which is good for about 235MHz+ system bus; 1.5v for 260MHz and beyond! My San Diego and your Venice are identical processors, bar L2 cache and maybe HTT link. The San Diego is a bit sensitive to heat, pretty much giving in at 50 centigrade.

[Eldonko]

Drop your cpu multi and retest to see if it's the mem.

[Supergrover]

Originally Posted by Eldonko

Drop your cpu multi and retest to see if it's the mem.

QFT As both posters said it sounds like memory, do you know the limit on your ram yet? I find the limit of my ram first ( or cpu first it doesn't matter ) drop the multi, throw 2.7v @ least ( I had mine @2.95v for years but whatever ) run stock timings or loosen them abit. I wouldn't go 3-3-3-8 yet but drop to 2.5 if your inclined. so start raising the FSB 1:1 5mhz @ a time if it boots to dows, run super pi, if it passes raise the FSB again. if it fails to boot or fails super pi then give it 2.8v if that fails loosen timings, once your @ the limit of your ram then you do the same thing with you cpu, raise the multi and drop to your lowest divider.
Now your ready to overclock, it rarely works perfect , @ least for me, now you know the "range" of what your hardware can do, now start fiddling to get the best clocks out of both cpu/ram, this isn't something that happens overnight. And thats the best part of overclocking, the little tweaks, the mass of notes on different settings scattered amongst my desk

[Eldonko]

Is that kit TCCD?

[BALISTX]

Originally Posted by Eldonko

Is that kit TCCD?

No, they are Aeneon or Infineon IC's in them according to OCZ

[BALISTX]

Originally Posted by Supergrover

QFT As both posters said it sounds like memory, do you know the limit on your ram yet? I find the limit of my ram first ( or cpu first it doesn't matter ) drop the multi, throw 2.7v @ least ( I had mine @2.95v for years but whatever ) run stock timings or loosen them abit. I wouldn't go 3-3-3-8 yet but drop to 2.5 if your inclined. so start raising the FSB 1:1 5mhz @ a time if it boots to dows, run super pi, if it passes raise the FSB again. if it fails to boot or fails super pi then give it 2.8v if that fails loosen timings, once your @ the limit of your ram then you do the same thing with you cpu, raise the multi and drop to your lowest divider.
Now your ready to overclock, it rarely works perfect , @ least for me, now you know the "range" of what your hardware can do, now start fiddling to get the best clocks out of both cpu/ram, this isn't something that happens overnight. And thats the best part of overclocking, the little tweaks, the mass of notes on different settings scattered amongst my desk

Not quite understanding.

So should I drop my CPU multi down from 10x to 9x?

Leave my mem divider @ 1:1?

So I'm increasing my memory MHz 5 at a time or the FSB 5 MHz at a time?

Up my voltage on the memory to 2.7 and should I leave my ram settings on auto?

So far on auto they show at 2-3-2-5

Here is what i've done so far it's been a mess.

I tried loosing the timings to 2.5-3-3-7 and left my mem div @ 1:1. I had my FSB to 208, wouldn't boot, drop it back down to 205 still wouldn't boot. Put everything back to auto for the memory and dropped the FSB back to 200 it booted.

[Eldonko]

Basically you have to test the max of CPU and mem separately so you know where the instability is coming from. To test mem max, drop your cpu multi, to test cpu max, use divider.