Flashing Polygons

[Mekhollandt]

I recently bought an Albatron 6800nu, and was able to unlock the extra pipes for a 16x1, 6vp configuration without any hassle whatsoever. I ran 3dMark2003 a few times without any overclocking just to make sure it was stable, and came out with great results--not a single problem I could see while instensely staring at the screen each time .

When I started overclocking, Rivatuner happily gave me a 375/875 clock, which I in turn benchmarked, once again with 3dMark2003. Everything ran fine with the program, except for the scene in 'Mother Nature" where the turtle is walking away from the river. For some reason, and allow me to emphasize that it is in ONLY this part of the benchmark, the turle's polygons flash all over its body.

Now, I'm aware of the more common errors that occur when the core or the memory are overheating (flashing pixels and artifacts, respectively). What exactly would these polygons be related to? I would like to guess memory, but I'm not sure.

[Dr. Vodka]

flashing polygons and snow: memory
missing polygons: memory
other types of arctifacts like checkerboards, lines, etc: gpu.

You clocked too much your card´s memory, bring it back 5-15 mhz and look.

and you only see arctifacts there because:
the mother nature game test in 3dmark01se is the only dx8 one, it is the only that uses pixel shaders (ALOT in the water) and vertex shaders ALOT too. It seems that the turtle part is the heaviest one, and makes your card feel "bad" there.

[TheGamer]

Just decrease your clock speeds by 20-25 Mhz and the polys' should go.

[HanShot1st]

that particular moment in '03 with the turtle is pretty much the most intense moment in 3d benching in terms of causing memory artifacts with the possible exception of game test one in '05.
My motto is if I can get past that turtle moment without a lockup or crash, all is good.
Scale back the memory FIRST and see if that helps before you decrease th core clock.