Well, I'd originally had my thoughts/questions in this post. And, diagnosing, it appeared to be the power supply. Said power supply was replaced under warranty.
It was not the power supply. The behavior, as part of its intermittent nature, simply didn't happen while I was testing with another PSU. Likewise, in another system.
I then once again started to suspect the video card. I was also able to enable a FreeSync indicator on my monitor (LEDs at the bottom white when FreeSync is off, and red when FreeSync is on). My monitor is the Acer XR382CQK 38" 3840x1600 IPS, 48-75 FreeSync Range.
Now, we're talking 3840x1600, but we're also talking about some singularly undemanding games, such as (windowed mode) Pinball Arcade, and (fullscreen) Don't Starve/Don't Starve Together, Portal, Portal 2, and Clue/Cluedo. My old R9 285 could do this (albeit with some struggle), and the GTX 1080 was managing it flawlessly at 60Hz.
Until recently.
Finally it dawned on me. I was using the 442.59 drivers. So, I uninstalled the drivers, and tried installing the latest, 442.74. It still happened. I tried earlier ones that I had an installer for (441.41 I believe), same thing.
I tried installing the earliest one I could find from Nvidia's advanced driver search, 430.39 (where are the earlier ones??), it still happens. Given that I'd also triggered the "change LED color when FreeSync is on" function on the monitor, and that I'd noticed that, if it was struggling with frame-rate, it seemed to coincidentally always be hovering at one FPS below my minimum FreeSync range.
I still had an installer for an earlier driver that I knew was working, so I went back to 417.71. Everything was fine in Pinball Arcade and Portal, and Portal 2.
With 430.39, I noticed that the screen juddering in Don't Starve Together, and Clue (seriously, it just pans the camera from an in-room view to an overhead view, and THAT'S IT!) were particularly bad. I'm going to try those with 417.71 tonight or later in the week, time permitting.
I might also bite the bullet and disable G-Sync/FreeSync in the drivers with one of the known bad drivers, just to see.
Maybe it's just the aggravation factor, but I swear, it seems like Nvidia is breaking FreeSync functionality that previously worked. I don't know if I need FreeSync for any of the games I'm playing, but it's really nice to be able to have the option. Why put it in, then later sabotage it?
It was not the power supply. The behavior, as part of its intermittent nature, simply didn't happen while I was testing with another PSU. Likewise, in another system.
I then once again started to suspect the video card. I was also able to enable a FreeSync indicator on my monitor (LEDs at the bottom white when FreeSync is off, and red when FreeSync is on). My monitor is the Acer XR382CQK 38" 3840x1600 IPS, 48-75 FreeSync Range.
Now, we're talking 3840x1600, but we're also talking about some singularly undemanding games, such as (windowed mode) Pinball Arcade, and (fullscreen) Don't Starve/Don't Starve Together, Portal, Portal 2, and Clue/Cluedo. My old R9 285 could do this (albeit with some struggle), and the GTX 1080 was managing it flawlessly at 60Hz.
Until recently.
Finally it dawned on me. I was using the 442.59 drivers. So, I uninstalled the drivers, and tried installing the latest, 442.74. It still happened. I tried earlier ones that I had an installer for (441.41 I believe), same thing.
I tried installing the earliest one I could find from Nvidia's advanced driver search, 430.39 (where are the earlier ones??), it still happens. Given that I'd also triggered the "change LED color when FreeSync is on" function on the monitor, and that I'd noticed that, if it was struggling with frame-rate, it seemed to coincidentally always be hovering at one FPS below my minimum FreeSync range.
I still had an installer for an earlier driver that I knew was working, so I went back to 417.71. Everything was fine in Pinball Arcade and Portal, and Portal 2.
With 430.39, I noticed that the screen juddering in Don't Starve Together, and Clue (seriously, it just pans the camera from an in-room view to an overhead view, and THAT'S IT!) were particularly bad. I'm going to try those with 417.71 tonight or later in the week, time permitting.
I might also bite the bullet and disable G-Sync/FreeSync in the drivers with one of the known bad drivers, just to see.
Maybe it's just the aggravation factor, but I swear, it seems like Nvidia is breaking FreeSync functionality that previously worked. I don't know if I need FreeSync for any of the games I'm playing, but it's really nice to be able to have the option. Why put it in, then later sabotage it?