Unable to record prior to overclocking my GPU

Toggle sidebar Toggle sidebar
S

Shadowex99

Honorable
Aug 22, 2014
194
0
10,680
So I was overclocking my gpu today after recently buying my PC less than a week ago. I have finally found a stable overclock for my games but now when I attempt to record my gameplay, my games crash instantly. It corrupts my video file and just shuts down the game completely no matter what game.

GPU: Asus Radeon HD 7850 Direct CU II
OCed:
Core Clock: 1030 Mhz
Memory Clock: 1440 Mhz

Stock:
Core Clock: 860 Mhz
Memory Clock: 1200 Mhz

10 Mhz higher on either and my games either freeze or crash. At worst case scenario just freezes my whole computer to be hard reset.

Bd6RkMQ.png


EDIT: I don't really play minecraft that often but it was the quickest to open e.g. (Battlefield 3 - 4, Tera, League of Legends, Maplestory, Combat Arms)
 
Sort by date Sort by votes
R

rhysiam

Splendid
Mar 24, 2013
4,366
29
26,990
What if you drop back the OC a bit? Once you approach the limits of an OC all kinds of strange errors can crop up (including games and drivers crashing as you're seeing) and it's certainly possible that recording the game pushes the video card just that little bit more (even if the bulk of the encode is being done by the CPU).

If you've only dropped back 10mhz from a crash, it's likely your graphics card is NOT going to be 100% stable in all situations. Drop back 40-50mhz and there's a very good chance the problem will go away and you'll have found a (properly) stable OC.
 
Upvote 0 Downvote
Dogsnake

Dogsnake

Distinguished
Oct 20, 2006
2,309
0
20,460
When you ask your system to record it places additional stress on the video. Since you have pushed the oc to the cards limit on the game the additional stress of recording the video crashes the card. Back off your oc.
 
Upvote 0 Downvote
R

rhysiam

Splendid
Mar 24, 2013
4,366
29
26,990


If it was working, and then you OC'd, and now it's not working... it's almost certainly the thing you changed -> the OC. Both the above responses have suggested the same thing, you've just pushed the OC a little too hard.

It's not at all unusual to think you've got a stable OC but then find edge cases which just push the card that little bit too hard and things go pear shaped. There's a very, very good chance that if you drop another 20Mhz off both the memory and core clock everything will work perfectly. There's also a very good chance that if you leave the clocks where they are at the moment, you'll occasionally run into other situations which just push the card that little bit harder and you get a driver or system crash.

It's your machine and you get to decide the level of stability you'll settle for, but if I were in your shoes I'd be dropping a little back so I'd be more confident things won't crash on me.
 
Upvote 0 Downvote
Dogsnake

Dogsnake

Distinguished
Oct 20, 2006
2,309
0
20,460
FYI a 10% oc is considered good. You have pushed way past that. How are you stress testing your settings? Also I have had stable O.C. under the stress t and then crash in real use. This is often because when in real time use I have other things going on. So I dial back to a stable setting under all my real world use. My choice and just a suggestion. Lastly and also my opinion is that an O.C. that does not yield real world improvement of my use is just useless after seeing what it is. If I have 60 fps in a game at stock and 85 fps at O.C. it looks good on a graph but in terms of play there is no difference. One side effect of any O.C. is heat and the associated wear stress on all the hardware from the increased heat loads. Even if the cards sensors show tolerable temps. the heat is still being produce at the chip/transistor level. To each their own. GL
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom