Custom Resolution Utility (CRU)

[moecre]

(07-11-2026 08:34 PM)MUC Wrote:  I assume you have already tried resetting all EDIDs in the Windows Registry using "reset-all.exe" and restarting the system. If the behavior remains unchanged, the AMD graphics driver is unfortunately having trouble with the EDID structure. I wouldn't know how to resolve this other than by using a larger EDID.

Good Morning MUC,

yes, I tried that, the PC restarts with 640x480@60Hz.

(07-11-2026 08:34 PM)MUC Wrote:  

1. Have you asked Blustream if the SM11EARC-8K can also be flashed with EDIDs larger than 256 bytes (i.e., more than 2 blocks)?
   

I'm going to write them tomorrow.

(07-11-2026 08:34 PM)MUC Wrote:  

1. Have you tested the MacBook?
   

Yes, I tried the MacBook from time to time, it shows a slightly different behaviour than the PC in some scenarios. Your EDID actually works for the MacBook, see     . The panel doesn't show the refresh rate though, is there another way to debug the current refresh rate on macOS?

(07-11-2026 08:34 PM)MUC Wrote:  

1. Have you tested whether an EDID override, applied directly to the AMD PC using CRU based on the original monitor EDID, would work?
   

I used CRU only for altering EDID files, haven't done any overwrites on the source PC yet.

I tested the original EDID without overwrites though, see     and     . The monitor seems to display the 5120x1440 in a 4K 16:9 picture. That's btw the same behaviour if I change the dip switches on the device to pass-through. I guess that's a Blustream device thing, maybe related to the small EDID.

Thanks for your help!

[moecre]

(07-11-2026 08:34 PM)MUC Wrote:  

1. Have you asked Blustream if the SM11EARC-8K can also be flashed with EDIDs larger than 256 bytes (i.e., more than 2 blocks)?
   

They came back to me, saying that both devices, SM11EARC-8K and SW41AB-8K are limited to 256 bytes EDIDs.

[MUC]

(07-13-2026 08:53 AM)moecre Wrote:  They came back to me, saying that both devices, SM11EARC-8K and SW41AB-8K are limited to 256 bytes EDIDs.

Okay, that’s a shame. But as I understand it, the 256-byte EDID you received from Blustream works with the AMD graphics driver. I’ll take a closer look again at the details and make another proposal based on everything we can squeeze into the available space.

[MUC]

Please try the 256-byte EDID in the attachment on the SM11EARC-8K. If possible, test with all source devices.

[moecre]

(07-13-2026 08:13 PM)MUC Wrote:  Please try the 256-byte EDID in the attachment on the SM11EARC-8K. If possible, test with all source devices.

Hi Muc,

test summary: it seems as a lot of resolutions and a refresh rate up to 120Hz are possible on PC. But not the desired 5120x1440@144Hz. Same on MAC, but doesn't matter what I choose the display stays black, not so on PC.

Here are my test results:
   
   

  edid-test-EDID_SM11EARC-8K_AORUS_CO49DQ_04.txt (Size: 831 bytes / Downloads: 7)
   

[MUC]

(07-14-2026 09:09 AM)moecre Wrote:  test summary

The EDID read by the AMD driver differs slightly from what I posted, but that shouldn't really matter.

The differing behavior of the computers is certainly interesting. My Nvidia PC won't boot at all using EDID #4, which I modified based on the Blustream suggestion, whereas your AMD PC seems to handle it just fine. However, if I activate the EDID externally only after Windows has already booted, I CAN select 5120 x 1440 @ 144 Hz on my Nvidia PC. That option is missing for you, likely because that mode isn't marked as "preferred" in the EDID. Attached is EDID #5, with the "preferred" flag enabled for 5120 x 1440 @ 144 Hz.

Unfortunately, it’s unclear whether a 256-byte EDID can be found that works for both the AMD PC and the Apple MacBook. If you want to continue experimenting, I suggest starting a separate thread. Please post the link here if you do.

[ToastyX]

(07-13-2026 08:53 AM)moecre Wrote:  They came back to me, saying that both devices, SM11EARC-8K and SW41AB-8K are limited to 256 bytes EDIDs.

There are actually two new ways to define higher resolutions in a CTA-861 extension block instead of DisplayID, but these are newer standards, so I'm not sure if AMD's driver supports them yet, and I only have a way to do one of the methods right now (the new video formats data block).

Try this EDID:
  AORUS-CO49DQ-5120x1440-60-120-144.bin (Size: 256 bytes / Downloads: 8)

[MUC]

(07-15-2026 01:55 AM)ToastyX Wrote:  but these are newer standards, so I'm not sure if AMD's driver supports them yet, and I only have a way to do one of the methods right now (the new video formats data block).

Try this EDID

Yes, that’s a good idea.

My Nvidia GeForce RTX 5060 Ti (running driver 610.47) supports the Resolution IDs (RIDs) you included, as well as the associated CTA-861 Optimized Video Timing (OVT). While it doesn't exactly match what the monitor expects, it’s worth testing. There’s a good chance the monitor can handle it. For comparison:

5120 x 1440 @ 144 Hz

Detailed Timing Descriptor of the monitor:
Front porch: 48 / 3
Sync width: 32 / 10
Back porch: 240 / 28
Sync polarity: + / -
Scan rate: 213.265 kHz
Pixel clock: 1160.16 MHz

CTA OVT (RID 10, FR 15):
Front porch: 96 / 20
Sync width: 32 / 8
Back porch: 32 / 82
Sync polarity: + / +
Scan rate: 223.200 kHz
Pixel clock: 1178.496 MHz

[Alkerion]

Hi,
I've installer CRU 1.5.3 on my W11 PC, I own a ASUS TUF GeForce RTX 5070 Ti OC Edition with a LG UltraGear 40WP95X-W (5120 x 2160 pixels, 39.70") monitor.
CRU doesn't detect it correctly, and resolution ara also missing.
Already tried reset-all.

[ToastyX]

(Today 11:59 AM)Alkerion Wrote:  Hi,
I've installer CRU 1.5.3 on my W11 PC, I own a ASUS TUF GeForce RTX 5070 Ti OC Edition with a LG UltraGear 40WP95X-W (5120 x 2160 pixels, 39.70") monitor.
CRU doesn't detect it correctly, and resolution ara also missing.
Already tried reset-all.

Looks fine to me. Did you check the extension blocks? 5120x2160 is usually in the DisplayID extension block.