7900GS-Clock too high?

"oldwolf" <1.RemoveThis@1.com> wrote in message
news:4681fb9e$0$7925$afc38c87@news.optusnet.com.au...
>
> "don't look" <don't look.RemoveThis@worldnet.att.net> wrote in message
> news:d7lgi.231864$p47.44699@bgtnsc04-news.ops.worldnet.att.net...
>> I let the drivers detect optimal settings. Came up 566(450 default) core
> and
>> 1540(1320 default) mem.What do you all think?
>>
>>
> Seems OK. Thats what Ive read on the net, they are good clockers. I got
> one
> not long ago, and am taking it up very slowly, play few games for a week
> then clock it some more, rinse and repeat.
> As always, run a couple of stress tests, and see how she pulls up.
> Back it off to 550/1500 if you want to play it safe.
>
>

I ended up with 555/824. 1500 is probably way too high. No way does a card
pull double in different rigs.
 >> Stay informed about: 7900GS-Clock too high? 

The driver really has no idea what the optimal settings are, since it
doesn't do any artifact checking. Visual artifacts and lockups are the only
reliable indicators for overheating.

Use the "fuzzy cube" artifact checker in ATiTool here (works on nVidia
cards): http://www.techpowerup.com/atitool/ . Increase the core and memory
clocks from default 5-10 MHz at a time, check for artifacts at each step.
Once you encounter artifacts, back down a notch.

--
"War is the continuation of politics by other means.
It can therefore be said that politics is war without
bloodshed while war is politics with bloodshed."


"don't look" <don't look.TakeThisOut@worldnet.att.net> wrote in message
news:d7lgi.231864$p47.44699@bgtnsc04-news.ops.worldnet.att.net...
>I let the drivers detect optimal settings. Came up 566(450 default) core
>and
> 1540(1320 default) mem.What do you all think?
>
>
 >> Stay informed about: 7900GS-Clock too high? 

"don't look" <don't look RemoveThis @worldnet.att.net> wrote in message
news:pbDgi.125772$Sa4.101492@bgtnsc05-news.ops.worldnet.att.net...
> Thanks,Pretty much what I was thinking.So far I've run imto trouble with
> Google Earth Pro. Crashes to desktop. But Quake 4 is running
> perfect.Google
> Earth is running DirectX and Quake4 is running Open GL.Wonder if that
> makes
> the difference.

Possibly something that could be cleared with the latest version of DirectX.
(Microsoft updates DirectX every two months or so, without rolling the
version number...)

Last time I tried Google Earth free (about a year ago), the app had an
OpenGL mode.

> BTW,I can't get Google earth to show buildigs in NYC,only the shapes all
> in
> white. Dang,can't think of the graphics term for that.

Last time I tried Google Earth free (about a year ago), the buildings were
all in white as well. I think this is intentional (otherwise Google will
have to stitch together photos of all the buildings to create textures).

--
"War is the continuation of politics by other means.
It can therefore be said that politics is war without
bloodshed while war is politics with bloodshed."
 >> Stay informed about: 7900GS-Clock too high? 

Thanks,Pretty much what I was thinking.So far I've run imto trouble with
Google Earth Pro. Crashes to desktop. But Quake 4 is running perfect.Google
Earth is running DirectX and Quake4 is running Open GL.Wonder if that makes
the difference.
BTW,I can't get Google earth to show buildigs in NYC,only the shapes all in
white. Dang,can't think of the graphics term for that.

"First of One" <root RemoveThis @127.0.0.1> wrote in message
news:o4CdnRilveepch_bnZ2dnUVZ_jqdnZ2d@giganews.com...
> The driver really has no idea what the optimal settings are, since it
> doesn't do any artifact checking. Visual artifacts and lockups are the
only
> reliable indicators for overheating.
>
> Use the "fuzzy cube" artifact checker in ATiTool here (works on nVidia
> cards): http://www.techpowerup.com/atitool/ . Increase the core and memory
> clocks from default 5-10 MHz at a time, check for artifacts at each step.
> Once you encounter artifacts, back down a notch.
>
> --
> "War is the continuation of politics by other means.
> It can therefore be said that politics is war without
> bloodshed while war is politics with bloodshed."
>
>
> "don't look" <don't look RemoveThis @worldnet.att.net> wrote in message
> news:d7lgi.231864$p47.44699@bgtnsc04-news.ops.worldnet.att.net...
> >I let the drivers detect optimal settings. Came up 566(450 default) core
> >and
> > 1540(1320 default) mem.What do you all think?
> >
> >
>
>
 >> Stay informed about: 7900GS-Clock too high? 

>
> I ended up with 555/824. 1500 is probably way too high. No way does a
card
> pull double in different rigs.
>
>
He is doubling the memory speed, same as most people.
which would mean you are running at 1648 mem speed.
Im currently at 750 which would give me 1500mem speed.
 >> Stay informed about: 7900GS-Clock too high?