Threaded Mode | Linear Mode

***ToastyX*** · 04-09-2017, 05:40 PM

(04-08-2017 01:10 PM)ffox Wrote: I have Windows 10 (x64), ATI Mobility 5450 (Radeon Software Crimson Edition 16.2.1 Beta), cable (HDMI-DVI) and Dell 1908FP (Digital). Monitor’s max resolution is 1280x1024 (5:4). I use your CRU with AMD/ATI Pixel Clock Patcher and everything works excellent but there is one problem. When I had Windows 7 the problem did not exist.

I can set different resolutions in Catalyst Control Centre and switch them on. 1280x720 is right aspect ratio 16:9 on the monitor [Fig.1]. All others 960x540, 800x450… are 16:9 as well. I can choose 1280x1024 (the aspect ratio changes good 5:4, 800x600, 1024x768... 4:3) be back to 1280x720 and the aspect is true every time. The GPU keeps ON and all goes automatically. It is also fine when I use system’s Windows Display Resolutions [Fig.2].

The problem occurs using Video Card Properties. Choosing 1280x720 stretches the screen to 5:4 [Fig.3]. Crimson shows “Full Panel”. Of course I can take “Keep Aspect Ratio” but switching to 1280x1024 and back to 1280x720 stretches the display again. It is interesting that apart from 1280x720 switching all other resolutions is perfect with proper auto aspect.

It is awful with 1280x720 games. I have noticed that part of them gets driver resolutions, other part uses windows resolutions and the rest takes the stretched one. Is there any fix?!?

If the scaling mode resets when you switch to a certain resolution, then it's a driver bug. Unfortunately, your video card is too old to try newer drivers, so I don't know what you can do about this.

Is this happening with 1280x720 @ 60 Hz defined in CRU? AMD's driver forces 1280x720 to exist no matter what, so you might have different results with and without it defined in CRU. You shouldn't need the pixel clock patch with these resolutions either. Also, check if "Hide modes that this monitor cannot display" makes any difference. Sometimes that won't stick either.

dmr · 04-10-2017, 01:31 AM

(04-09-2017 05:37 PM)ToastyX Wrote: You didn't say you were having a picture problem. Based on the frequencies, I assume you're talking about a 1920x1200 @ 60 Hz monitor. If that's the case, the default pixel clock is supposed to be 154 MHz, but hardware variances can cause slight differences. Such a small difference wouldn't affect the picture.

What monitor is this? Are you using DVI or HDMI? What is the exact problem you're having with the picture and what changes do you see with the NVIDIA custom resolution?

Just more pleasent picture for eye with pixel clock 154.002 than with 154.01 or 153.99. I notice more pleasent picture on amd gpu than nvidia, and saw in powerstrip on AMD freq. 59.951 and on nvidia 59.950 so I assume that is difference. Monitor is HP LP2475W 1200p connected over DVI.

ffox · 04-10-2017, 07:26 AM

(04-09-2017 05:40 PM)ToastyX Wrote:
(04-08-2017 01:10 PM)ffox Wrote: I have Windows 10 (x64), ATI Mobility 5450 (Radeon Software Crimson Edition 16.2.1 Beta), cable (HDMI-DVI) and Dell 1908FP (Digital). Monitor’s max resolution is 1280x1024 (5:4). I use your CRU with AMD/ATI Pixel Clock Patcher and everything works excellent but there is one problem. When I had Windows 7 the problem did not exist.

I can set different resolutions in Catalyst Control Centre and switch them on. 1280x720 is right aspect ratio 16:9 on the monitor [Fig.1]. All others 960x540, 800x450… are 16:9 as well. I can choose 1280x1024 (the aspect ratio changes good 5:4, 800x600, 1024x768... 4:3) be back to 1280x720 and the aspect is true every time. The GPU keeps ON and all goes automatically. It is also fine when I use system’s Windows Display Resolutions [Fig.2].

The problem occurs using Video Card Properties. Choosing 1280x720 stretches the screen to 5:4 [Fig.3]. Crimson shows “Full Panel”. Of course I can take “Keep Aspect Ratio” but switching to 1280x1024 and back to 1280x720 stretches the display again. It is interesting that apart from 1280x720 switching all other resolutions is perfect with proper auto aspect.

It is awful with 1280x720 games. I have noticed that part of them gets driver resolutions, other part uses windows resolutions and the rest takes the stretched one. Is there any fix?!?
If the scaling mode resets when you switch to a certain resolution, then it's a driver bug. Unfortunately, your video card is too old to try newer drivers, so I don't know what you can do about this.

Is this happening with 1280x720 @ 60 Hz defined in CRU? AMD's driver forces 1280x720 to exist no matter what, so you might have different results with and without it defined in CRU. You shouldn't need the pixel clock patch with these resolutions either. Also, check if "Hide modes that this monitor cannot display" makes any difference. Sometimes that won't stick either.

Thanks for your answer. Your tips did not help but I fixed this bug myself using your program. I simply changed the default monitor’s native resolution refreshing from 60Hz to 75Hz [Fig,4]. Problem has disappeared and everything works fine. So do games.

So, my old hardware is OK but software… ...I am an amateur. My programming in Assembler, Basic and Turbo Pascal ended years ago. I do not know where the error is in the system but I am sure there is a terrible mess in the original registry. People from Microsoft and AMD should think, please, THINK!

Thank you ToastyX for your CRU very much, once again.

spiritman · 04-11-2017, 02:09 AM

Man, I needed this! Now I just have to read this whole thread... I have a 1070 tried to get the custom rez to work. No cigar. I did get my main (display port) Samsung to get up to 5k but I am loosing some from the bottom of the screen. I need to find time to make this work!! THANKS!!

BlinkUW · 04-13-2017, 06:20 AM

Geforce GTX 670
Crossover 34U100 (100hz native at 3440x1440)
Win 10 x64
Geforce 381.65 WHQL drivers
Connected via DP 1.2

Trying to overclock this monitor using CRU, but the resolutions aren't showing up after I hit ok. They store within CRU, but I don't see them within Nvidia's "Change resolution" or in Window's display settings.

The only one that seems to stick is 101hz. That one shows up, any choice higher doesn't show up. Used pixel clock patcher since I'm on a Fermi card, not sure if that was necessary but no change. Also tried reinstalling Geforce Experience without luck.

Any suggestions? Thanks!

P.S. this monitor is awesome so far. 3440x1440@101hz passes the frame skip test, as well as 2560x1080 @ 144hz

***ToastyX*** · 04-13-2017, 07:34 AM

(04-13-2017 06:20 AM)BlinkUW Wrote: Geforce GTX 670
Crossover 34U100 (100hz native at 3440x1440)
Win 10 x64
Geforce 381.65 WHQL drivers
Connected via DP 1.2

Trying to overclock this monitor using CRU, but the resolutions aren't showing up after I hit ok. They store within CRU, but I don't see them within Nvidia's "Change resolution" or in Window's display settings.

The only one that seems to stick is 101hz. That one shows up, any choice higher doesn't show up. Used pixel clock patcher since I'm on a Fermi card, not sure if that was necessary but no change. Also tried reinstalling Geforce Experience without luck.

GTX 670 is Kepler, not Fermi. Kepler is limited to 540 MHz pixel clock with DisplayPort. The patch does not get around DisplayPort limits. You might be able to squeeze in a few more Hz by reducing the totals, but not by much at that resolution. "LCD reduced" might give you 104-106 Hz if the monitor can handle lower totals.

iyyama · 04-13-2017, 11:07 AM

got a new monitor that will only run at 30hz at 4k resolution, not gaming but still too low.
was hoping to get a higher framerate using CRU but get an access violation when trying to open it. Anyone know to avoid the access violation?
I actually deleted the msvcrt.dll file as it was suggested to me but still same error...
i attached a picture of the error. thank you

iyyama · 04-13-2017, 12:35 PM

(04-13-2017 11:07 AM)iyyama Wrote: got a new monitor that will only run at 30hz at 4k resolution, not gaming but still too low.
was hoping to get a higher framerate using CRU but get an access violation when trying to open it. Anyone know to avoid the access violation?
I actually deleted the msvcrt.dll file as it was suggested to me but still same error...
i attached a picture of the error. thank you

noone knows what to do about it? mouse is too laggy for my work

tobindax · 04-13-2017, 01:38 PM

17.4.2 seems to work fine on reboots.

BlinkUW · 04-13-2017, 04:11 PM

(04-13-2017 07:34 AM)ToastyX Wrote:
(04-13-2017 06:20 AM)BlinkUW Wrote: Geforce GTX 670
Crossover 34U100 (100hz native at 3440x1440)
Win 10 x64
Geforce 381.65 WHQL drivers
Connected via DP 1.2

Trying to overclock this monitor using CRU, but the resolutions aren't showing up after I hit ok. They store within CRU, but I don't see them within Nvidia's "Change resolution" or in Window's display settings.

The only one that seems to stick is 101hz. That one shows up, any choice higher doesn't show up. Used pixel clock patcher since I'm on a Fermi card, not sure if that was necessary but no change. Also tried reinstalling Geforce Experience without luck.
GTX 670 is Kepler, not Fermi. Kepler is limited to 540 MHz pixel clock with DisplayPort. The patch does not get around DisplayPort limits. You might be able to squeeze in a few more Hz by reducing the totals, but not by much at that resolution. "LCD reduced" might give you 104-106 Hz if the monitor can handle lower totals.

Thanks for the response Toasty, awesome tool. I guess I'll wait until AMD Vega is out before overclocking.