NVCP Setting automatically changing to 3D Discover - Fixed?
There's been a lot of threads about this issue. In NVidia Control Panel, under Set up Stereoscopic 3D, the "Stereoscopic 3D display type" setting would automatically change from (in my case) "Asus 120Hz 3D LCD" to 3D Discover. One way many of us were dealing with it was to set up a batch file to change the setting back. It hasn't happened to me in several weeks. This could be because they actually finally fixed it in the drivers, but I think there's a second and more likely explanation: Due to the issue with high idle clocks at 144Hz, I permanently switched my refresh rate to 120Hz. I'm realizing that I did that right about the same time that I stopped having this issue. And it makes sense! The correct display type specifically says 120hz. Perhaps the issue all along has been that it can't keep that setting properly if you're running at 144hz. Is anyone on the more recent drivers still having this issue? Whether you are or not, please state what refresh rate you're running at. But for me, personally, whether coincidence or not, as soon as I permanently switched to 120Hz refresh rate, the problem is completely gone.
There's been a lot of threads about this issue. In NVidia Control Panel, under Set up Stereoscopic 3D, the "Stereoscopic 3D display type" setting would automatically change from (in my case) "Asus 120Hz 3D LCD" to 3D Discover. One way many of us were dealing with it was to set up a batch file to change the setting back.

It hasn't happened to me in several weeks. This could be because they actually finally fixed it in the drivers, but I think there's a second and more likely explanation: Due to the issue with high idle clocks at 144Hz, I permanently switched my refresh rate to 120Hz. I'm realizing that I did that right about the same time that I stopped having this issue. And it makes sense! The correct display type specifically says 120hz. Perhaps the issue all along has been that it can't keep that setting properly if you're running at 144hz.

Is anyone on the more recent drivers still having this issue? Whether you are or not, please state what refresh rate you're running at. But for me, personally, whether coincidence or not, as soon as I permanently switched to 120Hz refresh rate, the problem is completely gone.

CPU: Intel Core i7-5930K
Cooler: Thermaltake Water 3.0 Ultimate
Motherboard: Asus RAMPAGE V EXTREME, BIOS 2101
Memory: G.Skill 32GB (4 x 8GB) DDR4-2666
Storage: Intel 750 Series 1.2TB PCI-E SSD
Storage: Sandisk Ultra II 960GB 2.5" SSD
Video: 2x Gigabyte Gaming G1 980 Ti in SLI, Driver 362.00
Case: Thermaltake Core V71 Full Tower
Power Supply: EVGA Supernova P2 1200W 80+ Platinum
Monitor: ROG SWIFT PG278Q 120Hz 27.0" running 1440p in 3DVision
OS: Windows 10 Pro x64 Build 10586

Overclocks:
Processor: 4.4 GHz adaptive (1.296v under load), LLC7 input 1.92v
Processor Cache: 4.2 GHz offset +0.27v (max 1.212v under load)
Memory: 2666 15-15-15-35-CR2 oc'd to 3000 15-15-15-35-CR1 at 1.38v
GPU SLI: Stock voltage, 1455 MHz, 8000Mhz memory

#1
Posted 01/03/2016 05:34 PM   
Scroll To Top