GTX 970 does extreme coil whine since this game. ~2000 FPS brakes hardware?

[Torx]

Update:
Dang, it's called "coil whine". :/

Original:
That sound is not made by the fans, and to my experience usually occurs when a game runs with ~1000 FPS. With this game it is the loudest with the pointless logo animations that can’t even be skipped.

I ran a CPU stress test only, and there is no sound, so I guess it’s the GPU or even the PSU? I can hear this sound with FurMark and a GPU load over 30%.

Normally when game makes this sound, it’s a crap game with no frame rate limiter for the menus. So V-Sync always helped. Now V-Sync doesn’t help anymore, I can hear it even in-game running with 60 FPS on ANY game. And when the startup logo animations play its around 2000 FPS.

The thing is that it started yesterday when I bought and installed Lichdom. I never had this sound with Arkham City/Asylum and Heroes of the Storm before, and with those games it there now, too.

Does anybody know what this sound is? May it even be the PSU? Can ~2000FPS damage hardware? Also right now some less sharp noise is to hear OUTSIDE a game. Fans are on 0 RPM temp is 56C. But it fades after a while. And it’s not the fans. The FPS rate over all seems to be normal when palying a game.

[Torx]

By the way, Windowed Fullscreen doesn’t do any V-Sync.

I used the CPU’s GPU, so removed the 970 entirely and there was no sound. My 660 Ti made sounds but they always do just a bit.I guess it's the GPU than and not the PSU.

[Rick]

I have a 970 and am having the same problems. I can't help unfortunatley, but you're not alone... :/

[RiO]

Coil whine usually comes from the capacitors on the card pushing a lot of juice through. A sustained insanely high FPS rate (yes; like ~2000 FPS) can stress them enough to develop whine: whine is really a harmonics problem and even minute changes in the composition of the material, like teeny tiny microfractures caused by maxing out a capacitor for too long, can cause whine.

I'm not kidding regarding the damage such a high amount of FPS can do to a card, btw. A similar issue where there was an uncapped framerate in Blizzard's StarCraft II outright burned some cards out on the spot. That was also a case of some poor sod at Blizzard having forgotten to implement a frame cap in the main menu:
http://www.dailytech.com/Hot+Starcraft+II+is+Frying+Graphics+Cards+Blizzard+Issues+Temporary+Fix/article19224.htm


I already figured something weird was up when my card would suddently hit the fans full blast whenever I entered the menus, so I'd been avoiding the game anyway because I suspected uncapped FPS in the menus. This pretty much cements it.

Really; why do the menus not have a freaking frame limiter when the game itself has a vsync option, devs?

[RiO]

(cont.)

Originally posted by SouldomainTM:

By the way, Windowed Fullscreen doesn’t do any V-Sync.

Technically, windowed fullscreen always has vsync, since it uses the desktop window manager to render the current frame to screen. It gives you a kind of triple buffering where the game renders to an internal context without vsync and the window manager blits the most recently completed frame to screen during vsync.

The window manager is pretty good at this if you're running with hardware acceleration (i.e. Aeroglass) enabled. It's very nice with games that implement vsync but have frame-jitter / micro-stutter, as it usually solves the jitter. Ofcourse, it's still absolute murder for your graphics card on games that don't implement vsync themselves, as they'll just render a ton of unused frames into the buffer that the window manager eventually will blit to screen at a nice vsync-capped FPS.

[ottopower]

Turn on Adaptive Vsync via Nvidia's Control Panel
https://www.youtube.com/watch?v=A8IpHPAUKZw