Threaded Mode | Linear Mode

DigDeep · (Last edited: 10-07-2019, 09:00 AM by DigDeep)

PLEASE READ THIS:

Since AMD driver version 17.11.3 Freesync Enabled through CRU doesnt work, screen goes black, I suspect AMD added some reader of CRU source code and when it finds it, it criples it. So could anyone try to lower CRU signature so that AMD drivers do not find traces of CRU Utility, that way I think black screen would not appear anymore, it works fine with v17.11.0 but not with later versions of drivers.

***ToastyX*** · 10-07-2019, 12:53 PM

(10-07-2019 08:59 AM)DigDeep Wrote: Since AMD driver version 17.11.3 Freesync Enabled through CRU doesnt work, screen goes black, I suspect AMD added some reader of CRU source code and when it finds it, it criples it. So could anyone try to lower CRU signature so that AMD drivers do not find traces of CRU Utility, that way I think black screen would not appear anymore, it works fine with v17.11.0 but not with later versions of drivers.

Not true. Black screen means your monitor is not handling FreeSync correctly. You should not need to use CRU to enable FreeSync on a FreeSync monitor.

DigDeep · (Last edited: 10-07-2019, 04:03 PM by DigDeep)

(10-07-2019 12:53 PM)ToastyX Wrote:
(10-07-2019 08:59 AM)DigDeep Wrote: Since AMD driver version 17.11.3 Freesync Enabled through CRU doesnt work, screen goes black, I suspect AMD added some reader of CRU source code and when it finds it, it criples it. So could anyone try to lower CRU signature so that AMD drivers do not find traces of CRU Utility, that way I think black screen would not appear anymore, it works fine with v17.11.0 but not with later versions of drivers.
Not true. Black screen means your monitor is not handling FreeSync correctly. You should not need to use CRU to enable FreeSync on a FreeSync monitor.

It is true, because it works fine on v17.11.3. so if it works fine on v17 and not on v19 then AMD has done something to the drivers. Monitor is not freesync.

***ToastyX*** · 10-07-2019, 04:20 PM

(10-07-2019 04:02 PM)DigDeep Wrote: It is true, because it works fine on v17.11.3. so if it works fine on v17 and not on v19 then AMD has done something to the drivers. Monitor is not freesync.

Older drivers didn't have FreeSync active on the desktop. Your monitor is blacking out because it can't handle FreeSync. Most non-FreeSync monitors can't handle FreeSync.

DigDeep · (Last edited: 10-07-2019, 06:02 PM by DigDeep)

(10-07-2019 04:20 PM)ToastyX Wrote:
(10-07-2019 04:02 PM)DigDeep Wrote: It is true, because it works fine on v17.11.3. so if it works fine on v17 and not on v19 then AMD has done something to the drivers. Monitor is not freesync.
Older drivers didn't have FreeSync active on the desktop. Your monitor is blacking out because it can't handle FreeSync. Most non-FreeSync monitors can't handle FreeSync.

Version 17 has Freesync. Like I said AMD disabled CRU probably in later drivers, so we cannot use freesync for free. Why is this so hard to believe?

***ToastyX*** · 10-07-2019, 10:28 PM

(10-07-2019 06:00 PM)DigDeep Wrote: Version 17 has Freesync. Like I said AMD disabled CRU probably in later drivers, so we cannot use freesync for free. Why is this so hard to believe?

Because that's not how it works. Your monitor can't handle FreeSync. Why is that so hard to understand? Every symptom you've described is the monitor not being able to handle FreeSync. Older drivers didn't have FreeSync active on the *desktop*, which is separate from games. Try the G-SYNC pendulum demo to see if it's actually working: https://www.nvidia.com/coolstuff/demos#!/g-sync

The FreeSync data block in CRU is meant for editing the HDMI FreeSync range, not for adding FreeSync to non-FreeSync monitors. A few non-FreeSync monitors can handle FreeSync, but the vast majority do not.

zaltys · 10-07-2019, 11:29 PM

Is anyone else having problems with custom resolutions on the latest Intel drivers for 6th Gen and later?

Whenever I set a custom resolution using CRU or Intel Graphics Control Panel / Command Center after the monitor has gone to sleep, and just at the point it is about to wake up I get a dxgkrnl crash recorded and the monitor stays blank.

I believe CRU and Intel tools use different registry settings, so it's odd there's a problem with both sets of tools.

It's quite repeatable and as soon as the custom resolution is removed the problem goes away.

Any workarounds?

DigDeep · 10-08-2019, 06:46 AM

(10-07-2019 10:28 PM)ToastyX Wrote:
(10-07-2019 06:00 PM)DigDeep Wrote: Version 17 has Freesync. Like I said AMD disabled CRU probably in later drivers, so we cannot use freesync for free. Why is this so hard to believe?
Because that's not how it works. Your monitor can't handle FreeSync. Why is that so hard to understand? Every symptom you've described is the monitor not being able to handle FreeSync. Older drivers didn't have FreeSync active on the *desktop*, which is separate from games. Try the G-SYNC pendulum demo to see if it's actually working: https://www.nvidia.com/coolstuff/demos#!/g-sync

The FreeSync data block in CRU is meant for editing the HDMI FreeSync range, not for adding FreeSync to non-FreeSync monitors. A few non-FreeSync monitors can handle FreeSync, but the vast majority do not.

Oh now I get it, sorry. So even v17 doesnt work in games, I tried it only on desktop. Ok, thanks for explanation.

b0uncyfr0 · 10-09-2019, 09:43 AM

Hey all, first-time poster ( i think). Thanks, toasty for a great tool!

I'm trying to overclock my 4K TV to higher frame rates. ATM i have 1080p working at 74hz from the usual 60hz. The problem is I had to increase the TMDS from 360 to 400 to get this. Is this a good idea, to manually increase it? What does the limit depend on?

I run the patcher and it did find and patch values. For referecene i have:

A 1070 - which is HDMI 2.0b compliant using a HDMI 2.0b cable.

***ToastyX*** · 10-09-2019, 03:01 PM

(10-09-2019 09:43 AM)b0uncyfr0 Wrote: I'm trying to overclock my 4K TV to higher frame rates. ATM i have 1080p working at 74hz from the usual 60hz. The problem is I had to increase the TMDS from 360 to 400 to get this. Is this a good idea, to manually increase it? What does the limit depend on?

I run the patcher and it did find and patch values. For referecene i have:

A 1070 - which is HDMI 2.0b compliant using a HDMI 2.0b cable.

I haven't seen NVIDIA's driver use the TMDS limit, and you shouldn't have to change it anyway because 1080p @ 74 Hz is nowhere near 400 MHz pixel clock. You shouldn't need the patcher with HDMI either.