Artifacts after overclocking..

[Digital X]

Was benchmarking on Batman AK to see how far I could go without anything happening and for the boost of FPS.

I was bumping up core clock and got to +250mhz(increments of 10 each bench) when artifacts in the top left corner started. Huge adrenaline rush then I immediately ALT F4'd the game and reset everything on MSI Afterburner.

I loaded up another game and it did screen wide.

Just restarted and loaded up killing floor and also serious sam to test (just random games I clicked first), no artifacts whatsoever.

I was dreading I had killed the card but it seems fine after restarting.

Should I be safe now if I just DON'T touch it for a while? I certainly won't go to 250mhz again.. Memory clock was at +50mhz

I'd followed MSI guide on OC'ing and had done it before without anything happening, just think I overdid it a tad.

 

[Radox-0]

Just drop down the overclock to say 200 MHz and then work up in smaller increments. Seeing artifacts while trying to find a stable overclock is not really unusual as you approach a boundary of the chip. No need to leave it for a while or anything like that just work in a smaller steps.

 

[Digital X]

Ok thanks, but why would it artifact even after resetting all clocks to normal? And only work fine again after restarting the PC?

 

[r7slayer]

Was benchmarking on Batman AK to see how far I could go without anything happening and for the boost of FPS.

I was bumping up core clock and got to +250mhz(increments of 10 each bench) when artifacts in the top left corner started. Huge adrenaline rush then I immediately ALT F4'd the game and reset everything on MSI Afterburner.

I loaded up another game and it did screen wide.

Just restarted and loaded up killing floor and also serious sam to test (just random games I clicked first), no artifacts whatsoever.

I was dreading I had killed the card but it seems fine after restarting.

Should I be safe now if I just DON'T touch it for a while? I certainly won't go to 250mhz again.. Memory clock was at +50mhz

I'd followed MSI guide on OC'ing and had done it before without anything happening, just think I overdid it a tad.

It's highly unlikley you will have killed your card from increasing its frequency. It's not like you threw a extra Ghz at it lol.

It will have artifacted because it became unstable and was causing errors, same happens with memory overclocking too. When you see atifacting dial the overclock down to what it was stable at previously and from there you either give it +10 ~ +15 mv extra voltage to see if you can stabilise it all within your cooling capacity.

Remember as long as you dont give your card too much extra voltage or let it get too hot VRMs, core etc then you shouldn't have to worry about killing your card too much lol.

Anyway your card should be fine you just found a point where it was unstable at stock voltage and it may of needed a reboot to get it stable again. The clocks may have stuck when it became unstable? It's happend to me before and needed to reboot to reset things.

 

[Aretak]

Perhaps the reset settings didn't take in Afterburner, if you forgot to hit apply or something. If it's fine after a restart, I wouldn't worry too much. It's extremely unlikely (borderline impossible) that you damaged your card just by raising the core clock.

 

[Digital X]

Ok thanks, just first time seeing it artifact so was fearing the worst.

 

[Safetytrousers]

I think the only way to damage your GPU is by increasing voltage.
Seeing a little bit of artifacting won't be a sign of any damage, you just need to dial back your overclock.

 

[Rroff]

The short version is that an unstable overclock can cause the GPU to get into a state that it normally wouldn't and doesn't know how to reset from until power cycled. Even a full driver restart, etc. can't always reset faulty states deep in the GPU.

 

[sand_dune]

Doesn't Batman AK come with artefacts built in?