Post Reply
NVIDIA Pixel Clock Patcher
07-15-2015, 11:08 AM
Post: #421
RE: NVIDIA Pixel Clock Patcher
does this work with 353.49?
Find all posts by this user
Quote this message in a reply
07-17-2015, 04:35 AM
Post: #422
RE: NVIDIA Pixel Clock Patcher
(07-15-2015 11:08 AM)shaca Wrote:  does this work with 353.49?
It should. I don't see anything different about 353.49.
Find all posts by this user
Quote this message in a reply
07-17-2015, 04:48 AM
Post: #423
RE: NVIDIA Pixel Clock Patcher
(06-09-2015 03:58 PM)jarda Wrote:  Is support for Windows 10 ??
The Windows 10 driver seems to use a different file name, so I will have an update for that soon.
Find all posts by this user
Quote this message in a reply
07-31-2015, 04:17 AM (Last edited: 07-31-2015, 04:17 AM by ZeroH)
Post: #424
RE: NVIDIA Pixel Clock Patcher
(07-17-2015 04:48 AM)ToastyX Wrote:  
(06-09-2015 03:58 PM)jarda Wrote:  Is support for Windows 10 ??
The Windows 10 driver seems to use a different file name, so I will have an update for that soon.

I upgraded to Windows 10 without any problems and was able to recreate the custom resolution with the higher refresh rate in NVIDIA Control Panel. Didn't have to reinstall anything. Love it!
Find all posts by this user
Quote this message in a reply
07-31-2015, 11:53 PM
Post: #425
RE: NVIDIA Pixel Clock Patcher
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.

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. I've tested my gtx's memory with memtestG80 (OPEN) and I get no errors, so my vram seems to be OK.

Any suggestions or logs that I could provide so you can check this ?

Thanks
Find all posts by this user
Quote this message in a reply
08-01-2015, 08:26 PM
Post: #426
RE: NVIDIA Pixel Clock Patcher
(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.
Find all posts by this user
Quote this message in a reply
08-02-2015, 08:35 AM (Last edited: 08-02-2015, 02:08 PM by jdmstanced)
Post: #427
RE: NVIDIA Pixel Clock Patcher
i'm having problem with overclocking my ASUS PB Series PB278Q 27"
i have NVIDIA GTX 970. hooked up using Display Port cable. Tried HDMI cable too.

i followed all the steps. patching, CRU and all.
But even increasing the rate by one won't let me allow it. My screen blacks out and says out of range.

What am i doing wrong?..


And nvlddmk.sys file is signed by Edgard roberto, not NGO
Find all posts by this user
Quote this message in a reply
08-02-2015, 02:41 PM
Post: #428
RE: NVIDIA Pixel Clock Patcher
(08-02-2015 08:35 AM)jdmstanced Wrote:  i'm having problem with overclocking my ASUS PB Series PB278Q 27"
i have NVIDIA GTX 970. hooked up using Display Port cable. Tried HDMI cable too.

i followed all the steps. patching, CRU and all.
But even increasing the rate by one won't let me allow it. My screen blacks out and says out of range.
The PB278Q is not overclockable, but if you want to add custom resolutions with NVIDIA, make sure "Custom extension block" is selected. Also, with HDMI, you need to add an HDMI support data block in the custom extension block or it will act like single-link DVI, which normally doesn't support 2560x1440 @ 60 Hz. DisplayPort and HDMI shouldn't need the patch either, but single-link DVI does.
Find all posts by this user
Quote this message in a reply
08-02-2015, 10:35 PM
Post: #429
RE: NVIDIA Pixel Clock Patcher
(08-02-2015 02:41 PM)ToastyX Wrote:  
(08-02-2015 08:35 AM)jdmstanced Wrote:  i'm having problem with overclocking my ASUS PB Series PB278Q 27"
i have NVIDIA GTX 970. hooked up using Display Port cable. Tried HDMI cable too.

i followed all the steps. patching, CRU and all.
But even increasing the rate by one won't let me allow it. My screen blacks out and says out of range.
The PB278Q is not overclockable, but if you want to add custom resolutions with NVIDIA, make sure "Custom extension block" is selected. Also, with HDMI, you need to add an HDMI support data block in the custom extension block or it will act like single-link DVI, which normally doesn't support 2560x1440 @ 60 Hz. DisplayPort and HDMI shouldn't need the patch either, but single-link DVI does.

That's weird because this guy oced the same monitor as mine.
http://www.tweaktown.com/tweakipedia/18/...index.html

i did set it to Custom extension block. Tried both HDMI and display port. i can't get my monitor to oc, not even 61 from 60.
I made a custom resolution on nividia control panel, window setting, CRU, and other softwares but they won't let me go past 60. It shows out of range.
Find all posts by this user
Quote this message in a reply
08-03-2015, 11:26 AM
Post: #430
RE: NVIDIA Pixel Clock Patcher
(08-02-2015 10:35 PM)jdmstanced Wrote:  That's weird because this guy oced the same monitor as mine.
http://www.tweaktown.com/tweakipedia/18/...index.html
He didn't check for frame skipping. The PB278Q is known to skip frames at refresh rates greater than 60 Hz. Some people have mentioned this in the last few comments. There's also a newer version with a different panel: http://wecravegamestoo.com/forums/monito...-ahva.html

(08-02-2015 10:35 PM)jdmstanced Wrote:  i did set it to Custom extension block. Tried both HDMI and display port. i can't get my monitor to oc, not even 61 from 60.
I made a custom resolution on nividia control panel, window setting, CRU, and other softwares but they won't let me go past 60. It shows out of range.
You might have the newer version with newer firmware that won't allow anything except 60 Hz. One way to know for sure is to try 60.1 Hz. If that works, then it's not an issue with custom resolutions. Most monitors that only accept 60 Hz will accept around 59.5-60.5 Hz.
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


User(s) browsing this thread: 13 Guest(s)