Framerate acting very funny

crazymarc

Distinguished
Dec 5, 2013
53
0
18,530
Hi,
My current build is:
Mobo - ASUS Z97-A LGA 1150

CPU - Intel Core i7-4770K Haswell Quad-Core 3.5GHz LGA 1150

GPU - EVGA SuperClocked 02G-P4-2765-KR GeForce GTX 760 2GB 256-bit GDDR5 PCI Express 3.0

PSU - XFX TS Series P1550SXXB9 550W ATX12V 2.2 & ESP12V 2.91

RAM - 4 x 2G

OS - Windows 7

I just upgrade the Mobo and CPU to play Wildstar and other games at max settings. When i first got everything put together and running i was getting 80+ frames on all games, then on my next boot up the next day my frames were in the 20s-40s and there was a lot of stuttering going on.

I thought maybe it was my RAM so i took two sticks out and rebooted and everything was back at 80+ frames. Then after another reboot it was back to the low framerate. I started up Saints Row 4 on Ultra and started running and sprinting around the city and it went to a black screen, then back to desktop and steam relaunched the game on its own. I started sprinting and running again then the screen went black and my monitor read it didnt have a connection and went into standby.

I ran Furmark burn in 1920x1080 15 min test and it didnt last but 2 mins before i got a BSOD so i'm assuming it is the GPU but i'm not 100%. What was weird is that sometimes the rig boots and everything is 80+ frames working great, but most boots it runs 20s-40s fluctuating.

Any help would be greatly appreciated
 
Solution
Looks like a video card related crash for sure.

Your GPU-Z sensors look VERY wrong.

1. The card is not getting to load(bottle necks cause this, but i do not think it is)
2. Both the GPU and memory are not clocking up properly by the look of things. The memory does not even move
3. This all seems to be triggered by the card or drivers thinking the card is over its TDP limit(big green PWR). The TDP indicator seems to show you are not even close to the power limit on the card.

My card is a 670, so it, while being the same type of core is still different.

This was taken with a stress test program similar to furmarks(OCCT : GPU test)
5djxoh.png


As you can see the clocks all bump up, but not to the max...

crazymarc

Distinguished
Dec 5, 2013
53
0
18,530
I'm running Saints row right now with GPU-Z up and these are the stats...they seem wrong to me, and the game must be running at 20 and below frames it is super laggy after playing it for like 10 mins


 

crazymarc

Distinguished
Dec 5, 2013
53
0
18,530
my drivers appear to be up to date Geforce 337.88, what Geforce experience tells me anyways and the bug check code for my crash is 0x00000116 if thats the code you are looking for
 
Looks like a video card related crash for sure.

Your GPU-Z sensors look VERY wrong.

1. The card is not getting to load(bottle necks cause this, but i do not think it is)
2. Both the GPU and memory are not clocking up properly by the look of things. The memory does not even move
3. This all seems to be triggered by the card or drivers thinking the card is over its TDP limit(big green PWR). The TDP indicator seems to show you are not even close to the power limit on the card.

My card is a 670, so it, while being the same type of core is still different.

This was taken with a stress test program similar to furmarks(OCCT : GPU test)
5djxoh.png


As you can see the clocks all bump up, but not to the max because the TDP limit gets past(the average stays at 99% and the clocks are lower than normal. The MAX of 1215 is NOT held in the test).

So either GPU-z does not work with the card(doubtful because it does seem to see the specs) or something is wrong with the card or drivers.

Since you appear to be in Windows 7, could you please power down the computer and power it back up to see if the results change. My first 670 was defective and would get a driver crash on some games and after it recovered the clocks speeds would get messed up.

Another program that will stress the video card would be to run Folding@Home. When my 670 was not working it would return errors when folding very fast, it was a very effective way to see that in my case, the cards own boost was too much a drop of 26mhz make the card stable. The company still replaced the card over the issue. You may be able to use something like afterburner to drop the cards clock speeds by 13 mhz at a time to see if it stabilizes.

One interesting thing about these kepler and newer cards is they use different clocks for different loads so one game may be 100% stable(either it does not require high speeds or is demanding enough that the card stays at a lower clock speed) while another may crash constantly. Bioshock Infinite was my card crasher, while Rage could run forever(it clocked much lower because it was easy to run).

It may be time to give Evga a call or message. They are far better equipped to deal with this kind of thing. I will still help in any way I can from here.
 
Solution