Monitor Tests Forum

(10-31-2020 08:58 PM)ToastyX Wrote: [ -> ]

(10-31-2020 05:39 PM)andres.espinal Wrote: [ -> ]I have a Samsung c27fg70 which I can´t set at 144 Hz because of a defective firmware https://www.youtube.com/watch?v=Ad4emOwpFEI.

Could this software help me? I'm trying it, no luck so far, can I do something?

Does that still happen with FreeSync disabled?

Yes it happens with freesync disabled.

(10-31-2020 10:15 PM)botounacruzeta Wrote: [ -> ]I noticed something in CRU I don't understand: it shows the monitor two times. (see attached picture, that corresponds to clean default settings). I don't know if it's due to GSYNC module, or if it's normal for every monitor. (There's only one monitor plugged to my PC).

That's not a problem. That's added by Microsoft's Basic Display Adapter driver when NVIDIA's driver is restarted. It has no effect on the active monitor.

Try installing this:
[attachment=600]

That's the CRU-exported settings with one minor change. Don't import with CRU because it will revert the change.

(10-31-2020 11:06 PM)andres.espinal Wrote: [ -> ]Yes it happens with freesync disabled.

Honestly, I would bug Samsung to replace it until they fix the problem because it should just work. If you want to play around with CRU, try editing the 144 Hz detailed resolution and try the different timing options.

(10-31-2020 11:49 PM)ToastyX Wrote: [ -> ]

(10-31-2020 11:06 PM)andres.espinal Wrote: [ -> ]Yes it happens with freesync disabled.

Honestly, I would bug Samsung to replace it until they fix the problem because it should just work. If you want to play around with CRU, try editing the 144 Hz detailed resolution and try the different timing options.

true, where how can I know the correct timings?

(10-31-2020 11:58 PM)andres.espinal Wrote: [ -> ]true, where how can I know the correct timings?

You have to try them and see what happens.

(10-31-2020 11:34 PM)ToastyX Wrote: [ -> ]

(10-31-2020 10:15 PM)botounacruzeta Wrote: [ -> ]I noticed something in CRU I don't understand: it shows the monitor two times. (see attached picture, that corresponds to clean default settings). I don't know if it's due to GSYNC module, or if it's normal for every monitor. (There's only one monitor plugged to my PC).

That's not a problem. That's added by Microsoft's Basic Display Adapter driver when NVIDIA's driver is restarted. It has no effect on the active monitor.

Try installing this:


That's the CRU-exported settings with one minor change. Don't import with CRU because it will revert the change.

I've run reset-all, restarted the GPU, and installed test.inf.

Then NVCPL did not work.

After I restarted GPU, NVCPL still didn't work.

In the attached image, I show how CRU and Dev manager displayed things after test.inf is properly loaded.

[attachment=601]

Note: I installed INF file using Windows only, and updated Monitor driver using Device Manager. I only opened CRU to show you how it displays things after inf is loaded.

(11-01-2020 12:23 AM)botounacruzeta Wrote: [ -> ]Note: I installed INF file using Windows only, and updated Monitor driver using Device Manager. I only opened CRU to show you how it displays things after inf is loaded.

This is frustrating because I can't pinpoint any particular change that is triggering the problem.

Are you sure about this:

(10-31-2020 08:13 PM)botounacruzeta Wrote: [ -> ]I could also open NVCPL after doing these simple steps:

-run reset-all.exe;
-restart GPU;
-In CRU, enable both "Include if slot available" options under "Range limits" and under "Serial number";
-import the CRU-exported settings (default ones) using CRU;
-restart GPU;

Importing the file should disable both the range limits and serial number since they aren't included in the file, so it should be exactly the same as just importing the file. You also said choosing "Import complete EDID" worked alone, but that shouldn't make any difference because there weren't any changes made to the non-imported parts. You also said enabling the range limits and serial number worked after installing the MonInfo .inf file and importing the CRU-exported settings, but then CRU would just make the same changes that it would without installing the .inf file.

What happens if you use Device Manager and right-click and choose "Scan for hardware changes" after restarting the driver?

The only other thing I can think of is try using DDU: https://www.wagnardsoft.com/display-driv...aller-ddu-

Then reinstall the driver, and try the non-DCH drivers.

(11-01-2020 02:01 AM)ToastyX Wrote: [ -> ]

(11-01-2020 12:23 AM)botounacruzeta Wrote: [ -> ]Note: I installed INF file using Windows only, and updated Monitor driver using Device Manager. I only opened CRU to show you how it displays things after inf is loaded.

This is frustrating because I can't pinpoint any particular change that is triggering the problem.

Are you sure about this:

(10-31-2020 08:13 PM)botounacruzeta Wrote: [ -> ]I could also open NVCPL after doing these simple steps:

-run reset-all.exe;
-restart GPU;
-In CRU, enable both "Include if slot available" options under "Range limits" and under "Serial number";
-import the CRU-exported settings (default ones) using CRU;
-restart GPU;

Importing the file should disable both the range limits and serial number since they aren't included in the file, so it should be exactly the same as just importing the file. You also said choosing "Import complete EDID" worked alone, but that shouldn't make any difference because there weren't any changes made to the non-imported parts.

Yes, doing these steps allow NVCPL to work.

(11-01-2020 02:01 AM)ToastyX Wrote: [ -> ]You also said enabling the range limits and serial number worked after installing the MonInfo .inf file and importing the CRU-exported settings, but then CRU would just make the same changes that it would without installing the .inf file.

Well, the above steps I did without installing the MonInfo .inf file, and it worked.

If I reset-all.exe, restart GPU, and import the CRU-exported settings, it works; (CRU doesn't show "(active) *", probably indicating nothing was changed)
If I reset-all.exe, restart GPU, delete a detailed resolution (using CRU), restart GPU, and import the CRU-exported settings ("Import complete EDID" either enabled or not), it doesn't work; (CRU shows "(active) *", probably indicating nothing was changed)

Where does CRU saves the settings? To registry?

I thought it could be a good idea to use CRU to import CRU-exported settings (default), save the registry entry, and then change something using CRU, re-import CRU-exported settings (default), and compare registry in both cases. Shouldn't they be the same, as in both cases, CRU imported the same file?

If you can tell me the registry values it updates, I'd gladly test it.

(11-01-2020 02:01 AM)ToastyX Wrote: [ -> ]What happens if you use Device Manager and right-click and choose "Scan for hardware changes" after restarting the driver?

Device Manager only refreshes its view, and the monitor retains its name.

(11-01-2020 02:01 AM)ToastyX Wrote: [ -> ]The only other thing I can think of is try using DDU: https://www.wagnardsoft.com/display-driv...aller-ddu-

Then reinstall the driver, and try the non-DCH drivers.

I'll try to do some more debugging before trying this, as it was a terrible experience installing the standard (non-DCH) drivers the last time I tried.

(11-01-2020 04:22 AM)botounacruzeta Wrote: [ -> ]If I reset-all.exe, restart GPU, and import the CRU-exported settings, it works; (CRU doesn't show "(active) *", probably indicating nothing was changed)

You said the opposite before:

(10-30-2020 05:18 AM)botounacruzeta Wrote: [ -> ]I've attached the default settings I'd exported from CRU right after using "reset-all.exe". (.inf format)

As a side note, I noticed when I import these settings (that should be the default ones) and restart the GPU, CRU shows a "*" to the right of the monitor name, meaning (at least I think so) the current settings are not the default ones.....but they are.

(11-01-2020 04:22 AM)botounacruzeta Wrote: [ -> ]I thought it could be a good idea to use CRU to import CRU-exported settings (default), save the registry entry, and then change something using CRU, re-import CRU-exported settings (default), and compare registry in both cases. Shouldn't they be the same, as in both cases, CRU imported the same file?

If you can tell me the registry values it updates, I'd gladly test it.

Yes, they should be the same. Search the registry for EDID_OVERRIDE. That's all it adds.

(11-01-2020 01:36 PM)ToastyX Wrote: [ -> ]

(11-01-2020 04:22 AM)botounacruzeta Wrote: [ -> ]If I reset-all.exe, restart GPU, and import the CRU-exported settings, it works; (CRU doesn't show "(active) *", probably indicating nothing was changed)

You said the opposite before:

(10-30-2020 05:18 AM)botounacruzeta Wrote: [ -> ]I've attached the default settings I'd exported from CRU right after using "reset-all.exe". (.inf format)

As a side note, I noticed when I import these settings (that should be the default ones) and restart the GPU, CRU shows a "*" to the right of the monitor name, meaning (at least I think so) the current settings are not the default ones.....but they are.

Yes, the problem is the first time I did it, I've enabled "Include if slot available" under "Range limits" and under "Serial number". I thought it was standard CRU procedure, that's why I didn't mentioned it before, sorry.
I'd read this tutorial
[attachment=602]
before using CRU, so I thought it was always needed.

(11-01-2020 01:36 PM)ToastyX Wrote: [ -> ]

(11-01-2020 04:22 AM)botounacruzeta Wrote: [ -> ]I thought it could be a good idea to use CRU to import CRU-exported settings (default), save the registry entry, and then change something using CRU, re-import CRU-exported settings (default), and compare registry in both cases. Shouldn't they be the same, as in both cases, CRU imported the same file?

If you can tell me the registry values it updates, I'd gladly test it.

Yes, they should be the same. Search the registry for EDID_OVERRIDE. That's all it adds.

Well, after some debugging that ONLY THE TRUE ANIMALS OF DEBUGGING would do, I've fixed the problem.

First, some details:

The original EDID seems to be located at

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\ACI27EC\1&8713bca&0&UID0\Device Parameters]

in the EDID key.

I then exported this key, for further comparison.

Then, I used CRU, removed a detailed resolution, restarted GPU, imported the CRU-exported settings (default ones), and restarted GPU. (without neither doing any change in "Include if slot available" options, nor choosing "Import complete EDID").

I then went to the CRU-created registry values at

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ACI27EC\5&149c2d9f&23&UID4357\Device Parameters\EDID_OVERRIDE]

and there were these 6 keys:

"0"
"CRU_Name"
"CRU_Serial_Number"
"CRU_Range_Limits"
"CRU_Extensions"
"1"

I then compared "0" key overriden by CRU to the original "EDID" at

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\ACI27EC\1&8713bca&0&UID0\Device Parameters]

The reason I've thought about comparing them is the start bytes were the same.

But then, after some point, the bytes were different.

So the "fix" I did consisted in replacing the value of "0" key at

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ACI27EC\5&149c2d9f&23&UID4357\Device Parameters\EDID_OVERRIDE]

with the value of the original EDID key found at

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\DISPLAY\ACI27EC\1&8713bca&0&UID0\Device Parameters]

After restarting GPU, NVCPL works, and the resolution I needed to delete is not there. Everything fully working.


I tried to modify the ini file, replacing the

Quote:[Monitor.AddReg]
HKR,EDID_OVERRIDE,"0"

with the contents from original EDID, but it didn't work: CRU actually imports the file, but NVCPL doesn't work. I believe converting the registry value to the ones suitable for the inf file isn't so simple, so I gave up there.


A interesting thing is, if after applying the registry fix, I used CRU to export the working settings (detailed resolution deleted, and working NVCPL) in inf format, and then:

-reset-all.exe;
-restart GPU;
-Import working settings (detailed resolution deleted, and working NVCPL) inf file using CRU;
-restart GPU;

It doesn't work, and the value of "0" key at

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ACI27EC\5&149c2d9f&23&UID4357\Device Parameters\EDID_OVERRIDE]

is different than before.

I don't know how CRU saves it's settings, but I assume the value of this key should be the same after settings have been imported.

So maybe something at

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\DISPLAY\ACI27EC\5&149c2d9f&23&UID4357\Device Parameters\EDID_OVERRIDE]

"0" key is detected as "corrupted" by NCVPL after CRU saves it, I don't know....