GTX 970 card maxing issues

[Iceman96051]

So very recently my GTX 970 has decided that using only 539.5 MHz of it's core clock is better than the 1300 or so of it's default (I honestly don't know the default exactly but it doesn't really pertain to this anyways). I've had this card for about a year now and it just started doing this a few days ago. It can't run anything above 30 FPS, it tries but it fails miserably. I'm starting to think it must be a power setting or something that got switched on because I've been watching it's temps and it doesn't go above 45 degrees Celsius which is definitely not anywhere near overheating. If it helps I also have MSI Afterburner which could be part of the problem but I'm not sure how it would be. The last thing I did before this issue happend was install Warframe which again shouldn't really effect it all. Anyways, any help would be greatly appreciated as gaming in 30 FPS is doable, but shouldn't need to be done with a 970.

I forgot to add that my processor is an I7 4790k which seems to running just fine on all parts. It doesn't max out either at the moment (which by max out I mean hit it's top temps of 70-75) but that's probably due to the graphics card keeping it behind.

 

[maxalge]

So very recently my GTX 970 has decided that using only 539.5 MHz of it's core clock is better than the 1300 or so of it's default (I honestly don't know the default exactly but it doesn't really pertain to this anyways). I've had this card for about a year now and it just started doing this a few days ago. It can't run anything above 30 FPS, it tries but it fails miserably. I'm starting to think it must be a power setting or something that got switched on because I've been watching it's temps and it doesn't go above 45 degrees Celsius which is definitely not anywhere near overheating. If it helps I also have MSI Afterburner which could be part of the problem but I'm not sure how it would be. The last thing I did before this issue happend was install Warframe which again shouldn't really effect it all. Anyways, any help would be greatly appreciated as gaming in 30 FPS is doable, but shouldn't need to be done with a 970.

I forgot to add that my processor is an I7 4790k which seems to running just fine on all parts. It doesn't max out either at the moment (which by max out I mean hit it's top temps of 70-75) but that's probably due to the graphics card keeping it behind.

did you enable vsync?


if its stuck at 30 fps you might have enabled it

 

[Iceman96051]

did you enable vsync?


if its stuck at 30 fps you might have enabled it

I was thinking it might be that as well but the setting in NVIDIA control panel is set to use 3D application which is normal and in-game it attempts to get to 60, sometimes it can, but it can't hold it. For example in KF2, it will hit 62 FPS at the start of a match, the moment you shoot it hits 40, the moment you hit something it hits 30, and when things start spawning and you start shooting it hits 15-20 and sometimes lower. Point is that even when benchmarking with the Heaven benchmark it stayed right at 540 MHz. I really hope it's just a setting or something and not the card being defective as I don't have the money to replace it right now. I also updated the card to the 368.81 update which is most recent. I was using the update from late May before which it didn't seem to fix it either. Neither did reseting all settings in Nvidia control panel to default. And running something without MSI just causes it to get to 50-60 degrees as the default settings don't turn the fans on for a while (at least not at high speeds). I'm at a total loss at what it could be.

I also forgot to add I'm using Windows 10 but I've had no issues with that for about 8 months now but I figure extra info can't hurt.

 

[maxalge]

did you enable vsync?


if its stuck at 30 fps you might have enabled it

I was thinking it might be that as well but the setting in NVIDIA control panel is set to use 3D application which is normal and in-game it attempts to get to 60, sometimes it can, but it can't hold it. For example in KF2, it will hit 62 FPS at the start of a match, the moment you shoot it hits 40, the moment you hit something it hits 30, and when things start spawning and you start shooting it hits 15-20 and sometimes lower. Point is that even when benchmarking with the Heaven benchmark it stayed right at 540 MHz. I really hope it's just a setting or something and not the card being defective as I don't have the money to replace it right now. I also updated the card to the 368.81 update which is most recent. I was using the update from late May before which it didn't seem to fix it either. Neither did reseting all settings in Nvidia control panel to default. And running something without MSI just causes it to get to 50-60 degrees as the default settings don't turn the fans on for a while (at least not at high speeds). I'm at a total loss at what it could be.

I also forgot to add I'm using Windows 10 but I've had no issues with that for about 8 months now but I figure extra info can't hurt.

do you monitor cpu temps while playing?

 

[Iceman96051]

do you monitor cpu temps while playing?

Yeah those temps were from when I was playing/benchmarking. It wouldn't go above 42-45 degrees celcius in either of those and it idles at 28-30 which I would say is pretty normal. Anyways it decided to kind of fix itself like my issue I posted on here (that was about my motherboard deciding to read all temperatures at 99 degrees celcius despite the fact there were not even a fraction of being that hot). Only thing I can think of that fixed it was me going through everything Nvidia related and various power settings on Windows itself and just defaulting all of the settings. Before that I tried turning it off and on, cleaning the PC out, running an anti-virus (to see if a virus was doing it), resetting settings in MSI Afterburner, running it without MSI afterburner, updating the card, enabling game optimization in Nvidia Experience and changing it's clock a bit to see if that would change anything (it really didn't). The going through and resetting quite a few things to default did seem to fix it however so I assume it must be a certain setting or something. Anyways thanks for trying to help on that. I tried looking up my problem but it didn't seem like people were having the exact issue I was (kind of like my motherboard thing) and I'm still not sure what caused it in the first place but I hope it stays fixed now.