overclock speeds

i have a 8700mGT and im wondering if anyone can suggest any speeds for me:?

 

Nope every gpu regardless if same make and model will have a different limit.

 

overclock using Ntune or Rivatuner. Run ATI tool stress test to look for artifacts, check the temps and repeat until you get a stable overclock with no delta artifacts in ATI tool.

Of course check in games too for artifacts. Simple as that.

I think I had mine 8700m GT´s SLI up to 700 on the core and shaders were up there too very high stable.

 

you could start with 730/1700/900, then see if you can push it higher...i have mine at 745/1800/975.

 

should you keep the core/shader linked?

what drivers are you guys using? im on 177.79 still and when i run farcry2 it says my drivers are out of date.

thx

 

there is no need in keeping them linked. just use rivatuner.
i´m using 180.43 drivers.

 

i say use Ntune and try the clocks in my sig and keep increasing in intervals of 50. Then when you start artifacting start decreasing in interval of 15.

GOOD LUCK AND WELCOME TO THE OC CLUB. LOL

 

Note, my 8700m GT maxed out at 800/1600/1000, but wouldn't run 3dmark06.
(it ran all other games, but 3dmark06 would crash)

778/1556/938x2 ran for everything at 69C so that's what I left it at for almost a year and a half.

Note, my x205 died from "drinking too much" and not GPU heat.
(the laptop wasn't to blame, it was just in the wrong place at the wrong time)


One word of warning... EASE your laptop's clocks up.
Do NOT set it to the maximums I listed... ease it up slowly by 10% increments. You might get even higher than I did stable, but you might also get lower.

Start with 700/1400/800... pretty sure every 8700m will run this pretty easily. Run benchmarks and test heat and record it.

Move to 766/1532/900x2 (play with RAM later, most of it is limited at 900-1000x2)

Ease core up and you will hit your limit quickly, then ease shader up once you ge core max stable speed. (usually shaders can go up furthur, but mine liked corex2)

After core and shaders max reached, you can play with RAM max between 900-1000 start at 933, 966, and try 1000 if 966 works.

ANY large heat fluctuaton or artifiacts or odd behavior of any kind should mean you accept it as FAILED.

After I find the max on any overclock, I bump her down one notch to account for human error.

 

hey thanks a lot for the info - i was wondering what the "x2" means though next to the memory and if it requires me doing something different

also... whats a good way to benchmark?

 

Just that the memory is x2. So for instance 900 memory overclock is actually 1800 memory.

 

3dmark06 works for a stress benchmark wonderfully.
So does anything else frankly.
Pick your favorite game benchmark if 3dmark06 doesn't work for you.

I use 3dmark06 for stress tests as it tends to be find flawed OCs pretty well.

All that matters is that you run the GPU and CP flat-out to get a realistic if it works at those clocks for extended periods.

x2 refers to double-data-rate (DDR) effective clock rates as compared to actual clock rate.
Some people will mistake 800 native for the DDR2 speed of 400x2 (800 effective) as compared to the native 800x2 (1600 effective) of DDR3.

 

I'd say that's way too high of increments. If you're going by 50 MHz, and your card's limit is 605 MHz core, and you see it's fine at 600 MHz and then try 650 MHz, you're way over what your card can handle. Same with 10% - that's usually somewhere in the 40 MHz-60MHz range these days - you're going quite far over what the card can handle.

While it is fairly safe to go by 25 MHz for the first increment or two, once you start getting a decent overclock (varies by card) I'd increment by only 10 MHz or even 5 MHz (what I'm incrementing by myself these days). Much less risk of entirely burning out the card by going over, since you won't be more than 4900 KHz too fast.

It does take longer to figure out what your maximum is this way, but it's better than a useless card. If you don't have the patience to test it 20 times in a day, just do like I do and increase it every few weeks by 5 MHz or so. It'll give you more opportunity to spot any artifacting that way than by running a 10-minute benchmark, as well.