Hello Everyone!
I recently bought a 1070 Ti FTW2 card (I got it on a huge discount, that's why I went for pascal this late). I noticed that the G/P/M logos don't change if Precision XOC is closed. They stay the default color (by that, I mean the lowest temperature color). I can change the default blue to anything, it gets saved, but just won't change to the second color even though the temp limit has been reached, unless I open Precision XOC. When I open it, if it's atm over the temp limit, it instantly changes to the right color. Is this a bug or is it supposed to work like that? It's a fresh Windows install, no driver leftovers for sure. Also, I tried several versions of Precision, from the latest one to the first that supported the 1070 Ti (so from 6.2.7 to 6.2.2) and the last one before the card was released and supported (6.1.16) and they all had this "issue" (if it is one indeed). I would appreciate any help. Thanks.
 
Edit: So, I tested this a bit more. Turns out the LEDs actually freeze, when Precision XOC is closed. To test this I turned the fans all the way down, raised the temp thresholds to 40/60/80C for the 3 colors. When I did this, all 3 temps were under 40C (around 35) so the LEDs were off. I closed Precision XOC and opened games and benchmarks, and monitored temps with GPU-Z. The core quickly reached 70 degrees, but the LEDs stayed OFF (which, again, is the below 40C "color"). Then I opened Precision XOC without stopping the Heaven benchmark, and after about 10 seconds, the LEDs turned on with the approriate colors (60C color for the core as it was at around 70, 40C color for the memory and power as they were around 50). Then, I quickly closed Precision again, stopped and closed the benchmark and let the card cool off, monitoring temps with GPU-z continuously. The card cooled off to below 40C on the gpu, the vrm and vram as well. (which should make all the LEDs turn off) but the LEDs stayed green/blue/blue (G/P/M, so 60/40/40 threshold). I opened Precision and after about 10s again, all the LEDs turned off. So again, confirmation, the LEDs FREEZE, not just stay default, when precision is not open. Sorry for the long post if this is how it's supposed to work, just wanted to share my discovery, in case it's actually a bug. Thanks again.

Ah, sorry for the really long post then. Thank you for your help.
I saw a fresh, similar post (right after I posted mine, whoops, my bad) where the OP had a different card but with the same "issue", but somebody said that they set the LED colors, uninstalled Precision and they stayed functional even after that, meaning that it is indeed an issue. It's relieving to hear that nothing is actually wrong. Although I wonder how he does it... Anyway, do you think this will be "fixed" (or, rather, modified) with Precision X1? I'm assuming pascal will work just fine with it and XOC users will be updated to X1.

And a firmware or vbios update is out of the question? I don't know if it would actually be enough though.

Alright, thank you very much for your time.

Sajin
Yes, you need precision running in the background for them to work correctly. IMO, you shouldn't need precision running in the background for them to work correctly.

 
I am not sure this is the case.. at least for my 1080 ftw2. Once you run XOC and adjust your GPM led settings it should be saved to the card itself. I never have XOC running and I have no issues with my GPM lights changing colors once my set temperature are reached.

I am suggesting that I don't need XOC running ( or even installed) for my GPM leds to change colors when temperature thresholds are reached..

Lee7b

Sajin
Yes, you need precision running in the background for them to work correctly. IMO, you shouldn't need precision running in the background for them to work correctly.

 
I am not sure this is the case.. at least for my 1080 ftw2. Once you run XOC and adjust your GPM led settings it should be saved to the card itself. I never have XOC running and I have no issues with my GPM lights changing colors once my set temperature are reached.

The 1080 ftw2 doesn't include the thermal led display system.
 

auToeXeC_g33k
It does, i just checked the spec sheet.

Ok, yeah, it does...
 

Any way to confirm this?

Well I would rather not do that unless I'm forced to, is there any chance that evga customer support might be able to confirm anything? 

I sent them an email, as I'm in the EU and this late I saw it as a better option. I'll update this thread as soon as I get a definitive answer.

Update
I asked for confirmation on whether or not I should RMA my card, and if it seems faulty or not. The answer was:
"Thank you for coming back with more details, the LED on the Graphics card seems to working normally.
However the illumination of the LED may vary  depending on the thresh hold of Temperature."
It seems to me that they're not really getting what the "issue" is, even though I described it even more precisely as I did here. Anyway, they're not saying it's faulty, and it works with precision open, AND a couple days ago they started working without it (although not as precisely, sometimes it takes some mtime to adjust to temp limits, but eventually they change), so I might as well just call it a day. Anyone who finds this thread with the same issue, I tell you: If it works with precision, you're fine. Try older versions, even the oldest your card supports, change it with that, play around a little a bit, and in my experience, they will work after some point by some sort of magic.
Thank you everyone who posted, I consider this solved.

 

Actually I do OC, I'm just used to closing the app after the fact (got a pretty stable and well cooled OC setting). Oh well, guess I'll leave it open from now on.

bob16314
From what I'm beginning to understand, whether it's right or not, is the last RGB color/temperature scheme set in Precision should get written to the memory/EEPROM of the MCU that controls the G/P/M LEDs and remain that way unless changed again and remain that way even if Precision isn't running..That jives with what EVGA told you and what others have said.

So what does it take to get the RGB color/temperature scheme to get saved to the MCU's memory?..I don't exactly know..Maybe a restart without closing Precision?..Maybe a shutdown/cold start with 'Fast startup' (Win 8/10) disabled in the Windows Power Options with or without Precision open/closed?..There must be some trick to it..Or maybe there is actually something wrong, but I'm thinking not.

You could PM somebody (Lee7b maybe) that has the same/similar RGB LED card to find out how they do it..You need 10 or more forum posts (which you have) to send a PM and the other member needs the same to reply to a PM..Most forum members will be glad to reply to a PM (or PM the link to this thread) and help out.

Just my input on the deal here..Good luck.

Well, thank you for that. Something IS actually loaded onto the card, because previously it didn't work at all (I can't remember if it worked before opening precision the first time with this card, but after that it was broken all the way), and now after some time (like not exactly when it reaches 60C threshold, but some time after that, minutes usually) it actually changes colors now. When I load games, benches, it eventually turns green, when I quit, it eventually goes blue, and then blank/black. I will definitely try your suggestions with the restart and fast boot, since I've fiddled with those since I got the card, so it could have done something to make it work and not work, I don't know for sure, I'll try and update the thread if I find something out. If I can't see any pattern, I might just take your advice and PM someone with greater knowledge.

Sajin

bob16314
So what does it take to get the RGB color/temperature scheme to get saved to the MCU's memory?

On my card I can't get the MCU's to remember the settings no matter what.

Just to be clear: at least part of the settings are remembered in my case. I always change green (the 2nd color) to purple to match my build's rgb, and when the leds for some magical reason actually change without precision, they change to purple, not the standard stock green. The problem seems to be with the detection of reaching the set temp limit (or saving the temp limit threshold, but just the number, since colors are saved).