suddenly getting terrible FPS

greatgreenman

Senior Member
Joined
May 19, 2016
Messages
566
Reaction score
16
Been using a Palit GTX 970 Jetstream.. All was going well until today when I started getting rubbish frames. Even running Valley benchmark I'm getting 20 fps on low settings.

Any idea what the hell happened? CPU, Memory, or GPU problem? Temps are completely fine and I don't see anything unusual in process view...
 

royfrosty

High Supremacy Member
Joined
Jul 23, 2009
Messages
27,727
Reaction score
1,553
Been using a Palit GTX 970 Jetstream.. All was going well until today when I started getting rubbish frames. Even running Valley benchmark I'm getting 20 fps on low settings.

Any idea what the hell happened? CPU, Memory, or GPU problem? Temps are completely fine and I don't see anything unusual in process view...

Might wanna check what resolution is it running on? Also might wanna check your vram utilize?
 

Encrypted11

Supremacy Member
Joined
Jun 9, 2012
Messages
5,937
Reaction score
271
Not sure what OS u using.

Quite recently, Windows 10 AU introduced changes to WDDM with its specifications updated to 2.1 from 2.0. Nvidia didn't update the spec for its R370 drivers properly and some games like CSGO and OpenGL applications (like firestorm viewer) had these issues.

A microsoft employee on the windows update team confirmed the replicable bug (via twitter) and Nvidia fixed it in like 3 weeks with 373.06 Whql. If its Windows 10 AU you're on, might want to update drivers to rule out driver issues.

https://twitter.com/johnwinkmsft/status/776492565801467904
 
Last edited:

greatgreenman

Senior Member
Joined
May 19, 2016
Messages
566
Reaction score
16
Not sure what OS u using.

Quite recently, Windows 10 AU introduced changes to WDDM with its specifications updated to 2.1 from 2.0. Nvidia didn't update the spec for its R370 drivers properly and some games like CSGO and OpenGL applications (like firestorm viewer) had these issues.

A microsoft employee on the windows update team confirmed the replicable bug (via twitter) and Nvidia fixed it in like 3 weeks with 373.06 Whql. If its Windows 10 AU you're on, might want to update drivers to rule out driver issues.

https://twitter.com/johnwinkmsft/status/776492565801467904

I had that AU awhile back and I did a rollback. However, there was another force update today and I'm not sure if it's the AU. I tried rolling back again but I got an error this round...

But yeah this fps drop started happening around the time I had a Windows update.

Did a memtest for about 15 mins, came back, and I was back up to 60 fps again. Played some games for awhile, and my FPS slowly started falling after some time.. GFX Clock on afterburner was stuck at ~300MHz while mem clock was at ~3000MHz.

Definitely nothing to do with temperature that much I'm sure
 
Last edited:

Elijahonli

High Supremacy Member
Joined
Oct 27, 2008
Messages
25,846
Reaction score
159
I had that AU awhile back and I did a rollback. However, there was another force update today and I'm not sure if it's the AU. I tried rolling back again but I got an error this round...

But yeah this fps drop started happening around the time I had a Windows update.

Did a memtest for about 15 mins, came back, and I was back up to 60 fps again. Played some games for awhile, and my FPS slowly started falling after some time.. Boost Clock on afterburner was stuck at ~300MHz while base was at ~3000MHz.

Definitely nothing to do with temperature that much I'm sure
i suggest doing a reformat
 

lamesensei

Senior Member
Joined
Aug 17, 2007
Messages
1,375
Reaction score
4
use afterburner or gpu-z check if ur clockspeeds are stuck at powersaving mode
 

Encrypted11

Supremacy Member
Joined
Jun 9, 2012
Messages
5,937
Reaction score
271
I had that AU awhile back and I did a rollback. However, there was another force update today and I'm not sure if it's the AU. I tried rolling back again but I got an error this round...

But yeah this fps drop started happening around the time I had a Windows update.

Did a memtest for about 15 mins, came back, and I was back up to 60 fps again. Played some games for awhile, and my FPS slowly started falling after some time.. Boost Clock on afterburner was stuck at ~300MHz while base was at ~3000MHz.

Definitely nothing to do with temperature that much I'm sure
Windows 10 updates are cumulative. As long as your update history has "Windows 10 cumulative" KB318xxxx you have the update installed. If the problem is AU + WDDM 2.1, you don't rollback. use 373.06 WHQL with the bugfix.
 

wwenze

Greater Supremacy Member
Joined
Dec 2, 2002
Messages
86,620
Reaction score
30,268
I had that AU awhile back and I did a rollback. However, there was another force update today and I'm not sure if it's the AU. I tried rolling back again but I got an error this round...

But yeah this fps drop started happening around the time I had a Windows update.

Did a memtest for about 15 mins, came back, and I was back up to 60 fps again. Played some games for awhile, and my FPS slowly started falling after some time.. Boost Clock on afterburner was stuck at ~300MHz while base was at ~3000MHz.

Definitely nothing to do with temperature that much I'm sure

Do they use base-8 in your universe?
 
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts. Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
Top