Overclocked GPU stable in stress tests, but crashes ingame

[CommandoGeek]

Hi, everybody!
I've overclocked my GPU's clock speed and memory clock speed, both by an offset of 100. I ran FurMark with these speeds and didn't see any artifacts, so I didn't think I needed to increase the voltage or power limit. So right now, the voltage is at its stock.

Now whenever I'm trying to run a game, I make it for about a minute before my computer suddenly shuts down, my GPU fan hits 100%, and then a reboot occurs. If I keep my GPU at stock-rated speeds, however, I can run the game fine and there's no problem.
I've used CoreTemp and HWiNFO to check my temperatures and power intake for both the CPU and the GPU, and I've found that everything's stable (below 60C).

What kind of problem is this? Is it a hardware malfunction, or should I downclock a bit? I've already tried pushing the overclock down to offsets of 50MHz, but that still results in a crash.

System:
MOBO- Asus Maximus VI Formula
CPU- Intel Haswell 4770K
Heatsink - Noctua NHD14
GPU- Asus 780Ti DirectCU II
PSU- Seasonic Platinum 860W

GPU speeds:
Core: 954MHz --> 1054MHz
Memory: 1750MHz --> 1800MHz

 

[CommandoGeek]

I was playing Star Citizen, which is probably a better stress test than both FurMark and Valley run simultaneously. I swear, that game knows how to REALLY push your system.

I'll investigate it further, because I was able to pass with only a core overclock of 50MHz (no memory overclock), with only minor artifacts. Increasing power limit by 5% should solve this, probably.

Is it possible that the same overclocks might demand different amounts of power input depending on the application being run? So that overclocking isn't exactly "persistent", and needs to be tweeked constantly?

 

[CommandoGeek]

Well, I just did a bit more info digging, and found out that apparently, this game can't handle overclocked GPU cards yet. I don't know how it's like this, but I've found multiple people who're getting the same problems.

Thanks for the help, though. It's very appreciated

 

[CommandoGeek]

It seems that it's also because CryEngine doesn't handle overclocks well...