On 1/13/2024 at 8:34 PM, xrayer said:

Hi, thanks for info about the patch, I've been waiting for this a long time and I believed it could be patched such way, that it's just some stupid constant nvidiot's limitation...

Well, from what I read, it seems this patch unlock HDMI output only, not the DisplayPort, well?
Did/can someone try this if it will work also for 4k resolution @60Hz? I would like to try this but I have access to 4k monitor only at work and my GTX970 is in home PC and both things are not small enought to take it in a pocket or bag to meet them 😀

 

On 1/23/2024 at 5:50 AM, xrayer said:

I tested the patch on GTX 970 and Dell 4k LCD and the HDMI pixel clock limit patch works but there's another artifical limitation to max 1600p! It needs to ba patched too... I played with custom modes and timings. The max I can reach is 3840x1600 @89Hz - near 600MHz pixel clock. But Anything over 1600p is immediatelly refused - test mode failed. I need to remove this limit to utilize the native 4k resolution 3840x2160, pixel clock is enough to get 60Hz, maybe a bit more.

Hi,
using versions 368.81 of the nv4_disp.dll and nv4_mini.sys files modified to achieve 600MHz pixel clock, I was able to get 4k resolution (3840x2160) at 60Hz with a GeForce GTX960 connected to an LG32UQ850V 4k monitor via an HDMI-to-HDMI cable:

 

 

The same result can be obtained by using the modified version 355.98 of the same files.

A DP-to-DP cable connection allows 4K resolution, but only at 30 Hz, so the changes only cover the HDMI connection. The 3840x2160 resolution at 60Hz can also be achieved by using an HDMI-to-DP cable from the GPU to the monitor’s DP port.

So far, I haven’t encountered any issues, although I haven’t do intensive use on the test PC and, more importantly, I haven’t tested it with games.

Edited March 15Mar 15 by Andalu

What patching you did exactly to break 1600p limit?

I just followed the Yas's how-to (on drivers ver 355.98).

Edited August 31Aug 31 by xrayer

On 8/31/2026 at 10:38 AM, xrayer said:

What patching you did exactly to break 1600p limit?

I just followed the Yas's how-to (on drivers ver 355.98).

To reach the 600MHz pixel clock limit and get 4k resolution (3840x2160 @60Hz) you have to make the following changes, which are essentially the same as the instructions provided by Yas (my thanks to him).

Driver v355.98:

nv4_disp.dll

offset 00031C9D

replace 88 84 02 00 with 00 09 27 C0

nv4_mini.sys

1) offset 000001A0

replace C0 4B A1 00 78 1E 00 00 with 00 00 00 00 00 00 00 00

2) offset 004E402C

replace 88 84 02 00 with 00 09 27 C0

3) remove hex values from offset 00A14BC0 to the end.

Recalculate the checksum for both files.

~~~~~~~~~~~~~~~~~~~~~~~~

In the same way for the driver v368.81:

nv4_disp.dll

offset 0031122

replace 88 84 02 00 with 00 09 27 C0

nv4_mini.sys

1) offset 000001A0

replace 40 FB CB 00 78 1D 00 00 with 00 00 00 00 00 00 00 00

2) offset 005AD79C

replace 88 84 02 00 with 00 09 27 C0

3) remove hex values from offset 00CBFB40 to the end.

Recalculate the checksum for both files.

P.S.: I tested the modded files in XP x86 only.

Edited September 7Sep 7 by Andalu

@Andalu I can't believe the timing on this, thank you for this post. I literally just built a Windows XP retro machine with a GTX 980 Ti and verified this fix works with 2560x1440 @ 144 Hz with 368.81. I had copilot do the editing for me, and it calculated the checksums incorrectly, so I had to go back to Yas's original with 355.98 to have it figure out where it was messing up.

For the ease of anyone else, here are the modified files: https://drive.google.com/file/d/1qdq_xJeo4C3dvEGJswqwaToWlRvAlaEs/view?usp=sharing

If you'd rather modify them yourself, here are some detailed instructions from copilot:

Update: The 368.81 32-bit patch has now been tested successfully on a GTX 980 Ti.

The required byte replacements are literal:

nv4_disp.dll, offset 0x0031122:

88 84 02 00 -> 00 09 27 C0

nv4_mini.sys, offset 0x005AD79C:

88 84 02 00 -> 00 09 27 C0

At nv4_mini.sys offset 0x000001A0, replace:

40 FB CB 00 78 1D 00 00

->

00 00 00 00 00 00 00 00

Then delete everything from offset 0x00CBFB40 to the end of nv4_mini.sys.

For checksum calculation, use the PE checksum algorithm or a PE-aware tool. The important details are:

1. Treat the file as 16-bit little-endian words.

2. Skip all four bytes of the PE checksum field.

3. Fold carries during the word summation.

4. Add the complete file length after the summation.

5. Do not fold away the high bits of that final file-length addition.

For the tested 368.81 files, the resulting checksums were:

nv4_disp.dll: 0x0034BA9D

nv4_mini.sys: 0x00CC4FDD

Result: GTX 980 Ti on Windows XP 32-bit, 2560x1440 @ 144 Hz.

The files were tested from clean 368.81 originals. This result confirms the patch works for this configuration; 4K has not yet been tested.