NVIDIA Pixel Clock Patcher

[ToastyX]

(07-31-2015 11:53 PM)sdanzzz Wrote:  Great pixel clock patch, but for me it started causing some trouble with the drivers. I'm using a 970 with nVidia 350+ drivers and all of them kernel crash every once and again, most prominently when I open a new tab or window. Sometimes it happens during games or just watching movies. Not too much though, like once every hour or so, but it does seem odd. It wasn't happening on some of the earlier drivers and if I "unpatch" and remove the custom resolutions I added with CRU the drivers never crash.

The patcher makes very simple changes that shouldn't cause crashes. This seems more like a driver bug possibly exacerbated by higher pixel clocks. Recent drivers had issues with hardware acceleration causing driver crashes with Chrome, but that should have been fixed in 353.38: https://forums.geforce.com/default/topic...er-353-38/

(07-31-2015 11:53 PM)sdanzzz Wrote:  I'm using a Seiki 4k tv that runs at 30hz but can do 120hz at 1080p or 240hz at 720p, it's probably somewhat related to it as it doesn't recognize 120hz by default, only after I have added the resolutions using CRU and updated the firmware. The resolution doesn't matter really as it happens on both the 30hz and 120hz ones.

You shouldn't need the patch with the Seiki if you add an HDMI support data block in the custom extension block. That will make the driver treat the display as HDMI instead of single-link DVI. That might help resolve the crashes if the problem only affects higher pixel clocks with single-link DVI.

You also don't need the patch with HDMI if you use the NVIDIA control panel to add custom resolutions, but then some games might not recognize the higher refresh rate.