Custom Resolution Utility (CRU)

[ToastyX]

(04-08-2026 07:04 PM)Huexxx Wrote:  I have tried several ways to solve it without sucess... I know that the problem is that Win11 is harder on HDMI handshake, and when the screen goes black... it takes EDID from monitor and it sees that working resolution is not on EEPROM EDID and fails.

So, what can I do to solve this?

The only ways I think it can work are:

- EDID Emulators.
- Extract working EDID from CRU (to .bin) and create an inf with Monitor Asset Manager (Moninfo). Once installed it should avoid EDID extraction from EEPROM and work... but maybe it will be hard to install on Win11 due to digital signature.
- Modify EDID on monitor replacing 2K 75Hz with a working mode.

Any thoughts?

That's not a Windows 11 issue. It's a driver bug, likely in Intel's graphics driver. An EDID emulator should work around the problem since it will keep the connection. CRU already does the same thing as installing an .inf file, and CRU can export .inf files, so that wouldn't make a difference. Modifying the EDID on the monitor might be possible, but my EDWriter doesn't support Intel GPUs. Another option to is to try the alternative method mentioned in the first post, which uses an Intel-specific method that might work around the problem.

[sushank21x]

Hi ToastyX,

I was trying to overclock my AOC G2260VWQ6, but as soon as I go above 76Hz it shows “Input Not Supported.”

I’ve tried adjusting range limits, max pixel clock, and a few other things in CRU. I’m pretty new to this, so I was also following some ChatGPT guidance, but no luck so far. I’m sure I managed to overclock it once before using CRU, just don’t remember exactly what I did.

I’ve also experimented with different timing presets, but still hitting the same issue.

Do you have any idea what I might be missing? I’m trying to push the maximum Hz possible at 1280x1080 resolution.    

[ToastyX]

(04-10-2026 05:21 PM)sushank21x Wrote:  I was trying to overclock my AOC G2260VWQ6, but as soon as I go above 76Hz it shows “Input Not Supported.”

I’ve tried adjusting range limits, max pixel clock, and a few other things in CRU. I’m pretty new to this, so I was also following some ChatGPT guidance, but no luck so far. I’m sure I managed to overclock it once before using CRU, just don’t remember exactly what I did.

I’ve also experimented with different timing presets, but still hitting the same issue.

Do you have any idea what I might be missing? I’m trying to push the maximum Hz possible at 1280x1080 resolution.

"Input not supported" means the monitor is rejecting the signal. There's nothing you can do on the computer's end to bypass the monitor's limitation. The range limits is information for the computer and does not affect what the monitor does.

[fv101]

Hello people and toasty! I own a samsung g55c and the dp 1.2 port cooked itself somehow and i do not have warranty so i'm stuck using HDMI 2.0 on this very new monitor.. (specs are: 10 bit @ 1440p/165hz at max capability)

It doesnt even support 10 bit color @1440p/144hz but i use 8 bit with dithering

anyways, i've been trying to overclock it using cru back to 165 but i can only hit 149 because the 600mhz pixel clock is the limiting factor. How do i get around this?


ive tried messing around with the timing options but native pc is the lowest so
PLEASE HELP. displayport doesnt work for some reason even though the monitor
detects it being plugged in?


   

---

(Yesterday 10:33 PM)fv101 Wrote:  Hello people and toasty! I own a samsung g55c and the dp 1.2 port cooked itself somehow and i do not have warranty so i'm stuck using HDMI 2.0 on this very new monitor.. (specs are: 10 bit @ 1440p/165hz at max capability)

It doesnt even support 10 bit color @1440p/144hz but i use 8 bit with dithering

anyways, i've been trying to overclock it using cru back to 165 but i can only hit 149 because the 600mhz pixel clock is the limiting factor. How do i get around this?


ive tried messing around with the timing options but native pc is the lowest so
PLEASE HELP. displayport doesnt work for some reason even though the monitor
detects it being plugged in?



its very bumpy and weird too on blur busters which it isnt on stock 144hz???

[ToastyX]

(Yesterday 10:33 PM)fv101 Wrote:  Hello people and toasty! I own a samsung g55c and the dp 1.2 port cooked itself somehow and i do not have warranty so i'm stuck using HDMI 2.0 on this very new monitor.. (specs are: 10 bit @ 1440p/165hz at max capability)

It doesnt even support 10 bit color @1440p/144hz but i use 8 bit with dithering

anyways, i've been trying to overclock it using cru back to 165 but i can only hit 149 because the 600mhz pixel clock is the limiting factor. How do i get around this?

I don't have a way to get around that limit. You won't be able to get 165 Hz except at a lower resolution. You might be able to squeeze in a few more Hz by reducing the timing parameters, depending on what the monitor can handle. If motion seems jumpy, the monitor might be skipping frames beyond 144 Hz with HDMI, in which case there is nothing you can do. Use this test with a camera to verify: https://testufo.com/frameskipping

[juanme555]

Hello Toasty, i have a question, do you have an Arc gpu?

[ToastyX]

(Today 07:30 PM)juanme555 Wrote:  Hello Toasty, i have a question, do you have an Arc gpu?

No, I don't.