So I'm going to try to overclock my GTS 250 . I was wondering when I should stop incrementing the clocks? I read a guide a while back saying I should stop when games start to crash, or if "artifacts" (I don't know what these are) start to appear. But, should I be aware of the temperature too? Say I overclocked my card quite a bit and a game hasn't crashed yet, but the GPU is at 80C or 90C. Should I stop then? Is there something else I should keep an eye out for when I'm OCing the card too? Thanks in advance for answering.
Going to overclock my card, need some advice
- Thread starter Trio
- Start date
I OC'ed my core clock and shader clock. I noticed the temp went up 10C (60C). It's still the same even after resetting the clocks. I also noticed during gameplay (Crysis: Warhead) that when I get out of the water, the little water dripping effect doesn't show up. Is this an artifact? The water effect still didn't come back after resetting the clocks to normal. Things are also taking a while to pop up, like rocks and plants in the water.
Original clocks:
756 Core Clock
1836 Shader Clock
1100 Memory Clock
OC'ed clocks:
776 Core Clock
1884 Shader Clock
1100 Memory Clock
Original clocks:
756 Core Clock
1836 Shader Clock
1100 Memory Clock
OC'ed clocks:
776 Core Clock
1884 Shader Clock
1100 Memory Clock
Last edited:
kennebell347
Member
how are you overclocking that card? what program? rivatuner tells me i dont have the supported drivers or somethin for my gts250 1gig
I'm using the EVGA Precision program that came with my card. You can download it here:
http://www.evga.com/PRecision/
I can't say much about OCing programs since this is my first time OCing, but it's pretty simple with EVGA Precision. It also allows you to view your card temperature and FPS during gameplay, and increase/decrease your fan speed.
So, I increased my Core Clock to 801 mhz. I climbed a rock and fell through it. Is this an artifact? It's happened before, but with a building. I haven't noticed any small dots. A green wall blocking half the monitor has appeared though. This happened before I OC'ed too.
Last edited:
kennebell347
Member
well my card is a sparkle gts250 1 gig so im not sure if i can use evga stuff or not
I mean I fell through it, lol. It's like the rock isn't there. It happened before on the last level of Crysis: Warhead when you're in that tower and all the aliens are invading. I didn't OC my card back then, and all I did to fix the problem was restart my computer.I'm using RivaTuner atm but when i get the new rig i'm going to use EVGA Precision
My OC is
Core Clock 609 MHz
Memory 444 MHz
Shader 1218 MHz
Default:
Core Clock 459
Memory 400
Shader 918
8500 GT ftwalso what do you mean when you climbed a rock and fell through it?
Kornowski
VIP Member
You should keep an eye on the temeperature, yes. I wouldn't let it get above 85c. They're good up to 100c, but I feel it's a little extreme.
Artifacts are pixels that aren't being displayed properly. Often blocks or dots of colour, Green and Red seem to be the main ones. When this happens, it's known as 'artifacting'.
Falling through rocks and buildings is nothing to do with your graphics card or display, that's simply a fault in the game. The Green wall you mentioned does sound like an artifacting problem though. How often does it happen? Or any other variations of artifacts appeared?
Artifacts are pixels that aren't being displayed properly. Often blocks or dots of colour, Green and Red seem to be the main ones. When this happens, it's known as 'artifacting'.
Falling through rocks and buildings is nothing to do with your graphics card or display, that's simply a fault in the game. The Green wall you mentioned does sound like an artifacting problem though. How often does it happen? Or any other variations of artifacts appeared?
It only happens in one part of the game, where I'm at the beach and I have to take out a few guys; it's only during combat though, and it happens "rarely". It's in the Call Me Ishmael chapter. It's only appeared as a green wall though.
I have a question: Is it bad to OC any clock drasticaly, even though you've already tried that speed and it was fine? My stock core clock speed is 756Mhz and I changed it to 796Mhz. When I started the game, the rocks took a while to render. The game was set to Gamer, btw. It's usually on Mainstream.
I found a REALLY glitchy turtle. Dunno if it's an artifact or not...? It isn't dot like.
Last edited:
Thanks. It's set to 100%.
So I increased my core clock to 836 and shader clock to 2030 and started seeing artifacts. In EVGA Precision, the graph for the shader clock appeared orange. Will keeping the shader clock below 2030 stop the artifacts?
**New question: Will a new driver effect overclocking?
**This thread answered my earlier question about the shader clock and artifacts:
http://www.overclock.net/nvidia/441744-should-core-clock-shader-clock-linked.html
I'm unlinking my shader and core clock now. If that thread is correct, the highest stable OC'ed core clock I can get is 1000mhz?
So I increased my core clock to 836 and shader clock to 2030 and started seeing artifacts. In EVGA Precision, the graph for the shader clock appeared orange. Will keeping the shader clock below 2030 stop the artifacts?
**New question: Will a new driver effect overclocking?
**This thread answered my earlier question about the shader clock and artifacts:
http://www.overclock.net/nvidia/441744-should-core-clock-shader-clock-linked.html
I'm unlinking my shader and core clock now. If that thread is correct, the highest stable OC'ed core clock I can get is 1000mhz?
Last edited:
I think I reached a bottle neck. Can someone make sure of this?
I tried OCing my Core Clock and Shader Clock a bit, and I found the maximum for both is 826/2006. Going any further produces artifacts. I read an article that said unlinking the core clock and shader clock with allow me to increase my core clock without getting artifacts, however I kept getting artifacts even after under clocking the shader clock (under clocking below 2006).
I reset the clocks and OC'ed the memory clock. I was pretty tired, so I only incremented it to 1150. I tried it out and no artifacts, but when I increased AA to 8xQ in 1980 x 1080, the entire game froze. I went into task manager and it said the CPU was being 100% used.
Is the CPU bottlenecking the game, by not allowing me to set AA past 8x in 1980 x 1080? Will I be able to OC the core clock above 826mhz if I leave the shader clock at the original speed? Here are the OC'ed clocks and the original clocks:
826/2006/1150 ~ OC
756/1836/1100 ~ Regular
The temperature never went passed 66C, just incase that helps. I'll really appreciate a reply. Thanks.
I tried OCing my Core Clock and Shader Clock a bit, and I found the maximum for both is 826/2006. Going any further produces artifacts. I read an article that said unlinking the core clock and shader clock with allow me to increase my core clock without getting artifacts, however I kept getting artifacts even after under clocking the shader clock (under clocking below 2006).
I reset the clocks and OC'ed the memory clock. I was pretty tired, so I only incremented it to 1150. I tried it out and no artifacts, but when I increased AA to 8xQ in 1980 x 1080, the entire game froze. I went into task manager and it said the CPU was being 100% used.
Is the CPU bottlenecking the game, by not allowing me to set AA past 8x in 1980 x 1080? Will I be able to OC the core clock above 826mhz if I leave the shader clock at the original speed? Here are the OC'ed clocks and the original clocks:
826/2006/1150 ~ OC
756/1836/1100 ~ Regular
The temperature never went passed 66C, just incase that helps. I'll really appreciate a reply. Thanks.