Decon01
Noticed a problem with precision XOC 6.1.8 not down clocking past base clock on my 1080TI SC2 when I close two specific games. I noticed it when I was playing Wolfenstein: The Old Blood and also Wolfenstein: The New Order. I compared it when playing other games like Ark: Survival Evolved and it down clocks past stock once closed.
 
Anyone have any ideas? A reboot resolves the issue but I suspect there might be an issue with Wolfenstein possibly not releasing all of its resources when closing or Precision thinks its not closed so it doesnt down clock.
 
1 Addition I noticed since I can replicate on command basically. Once the issue happens it will never down clock at all. Opening other games it will overclock to boost and past as it should but will never drop below base once you close the application after playing the two Wolfenstein games I mentioned.

What sort of monitor setup are you using? There is a known bug with Pascal, completely unrelated to EVGA or any of their software, where Pascal cards won't downclock at idle with certain monitor set ups. This is usually seen when using a 144Hz or higher refresh rate monitor, especially when you are running a multi monitor setup and the second monitor has a lower refresh rate. Though people have run into the issue with just a single monitor.

The only known way, that seems to work for everyone, to get the card to lower it's clock speeds outside of games is by lowering the refresh rate of the monitor to 120Hz or lower via the Nvidia Control panel. I personally experience this issue as well, and have gotten into the habit of leaving the Nvidia Control panel open throughout the day while I'm using my system, toggling between 120Hz when idle and 144Hz before launching a game.

It's annoying but it seems to be the only solution that works 100%. I've researched this issue extensively, and have seen other suggestions, but they don't always work and some are not even possible for everyone to take advantage of. One such being only using Displayport inputs for your monitors, something I don't have the option of doing.

Operating System
    Windows 7 Professional 64-bit SP1
CPU
    Intel Core i7 3770K @ 3.50GHz
    Ivy Bridge 22nm Technology
RAM
    16.0GB Dual-Channel DDR3 (9-9-9-24)
Motherboard
    ASUSTeK COMPUTER INC. SABERTOOTH Z77 (LGA1155)
Graphics
    VS24A (1920x1200@59Hz)
    VS24A (1920x1200@59Hz)
    VS24A (1200x1920@59Hz)
    NVIDIA GeForce GTX 1080 Ti (EVGA)
Storage
    238GB Samsung SSD 840 PRO Seri (SSD)
    2794GB Western Digital WDC WD3003FZEX-00Z4SA0 (SATA)
    931GB Western Digital WDC WD1003FZEX-00MK2A0 (SATA)
Optical Drives
    TSSTcorp CDDVDW SH-S223Q
Audio
    Creative X-Fi Audio Processor (WDM)
 
All my monitors are Asus and are 60Hz only.

Ill try that. Didn't think about the driver and it appears there are issues with 384 so ill try 382.

Those monitors only support HDMI and DVI for digital connections. What sort of adapter are you using to run the third monitor? DP adapters in particular may not allow the card to recognize the resolution it is driving correctly and cause the card to be overly cautious with the pixel clock, running the card faster than needed for the given resolution requirements of all three monitors.

Confirmed it was the nvidia driver. Seems that this down clock issue is widespread on 384. Thank you to pstlouis!

If I have firefox open with several windows and tabs, my card won't downclock completely.

Thanks, Sajin. That wasn't an isse of mine, I just wanted to point out that there might be other software keeping the clocks up. Also there is a button in the main gui of PXOC doing that (on purpose) as well as NVidia graphics driver power settings in the 3D settings area.