Custom Resolution Utility (CRU)

[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.