Frame rate dropping almost exactly 1 minute apart

Lucid Pixel

Reputable
Jun 29, 2014
1
0
4,510
Hey everybody, this would be my first post here :)

Issue: A few games I recently purchased drops to what I'm assuming is near 0 FPS for a very short time. I began timing the interval between drops and they were consistently 60 seconds apart each time.

I've been having this issue with Far Cry 3 and Payday 2 so far. I'm not sure what the deal is but the problem doesn't arise in Titanfall, StarCraft II, Bioshock Infinite, Skyrim. Not sure what Far Cry 3 and Payday 2 have in common but its driving me a little crazy trying to figure this out.

System Specs:
MB: Asus Z87 Deluxe LGA 1150
CPU: i7-4770K 3.50 GHz
GPU: ASUS GTX 770
RAM: (2x) 8 GB DDR3
PSU: Cooler Master 1000W
SSD: Samsung 840 Pro Series

Drivers: GeForce 337.88 Driver

I've tried changing the settings for both FC3 and PD2 in numerous combinations. It doesn't appear to be a V-Sync issue. As recommended in other posts, I turned off PhysX (just in case), MSAA Antialiasing, and shut my Antivirus down and I'm still getting lag the same exact way. Bringing the settings to their lowest possible in FC3 causes slight improvement at first, then continues to drop one minute apart once again. I've heard people using the GTX770 can run Far Cry 3 on ultra settings and get minimal issues.

Has anyone else experienced a problem like this? Can anybody help me get started troubleshooting/fixing my problem? I'm starting to suspect its a temperature issue, or defective hardware (all purchased 6 months ago).
 

Damn_Rookie

Reputable
Feb 21, 2014
791
0
5,660
While I haven't experienced this issue myself (as I'm still on the 332.21 drivers), there have been a lot of complaints on the nVidia forums of split second pauses/freezes/stutters with the 337.88 drivers. Some of the reports even mention them happening seemingly on a regular set schedule, similar to what you describe, which is why I thought I should bring it up.

Supposedly the issue popped up in one of the earlier driver releases, but is still present in the most recent WHQL release. It's a problem nVidia recognize, but they are having trouble reproducing the issue themselves, and thus haven't fixed it yet. The sheer number of complaints about the issue have put me off updating my drivers for the moment (I'm not in any rush anyway).

Obviously I'm not sure if this is the cause of the issue you're having, but maybe try one of the older driver releases and see if it helps at all. Try the 332.21 driver first, and if that doesn't help, try going back a bit further (making sure to opt for a clean installation each time).