PDA

View Full Version : 6800GT Problems artifacts? in timbury & far cry


TryingHard
01-19-05, 07:00 AM
What is wrong with my PNY 6800GT card?

I ran atitool last night for over an hour with no artifacts, but when I run timbury, clear sailing and far cry I get strange effects on my screen. (see screen shot of timbury)

My system:
P4C 3.2GHz
PNY 6800GT @ 350/1000 temps 46c/62c
1GB Corsair pc4000
WinXP Pro SP2
Enermax 470W PSU
Creative SB Audigy LS
17in LCD Flat Panel (25ms)
Lots of cooling and no over heating.

I have tried different drivers from 66.xx up to 71.40 but still problems persist and I always clean out the old drivers before installing the new ones.

Please can anyone help me?

MX/MX400
01-19-05, 08:45 AM
The Timbury demo isn't supposed to look like that!

Morn
01-19-05, 08:46 AM
Try on another computer. If it fails there too. It's RMA time.

TryingHard
01-21-05, 06:59 AM
I think I've found my problem.........

My FSB is overclocked from 200 to 240 and when I drop it down to 235 most of the artifacts? disappear and when I drop it down to 230 they all disappear. I've tested my memory (Corsair Twinx1024 4000PT) with memtest and it passed ok. My CPU was very stable at 240 FSB (3.2GHz @ 3.8GHz) so maybe it's a problem with my overclocked FSB messing up the AGP?

Any comments gratefully accepted.

|MaguS|
01-21-05, 07:19 AM
Do you have AGP Lock on your Motherboard? Thats probably the issue.

TryingHard
01-21-05, 07:26 AM
Do you have AGP Lock on your Motherboard? Thats probably the issue.

All I can find is an option for CPU only or CPU/AGP and I have this set to CPU only.

ViN86
01-21-05, 12:07 PM
i agree. agp lock would most likely solve the issue. if your bios allows easy overclocking, im sure its a feature. check your book or email the mobo/bios manufacturer.

TryingHard
01-27-05, 09:09 AM
AGP is definitely locked at 66.66/33.33

It's looking more and more like a memory or motherboard problem.

Will post the fix if ever I get one.

russo121
01-27-05, 02:17 PM
AGP is definitely locked at 66.66/33.33

It's looking more and more like a memory or motherboard problem.

Will post the fix if ever I get one.


Disable PAT... and try again....