Trying to OC 7950 again... Can't enable Unofficial Overclocking in MSI Afterburner!

[Techhog]

VRM temps get iffy at 110c. 80c is fine.

Hm... If you say so. I'll keep going I guess. Currently at 1175/1400 @1.2V

 

[Techhog]

Okay, now I'm seriously confused. I got lower scores in Valley and Firestrike at 1200/1400. Valley I know is having some type of issue because it's giving me bad performance at all clocks since it crashed once, but I have no clue what Firestrike's deal is... I'm gonna try 1450 on the mem

Also, my physics score in all 3 3DMark demos went up significantly... I have no idea what's going on lol

 

[monkeydelmagico]

Okay, now I'm seriously confused. I got lower scores in Valley and Firestrike at 1200/1400. Valley I know is having some type of issue because it's giving me bad performance at all clocks since it crashed once, but I have no clue what Firestrike's deal is... I'm gonna try 1450 on the mem

Also, my physics score in all 3 3DMark demos went up significantly... I have no idea what's going on lol

OC is probably unstable at that level. Look at min FPS. If your seeing low single digits in Valley you need to turn back the OC a bit.

Also, start with the GPU clock only. Leave mem speeds alone until you find the highest stable GPU clock.

 

[Bubbleawsome]

High memory clocks can also slow it down. Error correction kicks in. My 770 gets 20 less khash when memory overclocked to close to 8Ghz.

 

[Techhog]

OC is probably unstable at that level. Look at min FPS. If your seeing low single digits in Valley you need to turn back the OC a bit.

Also, start with the GPU clock only. Leave mem speeds alone until you find the highest stable GPU clock.

That's the thing. Valley was performing as if I was at stock clocks no matter what I did. Raising or lowering clocks did nothing. The program itself was bugged. A restart fixed that. My computer acts a bit weird sometimes when I change the clocks too much in a short period of time, or if Valley crashes at any point. (Which it did, so I tried raising voltage and suddenly my performance dropped like a rock.)

So, Valley works after the restart, so now I'll test Heaven and 3DMark...

 

[Techhog]

Well, I was playing a game and the GPU kept switching between full and idle clocks on the menu. I think I'm gonna stay at 1180.

 

[Bubbleawsome]

Menus do that with high clocks. There was also a crazy thread that said Tahiti power limited even with +20 in benchmarks. Might look at using a pt1 bios and 1.25v if you really want that extra bragging.

 

[Techhog]

Menus do that with high clocks. There was also a crazy thread that said Tahiti power limited even with +20 in benchmarks. Might look at using a pt1 bios and 1.25v if you really want that extra bragging.

I see. I don't really want to go that fa, though. I got up to 1200/1500, which is fine. I still have some weird issue where where Afterburner doesn't properly apply overclocks after waking up from sleep (the driver crashes when starting games), forcing me to reapply the overclock though. I don't know if the problem is the overclock since I've seen this happen even at much lower clocks but I have no issues playing for hours after that. It's really weird. I thought it was fixed after last time I re-installed afterburner, but it's happening again.

 

[KingFatty]

I have the same PCS+ 7950, and when I overclock too aggressively, the symptom is the driver will crash and recover. But even after recovering, it doesn't work quite right all the time, until I reboot.

So maybe you are just at the ragged edge of overclocking based on your chosen voltage and fan speed/case cooling, and your behavior is expected based on the driver crashes? I'm just not certain you've found a rock-solid 24/7 overclock setting, unless maybe you need to crank up your fan speed a lot more or something? Don't settle until you've eliminated the driver crashes/restarts.

 

[Techhog]

I have the same PCS+ 7950, and when I overclock too aggressively, the symptom is the driver will crash and recover. But even after recovering, it doesn't work quite right all the time, until I reboot.

So maybe you are just at the ragged edge of overclocking based on your chosen voltage and fan speed/case cooling, and your behavior is expected based on the driver crashes? I'm just not certain you've found a rock-solid 24/7 overclock setting, unless maybe you need to crank up your fan speed a lot more or something? Don't settle until you've eliminated the driver crashes/restarts.

The thing is that this happened even at 1050/1250 @ 1.1V, though that stopped when I reinstalled Afterburner. And now it's back. I'm pretty sure the only way to actually prevent it is to run at stock clocks.

Also, when i say it crashes, I mean that is crashes and recovers repeatedly until I either close the game or reapply the overclock. I'll test it with a few game when i get the chance, though I'll generally use stock clocks in games which don't actually need the extra power.

EDIT: Just tested. I get the crash after sleep from any clocks above 1000MHz.