• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Unexplainable Performance Issues (Win 10 CU, 980Ti, GSYNC)

Soldato
Joined
13 Jan 2004
Posts
21,010
This is somewhat of a revisit as I thought I had narrowed the issues down to stuttering many people had been experiencing and was allegedly fixed in a recent nVidia driver update. This is not the case though, this seems to be a totally different issue.

My original observations were as follows:

The Problem:
Ever since installing Creators Update gaming performance is poor. Notably poor frame times, FPS and a consistent drop until unplayable when multi-tasking on the system.

Overwatch is a prime example. I can cap my FPS at 142 in game and hold it there without ever dropping. Since the issue has arisen with the Win10CU install FPS barely manages to reach my 142 cap, including in spawn, outside areas dip to sub 100 and team fights to 40-50FPS. Utterly dire performance.

My System:
  • Win 10 Creators Update Build 1803 (Fresh, clean install)
  • Latest nVidia Drivers, Albeit the problem persists with any driver version
  • intel i7 4770k @ 4.5Ghz
  • 16GB of RAM
  • 980Ti Classified @ 1475/3800
  • G-SYNC enabled Asus monitor, 2560x1440 144Hz (DisplayPort)
  • Secondary IPS monitor with extended desktop, 1290x1200 60Hz (HDMI)
Observations:
  • The problem ONLY seems to occur when multi-tasking on the system
    • Having a Chrome window open at any point after a system boot for example
  • Closing everything down, as if fresh booted, then loading the game still results in the same issue persisting despite no apparent processes running that would cause it
  • Fresh booting the system, opening NOTHING and loading the game/never alt-tabbing will yield as expected, capped 142FPS results in Overwatch with no perf issues at all
  • With the issue present Task Manager reports 100% GPU usage
  • With the issue present CPU/Memory usage appears as expected
  • Observing GPU stats reveals no particular cause for concern. Clock speeds are up, temps are low.
Fix Attempts:
  • Disabled/Uninstalled Win10 Xbox App and GameDVR
  • DDUed nVidia drivers and performed clean installs
  • Disabled Intel onboard GPU
  • Ran stock GPU clocks
  • Reinstalled game titles
  • Clean Win10 install from fresh ISO media and installing nothing but bare essentials, drivers and game title
Thoughts:
  • My system has enough overhead to handle mutli-tasking background apps. It was never an issue before the CU update and I could easily have multiple Chrome tabs open and alt-tab between titles at will
  • Is there some kind of a focus problem with Win10 and game titles? As in, the second one alt tabs out and alt-tabs back the 3D renderer is not behaving as expected?
  • Why does the issue persist having used my system but then closed down all the apps and be running nothing but the game title?

My new observations have changed a little:

  • I've swapped to FireFox Quantum and no longer use Chrome
  • The problem has reared it's head even when fresh booting the system and playing Overwatch having done NOTHING else
  • I've done some hardware logging although this has not revealed much, see further below
  • There is no rhyme or reason and no noticeable performance statistic other than the observable loss in FPS which indicates what is causing the problem
  • It's not just FPS drops and stutter. There is HUGE input lag, for example I can strafe left and right and see the movement significantly after the actual press, talking 100s of milliseconds here.
  • Sometimes I can game for hours without the issue becoming apparent. Sometimes I cant even get the first game in. Sometimes the issue arises after a few hours. Sometimes the issue does not come at all.
Below are the graphs from GPU logging:

Win10CU-980ti-Issues-G1.jpg

Win10CU-980ti-Issues-G2.jpg

Win10CU-980ti-Issues-G3.jpg


As you can see my Core Clock and Memory clocks remain constant. As does the GPU temp which is under water and usually normalizes at 42 Deg C (Not graphed).

You can clearly see where the performance issues start where the Frametime jumps after having been steadily sub 10ms. This is where buttery smooth, pretty consistent FPS/Frametime gameplay turns into a mess. There is no correlation to what is happening in game. The FPS can recover to 140+ for a short period in intense firefights but then drop to sub 50 when looking at the floor with nothing happening.

Whilst observable GPU usage fluctuates, it does normally anyway. There is no apparent link between GPU Usage and the performance drop. Infact Windows Task Manager report 99% GPU usage throughout, perfect performance or poor performance.

There is a noticeable drop in Total Power. I suspect this is as a result of whatever is causing the performance issues and lowering FPS rather than Total Power dropping and causing the issue itself.

My system memory remains constant whilst gaming ~4GB used out of 24GB. My overclock remains at 4.5Ghz with an average of 50% usage. There is no disk activity. There are no background applications running beyond what boots with the OS normally (Precision X, Logitech Gaming Mouse Software) I have no OSD, Overlays, Comms Apps, Instant Messengers etc running.

I am pulling my hair out. I have ran out of things to try. I can only attribute the problems to the Windows 10 CU update. I had NONE of this on exactly the same hardware configuration prior to the CU update.
 
Do you really mean the Creator's Update? Because there've been updates since. Anyway, this problem was well-known last year. Just go to the Gaming page in your Settings and disable the DVR (may be XBox DVR). Indeed, you could just disable Game Mode. You might also want to check Shadowplay.
 
The issue started with the enforced Windows 10 Update, I'm on the latest 1803 build at present.

I've no Shadowplay, GFE is not installed.

I've got DVR disabled and all Xbox/Game Bar stuff uninstalled/disabled.

The bonkers thing is I can launch and play the game flawlessly, then without warning and for no reason my performance tanks and never recovers. I have to reboot the system.
 
Have you tried disabling full screen optimisations on the games exe?

You will find that on the compatibility tab in properties by right clicking the exe of the games. I have to do that on nearly every game to get smooth performance since the creators update.

Try that first then try stock CPU speed, one stick of ram at a time and one monitor at a time.
 
Last edited:
If it happens after gaming for a while; minimise the game and check the memory tab in the resource monitor, see how much memory is committed to 'standby'.

R1NOm9z.png

In my case, it was steadily increasing until there was no 'free' memory left - this was killing my performance in BF1 especially, followed the below fix to resolve it and haven't had any issues since.

https://www.reddit.com/r/Windows10/...by_memory_issue_causing_stutters_on_creators/

Could be totally unrelated as this was a while ago now, and I'm sure it would have been patched but worth checking.
 

This used to happen to me on windows 7(maybe, 75% sure)/8(definitely) on my on 5770 on both BF3 and BF4 and I remember reading I wasn't alone. Oddly enough they 'fixed' it in BF3, then broke it, then fixed it again and when BF4 launched it was broken again. I wouldn't be surprised to learn that the problem still exists tbh.

Doesn't Chrome use your graphics card for hardware acceleration by default? Could be that.

Battle.net can also use a fair amount of GPU just by being open, for me I've seen it hit 30% gpu usage doing FA on my 580 - even though hardware acceleration is off. I've got to set it to minimize or close upon game launch.

Edit: Have you tried turning GSYNC off?
 
Cheers for all your replies.

Have you tried disabling full screen optimisations on the games exe?

Try that first then try stock CPU speed, one stick of ram at a time and one monitor at a time.

Have tried this, no luck.

Have also tried one monitor.

Have not tried stock CPU speed or cycling RAM sticks but will add it to the list of options.

If it happens after gaming for a while; minimise the game and check the memory tab in the resource monitor, see how much memory is committed to 'standby'.

In my case, it was steadily increasing until there was no 'free' memory left - this was killing my performance in BF1 especially, followed the below fix to resolve it and haven't had any issues since.

https://www.reddit.com/r/Windows10/...by_memory_issue_causing_stutters_on_creators/

Could be totally unrelated as this was a while ago now, and I'm sure it would have been patched but worth checking.

Implemented the EmptyStandbyList trick, unfortunately no difference.

Doesn't Chrome use your graphics card for hardware acceleration by default? Could be that.

I've stopped using Chrome, before that had disabled GPU Acceleration but no impact.

This used to happen to me on windows 7(maybe, 75% sure)/8(definitely) on my on 5770 on both BF3 and BF4 and I remember reading I wasn't alone. Oddly enough they 'fixed' it in BF3, then broke it, then fixed it again and when BF4 launched it was broken again. I wouldn't be surprised to learn that the problem still exists tbh.

Battle.net can also use a fair amount of GPU just by being open, for me I've seen it hit 30% gpu usage doing FA on my 580 - even though hardware acceleration is off. I've got to set it to minimize or close upon game launch.

Edit: Have you tried turning GSYNC off?

I've configured Battle.net to close after launching a game, prevents it running in the background.

Not tried disabling G-SYNC yet, I'll add it to the list but I sure as hell hope it's not that causing it....not sure I can return to non VRR gaming.
 
Are you talking specifically about Overwatch here? If so, there's a well known bug that FPS tanks after alt-tabbing sometimes if you have "reduce buffering" enabled. The fix is to turn "reduce buffering" off and on again. I actually think they fixed this bug (or at least made it happen far less often) recently so your problem is probably more general.
 
Not tried disabling G-SYNC yet, I'll add it to the list but I sure as hell hope it's not that causing it....not sure I can return to non VRR gaming.

I doubt it's that tbh, but it's one less thing to have going on. When you reinstalled windows was it still 1803? Can you get hold of an older version if it was? I'm either cursed or blessed that I don't think I'd notice if I lost freesync :p

Edit: Also have you tried running just one screen?

Edit Edit: Try running Latencymon to see if it picks anything up http://www.resplendence.com/latencymon
 
Last edited:
I think I remember reading DPC Latency Checker has issues with either W7 onwards or W8 onwards, either way on W10 it'd be borked. Surprised LatencyMon shows nothing odd when the system starts to lag. Not sure what else to suggest, W10 does seem to be getting progressively crapper IMO, I'm pretty sure I've had less issues with all prior versions of windows (back to XP) than I have with the W10 with it getting worse as we get more updates and my desktop has had W10 reinstalled multiple times.
 
I know I mentioned my Elite Dangerous issues in the other thread but I can also add that my problems only occur if I have the game set to use window or borderless window. If full screen the problem goes away, even if using Chrome. What I found when the problem was happening was that the fps displayed by the Afterburner companion app was showing 142Hz all the time (locked frame rate in the app), but the actual frame rate in the game looked like it was in the 30's, and was especially apparent on the galaxy map when rotating the view, the star names visibly jiggered. Put it on full screen and it was as smooth as silk. This is the weird thing I didn't mention in the other thread, the fps displayed in the overlay thing still being 142Hz. I did find that using Edge solved the problem when leaving the game in a borderless window, but now I am not so sure that wasn't just because I hadn't started Chrome since reboot, like you seem to have. Will have to test that again.
 
Back
Top Bottom