Settings revert to RGB from YCbCr444 in Nvidia after 1080ti upgrade; screen going black too

[BobCharlie]

Recently upgraded to a MSI GTX 1080ti card coming from a GTX 970, which never had issues. 1kw Super Nova G2, 16gb Ripjaw, FX8350, Win 7 SP1.


After installing the 1080ti and doing a clean install of most recent 390.77 driver, had issues getting my Samsung 4k monitor to STAY off the "PC" setting on the TV's HDMI settings, as every time a game loaded, etc. the TV would would revert back to the PC setting, which blocks a ton of the TV's internal settings from being used (HDMI color settings, HDR, dejudder, etc.). That was seemingly fixed by using the HDMI preset "Gaming Console" (I've added this info as it still might be related, unsure at this point). The other issue has been the YCbCr444 setting is routinely reverting back to the default RGB output color depth (which looks like garbage on a 55" 4k monitor) and just now with a couple windows open in the background while watching a you tube video, screen went black and TV reverted to it's default "Nothing detected" message. Could still hear the audio (external out going to stereo; not using HDMI audio) so pulled the HDMI and reinserted, and the signal was detected again. Checked nvidia settings and they once again reverted to the RGB color depth nonsense.

ANY ideas what's going here? GPU temps were ice cold in the low 20's when this happened. Have been gaming prior w/o issues in-game.

 

[helpstar]

Remove the nvidia drivers completely by using DDU uninstaller and install the latest from nvidia.com again.

Check for firmware updates for the Samsung TV and try a different HDMI cable.

update the motherboard´s BIOS of you system

 

[BobCharlie]

Remove the nvidia drivers completely by using DDU uninstaller and install the latest from nvidia.com again.

Check for firmware updates for the Samsung TV and try a different HDMI cable.

update the motherboard´s BIOS of you system

Going to try DDU now and check if anything for the TV is available.

 

[BobCharlie]

DDU was buggy and would hang in safe mode. Had to use CCleaner to remove leftover registry and physically delete entries that control panel stated were not there from the botched removal. Wouldn't auto restart either.

After going through that, and updating the TV's software which jumped fairly high in the rev. number sequence, it took awhile but finally recurred. Like last time, was watching a video on you tube (actually watched a bunch w/o issue) and screen dropped. Temps are in the upper 20c range and card was on lowest auto-clock preset. After unhooking the hdmi and reconnecting, the TV "saw" the connection again. After a manual PC restart though shortly after, nvidia was back on the RGB setting and TV was back on the "PC" preset, which I'm assuming is due to the signal drop.

Any way to pinpoint if it's something with the PC exclusively or the TV? FWIW, I have over 50 hours gaming on the card atm (ultra settings @4k with internal upscaling on top of that) pushing it as far as it can handle, and have yet to see this happen in-game. Could it be an issue with some sort of low-usage power saving state that's tripping the TV into thinking the connection was severed?

Board is a 990FXA-GD80 and it shipped with the last msi BIOS update available (from 2012 era) for win7 variants.

 

[helpstar]

If DDU hangs, I would say something is wrong with the hardware (motherboard, GPU, power supply, HDD, RAM). Also could be something in windows.

Did you use ccleaner before or any other tuning tool?

Check the system integrity:
https://support.microsoft.com/en-us/help/929833/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system

 

[BobCharlie]

CCleaner was used after. It hung during the clean/restart setting, and after about 15 minutes, I forced it shut via task manager and rebooted, then tried again w/o the auto-restart option. Hung like before. Checked control panel and nvidia stuff was "gone" but still stuck in the uninstall list, so I used cc to delete the left over entries and loose reg. junk.

Samsung Magician is stating the 850 pro is good. Mass Effect Andromeda pushes around 15gb of the 16gb total of RAM and 10gb of page file with all settings nearly maxed (had to back some off as the game can squeak into the upper 16gb range), and has yet to falter. Have about 120 hours of the game logged, so doubt it's RAM at this point or I suspect it'd be crashing in-game constantly with blue screens or something.

Again, this didn't start happening until the 1080ti was added, and ONLY so far during very low browser-usage states.

 

[BobCharlie]

EDIT: Happened again when I just hit enter for the last reply 😡

 

[BobCharlie]

Thanks for mentioning the scannow option. I completely forgot that existed. It stated there were issues and it repaired them. Skimmed the log as best as possible; hard to tell what it actually fixed as the log was large, but it might have "fixed" some older.netframework stuff, etc.

Ran a 2nd time just to be sure and it stated nothing needed fixed. Log on 2nd run was nearly half the size as the first run, so there might have been quite a few issues initially.

Will definitely update on progress if that solved the issues or not. Thank you!

 

[helpstar]

Did you alter the pagefile settings manually? Set it to windows managed.

check your RAM nonetheless

 

[BobCharlie]

Yes, it's set to windows managed. PF had been off for years as it wasn't needed until now.

Got another screen drop a little while ago, so looks like it might be something else. I'll try mem test and see if it reveals anything.

 

[BobCharlie]

Ran mem test until it finished (about 11 hours). 48 passes and ZERO errors/faults. RAM appears OK.

Running out of ideas. Card has both 4-pin power connectors, have a small wooden dowel rod as a prop on the shroud to prevent sagging, stock cpu clocks, stock RAM clocks, stock GPU clocks (which hit 1950Mhz as the card is an OC model- which it handles w/o issue), card's not overheating (still waiting nearly 2 weeks for liquid cooler to arrive though), PSU is overkill for the build so plenty of current on-demand if needed.

But the drops still only happen on light usage. And the last 2 times it's happened at the same time I've hit a "submit your answer", which I'm not thinking is coincidence. Has happened with Chrome and Firefox, though I dropped Chrome completely and uninstalled.

 

[BobCharlie]

Spent some time perusing the nvidia drivers forum and found others with a similar issue (in their cases, the screen recovers with an error vs. mine where the TV fails to redetect signal). For them, it's happening under virtually identical scenarios of "watching you tube or browsing w/ Firefox and driver crashes; games are NOT crashing, etc.". Something possibly to do with how FF is accessing the gpu driver with hardware acceleration enabled, though it might be speculation. Chrome apparently does something similar, and problem is more inherent with win7 atm.

Checked Event Viewer and there's a ton of "nvlddmkm error 13" warnings littering log box. Gonna try and disable HW acceleration in FF and see if that helps. Some claim older drivers stop the issue as well, but going hold off going that route atm.

 

[helpstar]

would reinstall windows to check if it´s software related

did you overclock your system? undo and test

2x8PIN PCIe power is plugged in? I think it´s just a typo (2x4pin), but wanted to ask to be sure 😉

 

[BobCharlie]

Yeah, that's a typo. Both are connected.

I've disabled HW acceleration via FF options. So far, no crashes. Time will tell.

As mentioned, this seems to be a conflict with the browsers and the gpu driver or something along those lines as nvidia in the forum are trying to reproduce. Others seem to experience the same thing with their 10xx nvidia cards after doing an upgrade to one.

 

[BobCharlie]

Just an update for those that it might help:

1. The RGB reverting seems to be an actual fault with some newer Samsung TV's that Samsung seems to either be ignoring, or unwilling to modify on a software level. Basically, the set auto-detects a "PC" regardless of user input on the Edit tab within the TV's settings. i.e. set to Game Console, Blu-Ray, etc. and every time the PC starts up, the TV treats it like a new device it's detected. Since the generic "PC" setting can NOT use YCbCr444 setting, it reverts to RGB. Lower settings like YCbCr420, might not revert to RGB if it's within the ability of the preset to display.

MANY complaints on the Samsung site for various models that are affected by this. WHY it started happening now vs. before, is puzzling, but oh well. Gotta manually reset as a work around every time.

2. The black screen issue with a Firefox open is definitely bypassed by turning HW acceleration off within FF settings. Only issue I can find is random yahoo pages can be a little buggy with displaying embedded videos or text i.e. load a page, scroll down, everything within the page borders disappear; reloading page fixes it. Very minor irritation vs. loosing the entire screen and having to unplug the HDMI. This is the ONLY time this happens. Hours of gaming, watching videos/surfing (HW acceleration off), etc. do NOT cause issues otherwise.

Nvidia just released driver 391.24, and in the details, was a bug fix specifically for a Firefox related crash, though it didn't fix my issue as it went black within 60 seconds of turning HW acceleration back on. Hopefully FF or nvidia fixes this in the future. In the mean time, turn off Hardware Acceleration in FF settings as a viable work around with minimal impact.