R7870 Hawk - 2nd screen flicker???

[c.pryor2223]

So i have my 7870 hawk on a stable overclock @ 1250MHz GPU clock and 1450MHz Mem clock. I say its stable because ive run Furmark Burn-in with no problems on air, with a max temp of 82 degrees C, for several hours. However, when gaming / browsing. Occasionally my screen flicker goes off the walls, and i have to relog into windows with script macros to regain functionality. No driver failure. None of this artifacting occurred during Furmark burn-in. So my question, WHAT THE FUCK IS HAPPENING.

Thanks in advance for any replies,

Christian

[mvitkun]

I'd lower the memory clock back to the stock 1200mhz as memory OC'ing leads to system instability and has very few if any performance gains.

also,just for future reference,when you have to say "it's stable in _______,it's just unstable in _____" it typically means it's not stable,because it's either stable in everything,or it's unstable.there's no in between area whatsoever.

[c.pryor2223]

I'd lower the memory clock back to the stock 1200mhz as memory OC'ing leads to system instability and has very few if any performance gains.

also,just for future reference,when you have to say "it's stable in _______,it's just unstable in _____" it typically means it's not stable,because it's either stable in everything,or it's unstable.there's no in between area whatsoever.

i took your advice and turned down the mem clock. I was able to maintain it jumping through some hoops every boot (

) Which is so dumb, that i just have my "unlocked" gpu running stock speeds now. I said it was stable because in Furmark the GPU was at 100% load and running seamless OC'ed. the flickering and whatnot occurred during random browsing at minimal loads (while OC'ed). So I was at a loss. My understanding/theory now is that it has to do with the AMD drivers + idle clocks + OC'ing. Im hoping the next CCC drivers fix these shenanigans

[mvitkun]

i took your advice and turned down the mem clock. I was able to maintain it jumping through some hoops every boot (

) Which is so dumb, that i just have my "unlocked" gpu running stock speeds now. I said it was stable because in Furmark the GPU was at 100% load and running seamless OC'ed. the flickering and whatnot occurred during random browsing at minimal loads (while OC'ed). So I was at a loss. My understanding/theory now is that it has to do with the AMD drivers + idle clocks + OC'ing. Im hoping the next CCC drivers fix these shenanigans

you can still overclock it just overclock the core clock instead of the memory clock.

also Furmark tasks the gpu intensively in certain areas and less so in others,when those other areas are tasked more intensively they crash.

I'd say test it on

Furmark

Heaven (max settings)

3DMark (highest quality profile)

and atleast one intensive game,like crysis (at max settings)

by doing this you test memory clocks,core clocks,and temperature stability instead of simply 1 or 2 of them allowing for a more stable system.

if any of them have issues,even a single artifact,or a small flicker once in the benchmark,it means it's unstable.

[c.pryor2223]

i took your advice and turned down the mem clock. I was able to maintain it jumping through some hoops every boot (

) Which is so dumb, that i just have my "unlocked" gpu running stock speeds now. I said it was stable because in Furmark the GPU was at 100% load and running seamless OC'ed. the flickering and whatnot occurred during random browsing at minimal loads (while OC'ed). So I was at a loss. My understanding/theory now is that it has to do with the AMD drivers + idle clocks + OC'ing. Im hoping the next CCC drivers fix these shenanigans

you can still overclock it just overclock the core clock instead of the memory clock.

also Furmark tasks the gpu intensively in certain areas and less so in others,when those other areas are tasked more intensively they crash.

I'd say test it on

Furmark

Heaven (max settings)

3DMark (highest quality profile)

and atleast one intensive game,like crysis (at max settings)

by doing this you test memory clocks,core clocks,and temperature stability instead of simply 1 or 2 of them allowing for a more stable system.

if any of them have issues,even a single artifact,or a small flicker once in the benchmark,it means it's unstable.

I will play with just OC'ing the gpu. And yeah i dont know why i didnt mention it, but i was also testing with

3DMark Jane

3DMark New Calico

Max settings BF3 (for about 20mins)

-With absolutely no troubles.

Hopefully leaving the mem speed alone will stop the flickering on my 2nd screen

Thanks for the quick responses and info :D

[mvitkun]

3DMark Jane

3DMark New Calico

Max settings BF3 (for about 20mins)

I'd say battlefield 3 is a good way to test most aspects of the graphics card as it uses a good amount of memory as well as being GPU core intensive.

I'd recommend trying 3Dmark11 as well,for me personally I've passed 3d mark vantage,Crysis,heaven,furmark,random other games like bioshock 2 that I played and then failed 3dMark 11.

it really just shows that you need a large variety of tests to give a high probability of system stability.

also try running all the 3dmark vantage tests instead of a select few.

I'd also recommend running HWInfo in the background and monitoring VRM,memory,and gpu temps to make sure that no part of the graphics card overheats,although the twin frozr series of heatsinks typically does a superb job of cooling the entire graphics card so I doubt it'll be an issue.

and good luck with the OC'ing hope it goes well.

[c.pryor2223]

Wow, i was using Cpu-z , coretemp, and gpu-z. hw info is so much more intuitive! thanks for the suggestion! We'll wait and see how my OCing goes :P