Custom Resolution Utility (CRU)

[falkentyne]

Hi ToastyX
There seems to be a bug with the driver here.
I am using the "Creator's update hotfix" Nvidia driver. (Forgot the version but it was from a week ago).

1) With the XL2720z plugged into mini displayport on the mobile GTX 1070, I lose the ability to choose between 6 and 8 bit. It's 8 bit only, even at 60hz or 144hz.
2) attempting to use the Nvidia control panel (NVCP) to set a custom refresh rate that has a pixel clock higher than 359.85 MHz causes the Benq to black screen and the monitor is "Frozen" until the test resolution fails and times out (or I just press "No" blindly). The OSD on the Benq does not respond.
359.94 MHz (HT: 2001, VT: 1499, at 120hz) black screens even though the pixel clock is less than 360 mhz.

3) My favorite 125hz VT tweak I use on my R9 290x also does not appear if installed with your CRU (2080 HT, 1497 VT, pixel clock 389 MHz)
If tested in NVCP, monitor black screens (OSD unresponsive) until test times out.

However 359.70 MHz and 359.46 MHz (VT 1498 and VT 1497) both TEST successfully. So it can be added in the NVCP itself and it works.
However if I use your CRU to add them, the refresh rate does not appear at all. So the driver is blocking those pixel clocks if added through CRU, but using the NVCP works. (I would prefer NOT using the NVCP because I don't trust Nvidia).

However VT 1485 (356.58 MHz) DOES appear if I add this in your CRU, but this VT is not accepted properly by the monitor (I see the windows screen but an "Out of range" error pops up anyway). I have to use 1497-1502 which clearly isn't working

This seems to definitely be a driver issue with the laptop GPUs.

I guess this explains why "Advanced adapter properties" does not even load when I have it selected to use the Benq screen.

I have NOT tried an older driver like 378.xx. I suspect it won't work and it took me a long time to test this for you.

How do I report this to Nvidia? Will they even care? I'm 100% certain a monitor capable of HBR2 without reverting to 6 BPC at >359-480 MHz would work perfectly (since no one would care if 6 bpc is missing due to a bug anyway), so this is a pretty huge bug. I have no idea if this happens on desktop 10xx series gpus as I don't have one