Post Reply
Custom Resolution Utility (CRU)
09-19-2015, 04:38 AM
Post: #1661
RE: Custom Resolution Utility (CRU)
(09-18-2015 10:37 PM)DustyShinigami Wrote:  Hi

First forum post. I'm having problems adding my own custom refresh rates with the Custom Resolution Utility. With my last monitor it worked no problem, but I got a new one today - a BenQ XL2420G - and no matter what I do, whenever I check my monitor's list of refresh rates, the ones I added never show up. I'm trying to add 70 and 80Hz refresh rates.

The XL2420G has two scalers in one.
Make sure you are using the classic scaler (The Z scaler) that has the blur reduction module, if you are trying to add low refresh rates like that. There should be a hardware switch on the back of the monitor to toggle between the scalers. You have to power it off each time, though.

The gsync scaler is not a hardware scaler, and I don't think it supports those low refresh rates. People were getting out of range errors trying to add 75hz and 85hz to the Asus ROG Swift, which also uses a gsync scaler. I don't know much about the gsync modules, and I don't know if what it supports is controlled by Nvidia themselves, by the video card or if the monitor makers can add things or not.
Find all posts by this user
Quote this message in a reply
09-19-2015, 01:33 PM
Post: #1662
RE: Custom Resolution Utility (CRU)
Okay, thanks. I tried connecting the monitor via HDMI, DVI single and DVI dual, but it didn't make any difference; it wouldn't accept 70 or 80Hz. "/ It's weird because it'll manage 85, 100 and 144Hz no problem, so you would think it could do any refresh rate inbetween those. Also my last monitor, which was smaller, could manage 70Hz without a problem.
Find all posts by this user
Quote this message in a reply
09-19-2015, 01:49 PM
Post: #1663
RE: Custom Resolution Utility (CRU)
(09-18-2015 10:37 PM)DustyShinigami Wrote:  First forum post. I'm having problems adding my own custom refresh rates with the Custom Resolution Utility. With my last monitor it worked no problem, but I got a new one today - a BenQ XL2420G - and no matter what I do, whenever I check my monitor's list of refresh rates, the ones I added never show up. I'm trying to add 70 and 80Hz refresh rates.
You didn't mention what video card you have or how you have the monitor connected. If you have an NVIDIA card, you need to use a custom extension block as described in the main post. If you're using HDMI, you need to add HDMI support to the extension block.
Find all posts by this user
Quote this message in a reply
09-19-2015, 02:07 PM
Post: #1664
RE: Custom Resolution Utility (CRU)
(09-17-2015 11:27 PM)zaczac Wrote:  Yes it is a software bug, but to be clear custom resolutions have never worked on IVY or haswell for laptops (possibly desktops too) that is what they are fixing, the ability to add custom resolutions and refresh rates etc via the control panel. Would that not mean that they are adding in edid overrides via their own software?
No, custom resolutions are not EDID overrides. CRU uses EDID overrides because that was the best way to support both AMD and NVIDIA, and EDID overrides can do other things like remove unneeded resolutions. Drivers have their own way of adding custom resolutions. CRU may support driver-specific methods in the future, but Intel doesn't have that information publicly available either. There's also the issue of pixel clock limits, which would require modifying the driver.
Find all posts by this user
Quote this message in a reply
09-19-2015, 02:33 PM
Post: #1665
RE: Custom Resolution Utility (CRU)
(09-17-2015 06:48 PM)falkentyne Wrote:  is there a technical reason why video cards don't downclock the memory (or sometimes the core) from load speeds, when the Vertical Total is lower than the default? Is this a hardware limitation or by design?
The memory needs to be retrained after changing clock speeds. This is done between screen refreshes during the vertical blanking period to avoid screen flicker. If the vertical blanking period is not long enough, there won't be enough time to refresh the memory contents before the next screen refresh.

AMD cards are also hard-coded to switch clock profiles when video acceleration is active even if the memory clock is not supposed to change. That's why the screen gets corrupted with a lower vertical total when video acceleration is active with the memory overclocked.
Find all posts by this user
Quote this message in a reply
09-19-2015, 02:43 PM
Post: #1666
RE: Custom Resolution Utility (CRU)
(09-19-2015 01:49 PM)ToastyX Wrote:  You didn't mention what video card you have or how you have the monitor connected. If you have an NVIDIA card, you need to use a custom extension block as described in the main post. If you're using HDMI, you need to add HDMI support to the extension block.

I have a GTX 970 and at the moment I'm connected via a Display Port. The 'include extension block' is already ticked by default.
Find all posts by this user
Quote this message in a reply
09-19-2015, 03:39 PM
Post: #1667
RE: Custom Resolution Utility (CRU)
(09-19-2015 02:43 PM)DustyShinigami Wrote:  I have a GTX 970 and at the moment I'm connected via a Display Port. The 'include extension block' is already ticked by default.
That's an old version of CRU. You should use the latest version. NVIDIA doesn't support using the default extension block in EDID overrides. Setting "Custom extension block" replaces having to import blank-extension.dat in the older versions. You'll also have to add 144/120/100/85 Hz manually when using a custom extension block. You might be better off just using the NVIDIA control panel to add custom resolutions because it will be easier in this case.

One of my goals for CRU 1.3 is to use driver-specific methods to read the default extension block so this won't be necessary anymore.
Find all posts by this user
Quote this message in a reply
09-19-2015, 07:09 PM
Post: #1668
RE: Custom Resolution Utility (CRU)
(09-18-2015 05:27 PM)herkow Wrote:  Hi evereyone. First of all, ToastyX: thank you very very much for this software. I almost grab an axe to "fix" my monitor before using this app.

ATI Radeon HD 3650

The original issue was that at 1920x1080 59 Hz the text (and mouse pointer) was blurry in some places, not all the screen. I've solved this before by changing the refresh frequency on other systems and monitors. But here, no way...
So, CRU brougth me back to life, and I couldn't believe my luck when I saw every letter perfectly defined. But happines won't last forever. After reboot, the image got blurry again.
Anyway, I've been trying several frequencies, over 59Hz (the monitor recognizes 59, 60, and 61 Hz as 60Hz.) at 1920x1080 res., and it works perfectly, but when I reboot, or power off, the image becomes blurry again. If I run restart64.exe, everything looks perfect again.
If you have to run restart64.exe after rebooting, that usually indicates a driver bug. The only way around that would be to flash the monitor's EDID. That would fix it once and for all.

I'm more concerned about why 59 Hz is blurry. You didn't show me what you did to fix it. 1920x1080 @ 60 Hz should already be defined as exactly 60 Hz with a pixel clock of 148.50 MHz, so I don't know what you changed. Normally the driver adds 59 Hz as an alias for 59.94 or 60 Hz, so that shouldn't make a difference. Are you using DVI? HDMI? VGA?

Make sure 1920x1080 @ 60 Hz is only defined once. It should be a detailed resolution and not a standard resolution. If the monitor has a default extension block, change it to a custom extension block to make sure it's not defined in there as well.
Find all posts by this user
Quote this message in a reply
09-19-2015, 08:30 PM (Last edited: 09-20-2015, 02:45 AM by herkow)
Post: #1669
RE: Custom Resolution Utility (CRU)
(09-19-2015 07:09 PM)ToastyX Wrote:  
(09-18-2015 05:27 PM)herkow Wrote:  Hi evereyone. First of all, ToastyX: thank you very very much for this software. I almost grab an axe to "fix" my monitor before using this app.

ATI Radeon HD 3650

The original issue was that at 1920x1080 59 Hz the text (and mouse pointer) was blurry in some places, not all the screen. I've solved this before by changing the refresh frequency on other systems and monitors. But here, no way...
So, CRU brougth me back to life, and I couldn't believe my luck when I saw every letter perfectly defined. But happines won't last forever. After reboot, the image got blurry again.
Anyway, I've been trying several frequencies, over 59Hz (the monitor recognizes 59, 60, and 61 Hz as 60Hz.) at 1920x1080 res., and it works perfectly, but when I reboot, or power off, the image becomes blurry again. If I run restart64.exe, everything looks perfect again.
If you have to run restart64.exe after rebooting, that usually indicates a driver bug. The only way around that would be to flash the monitor's EDID. That would fix it once and for all.

I'm more concerned about why 59 Hz is blurry. You didn't show me what you did to fix it. 1920x1080 @ 60 Hz should already be defined as exactly 60 Hz with a pixel clock of 148.50 MHz, so I don't know what you changed. Normally the driver adds 59 Hz as an alias for 59.94 or 60 Hz, so that shouldn't make a difference. Are you using DVI? HDMI? VGA?

Make sure 1920x1080 @ 60 Hz is only defined once. It should be a detailed resolution and not a standard resolution. If the monitor has a default extension block, change it to a custom extension block to make sure it's not defined in there as well.

When I use 60Hz, in fact, no matter what refresh I set, windows switchs it back to 59Hz.

I tried to fix it by setting a deatiled resolution of 75Hz and 60Hz with the same result.

I'm using DVI out to HDMI in.

Here's more data, from Monitor Asset Manager:

Code:
Monitor
  Model name............... TV-monitor
  Manufacturer............. SKY
  Plug and Play ID......... SKY0001
  Serial number............ n/a
  Manufacture date......... 2014, ISO week 24
  Filter driver............ None
  -------------------------
  EDID revision............ 1.3
  Input signal type........ Digital
  Color bit depth.......... Undefined
  Display type............. RGB color
  Screen size.............. 890 x 500 mm (40,2 in)
  Power management......... Not supported
  Extension blocs.......... 1 (CEA-EXT)
  -------------------------
  DDC/CI................... Not supported

Color characteristics
  Default color space...... Non-sRGB
  Display gamma............ 2,20
  Red chromaticity......... Rx 0,625 - Ry 0,340
  Green chromaticity....... Gx 0,280 - Gy 0,595
  Blue chromaticity........ Bx 0,155 - By 0,070
  White point (default).... Wx 0,283 - Wy 0,298
  Additional descriptors... None

Timing characteristics
  Horizontal scan range.... 15-80kHz
  Vertical scan range...... 49-76Hz
  Video bandwidth.......... 140MHz
  CVT standard............. Not supported
  GTF standard............. Not supported
  Additional descriptors... None
  Preferred timing......... Yes
  Native/preferred timing.. 1920x1080p at 60Hz (16:9)
    Modeline............... "1920x1080" 148,500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync
  Detailed timing #1....... 1360x1536i at 60Hz (16:9)
    Modeline............... "1360x1536" 85,500 1360 1424 1536 1792 1536 1542 1554 1590 interlace +hsync +vsync

Standard timings supported
     720 x  400p at  70Hz - IBM VGA
     640 x  480p at  60Hz - IBM VGA
     640 x  480p at  67Hz - Apple Mac II
     640 x  480p at  72Hz - VESA
     640 x  480p at  75Hz - VESA
     800 x  600p at  56Hz - VESA
     800 x  600p at  60Hz - VESA
     800 x  600p at  72Hz - VESA
     800 x  600p at  75Hz - VESA
     832 x  624p at  75Hz - Apple Mac II
    1024 x  768p at  60Hz - VESA
    1024 x  768p at  70Hz - VESA
    1024 x  768p at  75Hz - VESA
    1280 x 1024p at  75Hz - VESA
     640 x  480p at  60Hz - VESA STD
     800 x  600p at  60Hz - VESA STD
    1024 x  768p at  60Hz - VESA STD
    1280 x  800p at  60Hz - VESA STD
    1360 x  765p at  60Hz - VESA STD
    1280 x 1024p at  60Hz - VESA STD
    1920 x 1080p at  60Hz - VESA STD

EIA/CEA-861 Information
  Revision number.......... 3
  IT underscan............. Not supported
  Basic audio.............. Supported
  YCbCr 4:4:4.............. Supported
  YCbCr 4:2:2.............. Supported
  Native formats........... 4
  Detailed timing #1....... 1280x720p at 50Hz (16:9)
    Modeline............... "1280x720" 74,250 1280 1720 1760 1980 720 725 730 750 +hsync +vsync
  Detailed timing #2....... 1920x1080i at 50Hz (16:9)
    Modeline............... "1920x1080" 74,250 1920 2448 2492 2640 1080 1084 1094 1124 interlace +hsync +vsync
  Detailed timing #3....... 720x480p at 60Hz (16:9)
    Modeline............... "720x480" 27,000 720 736 798 858 480 489 495 525 -hsync -vsync
  Detailed timing #4....... 720x576p at 50Hz (16:9)
    Modeline............... "720x576" 27,000 720 732 796 864 576 581 586 625 -hsync -vsync

CE video identifiers (VICs) - timing/formats supported
     720 x  480p at  60Hz - EDTV (4:3, 8:9)
    1280 x  720p at  60Hz - HDTV (16:9, 1:1)
     720 x  576p at  50Hz - EDTV (4:3, 16:15)
    1280 x  720p at  50Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  24Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  30Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  60Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  25Hz - HDTV (16:9, 1:1)
    1920 x 1080p at  50Hz - HDTV (16:9, 1:1)
     720 x  480i at  60Hz - Doublescan (4:3, 8:9)
     720 x  576i at  50Hz - Doublescan (4:3, 16:15)
     720 x  480p at  60Hz - EDTV (16:9, 32:27)
     720 x  480i at  60Hz - Doublescan (16:9, 32:27)
     720 x  576p at  50Hz - EDTV (16:9, 64:45)
     720 x  576i at  50Hz - Doublescan (16:9, 64:45)
    1920 x 1080i at  60Hz - HDTV (16:9, 1:1)
    1920 x 1080i at  50Hz - HDTV (16:9, 1:1)
    NB: NTSC refresh rate = (Hz*1000)/1001

CE audio data (formats supported)
  LPCM    2-channel, 16/20/24 bit depths at 32/44/48/88/96/176/192 kHz
  AC-3    2-channel,  640k max. bit rate at 32/44/48/88/96/176/192 kHz

CE speaker allocation data
  Channel configuration.... 2.0
  Front left/right......... Yes
  Front LFE................ No
  Front center............. No
  Rear left/right.......... No
  Rear center.............. No
  Front left/right center.. No
  Rear left/right center... No
  Rear LFE................. No

CE vendor specific data (VSDB)
  IEEE registration number. 0x000C03
  CEC physical address..... 1.0.0.0
  Supports AI (ACP, ISRC).. Yes
  Supports 48bpp........... No
  Supports 36bpp........... Yes
  Supports 30bpp........... Yes
  Supports YCbCr 4:4:4..... Yes
  Supports dual-link DVI... No
  Maximum TMDS clock....... 225MHz
  Video latency (p)........ 23ms
  Audio latency (p)........ 23ms
  Video latency (i)........ 23ms
  Audio latency (i)........ 23ms
  HDMI video capabilities.. No
  Data payload............. 030C001000B82DC00C0C0C0C00

Report information
  Date generated........... 19/9/2015
  Software revision........ 2.90.0.1000
  Data source.............. Real-time 0x0011
  Operating system......... 6.2.9200.2

Raw data
  00,FF,FF,FF,FF,FF,FF,00,4D,79,01,00,01,01,01,01,18,18,01,03,80,59,32,78,0A,​0D,C9,A0,57,47,98,27,
  12,48,4C,BF,EF,00,31,40,45,40,61,40,81,00,8B,C0,81,80,D1,C0,01,01,02,3A,80,​18,71,38,2D,40,58,2C,
  45,00,75,F2,31,00,00,1E,66,21,50,B0,51,00,1B,30,40,70,36,00,75,F2,31,00,00,​9E,00,00,00,FC,00,54,
  56,2D,6D,6F,6E,69,74,6F,72,0A,20,20,00,00,00,FD,00,31,4C,0F,50,0E,00,0A,20,​20,20,20,20,20,01,DD,
  02,03,2F,74,51,02,04,11,13,20,22,10,21,1F,06,15,03,07,12,16,05,14,26,09,7F,​07,11,7F,50,83,01,00,
  00,6D,03,0C,00,10,00,B8,2D,C0,0C,0C,0C,0C,00,01,1D,00,BC,52,D0,1E,20,B8,28,​55,40,75,F2,31,00,00,
  1E,01,1D,80,D0,72,1C,16,20,10,2C,25,80,75,F2,31,00,00,9F,8C,0A,D0,8A,20,E0,​2D,10,10,3E,96,00,75,
  F2,31,00,00,19,8C,0A,D0,90,20,40,31,20,0C,40,55,00,75,F2,31,00,00,18,00,00,​00,00,00,00,00,00,02


UPDATE:

I've removed all 1920x1080 res., no extension block, set detailed res to 1024x768 @75 HZ... Reset64.exe and resolution is 1920x1080 @59Hz.

I need a priest to exorcise my GPU. Sad
Find all posts by this user
Quote this message in a reply
09-19-2015, 11:18 PM
Post: #1670
RE: Custom Resolution Utility (CRU)
(09-19-2015 03:39 PM)ToastyX Wrote:  That's an old version of CRU. You should use the latest version. NVIDIA doesn't support using the default extension block in EDID overrides. Setting "Custom extension block" replaces having to import blank-extension.dat in the older versions. You'll also have to add 144/120/100/85 Hz manually when using a custom extension block. You might be better off just using the NVIDIA control panel to add custom resolutions because it will be easier in this case.

One of my goals for CRU 1.3 is to use driver-specific methods to read the default extension block so this won't be necessary anymore.

I've tried using the NVIDIA Control Panel too, but it made no difference either. Also, I'm not concerned about adding custom resolutions, just my own refresh rates. Smile
Find all posts by this user
Quote this message in a reply
 Post Reply


Forum Jump:


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