Error with profile_loader.pyc while loading profile

[ffffffff01]

Hello,

I ran displaycal 3.6.0 properly for 1 month, but today after I connect a same type monitor and then change it back. I can no longer load the color profile. I tried calibrate again, uninstall and reinstall displaycal multiple times, but still doesn’t work. The error in the DisplayCAL-apply-profiles.log says as below.  Could anyone help? Thanks!

2018-07-23 18:48:53,743 Buggy video driver detected: Intel(R) UHD Graphics 620. Gamma ramp hack activated.
2018-07-23 18:48:53,872 Intel(R) UHD Graphics 620
2018-07-23 18:48:53,872 |- Wide viewing angle & High density FlexView Display 2560×1440 (deactivated)
2018-07-23 18:48:53,872 |- 1. LG UltraFine @ 0, 0, 5120×2880 [PRIMARY]
2018-07-23 18:48:54,015 Fixing profile association for 1. LG UltraFine @ 0, 0, 5120×2880 [PRIMARY]: B140QAN02.0 #1 2018-07-23 16-45 D6500 2.2 F-S XYZLUT+MTX.icm -> UltraFine #1 2018-06-28 00-35 D6500 2.2 F-S XYZLUT+MTX.icm
2018-07-23 18:48:54,062 Traceback (most recent call last):
2018-07-23 18:48:54,062 File “DisplayCAL\profile_loader.pyc”, line 1969, in _check_display_conf_wrapper
2018-07-23 18:48:54,062 File “DisplayCAL\profile_loader.pyc”, line 2000, in _check_display_conf
2018-07-23 18:48:54,062 File “DisplayCAL\profile_loader.pyc”, line 1928, in _check_display_changed
2018-07-23 18:48:54,062 TypeError: OpenKey() argument 2 must be string without null bytes or None, not str
2018-07-23 18:48:55,796 Executing ProfileLoader.exit(None)
2018-07-23 18:48:55,848 Executing BaseApp.OnExit()
2018-07-23 18:48:55,849 Running application exit handlers
2018-07-23 18:48:55,849 Shutting down profile loader
2018-07-23 18:48:55,852 Resetting profile association for Wide viewing angle & High density FlexView Display 2560×1440: UltraFine #1 2018-06-28 00-35 D6500 2.2 F-S XYZLUT+MTX.icm -> B140QAN02.0 #1 2018-07-23 16-45 D6500 2.2 F-S XYZLUT+MTX.icm
2018-07-23 18:48:55,957 Waiting for thread ScriptingHost.ConnectionHandler to exit
2018-07-23 18:48:55,983 ScriptingHost.ConnectionHandler exited
2018-07-23 18:48:55,987 Exiting DisplayCAL-apply-profiles
2018-07-23 18:48:55,987 Ran application exit handlers

[Florian Höch]

Hi,

looks like your registry may be corrupt. Please export the registry tree at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration (using regedit) and attach the reg file (create a ZIP archive).

[ffffffff01]

Thanks a lot. I’ve enclosed the file here.

Attachments:

You must be logged in to view attached files.

[Florian Höch]

Please use RegDelNull to check for malformed registry keys. Run it from a Windows command prompt like this:

RegDelNull HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration -s

If it finds malformed keys, don’t delete them yet, just post the output.

[ffffffff01]

Thanks. First, please check my enclosed screen.PNG file, i found four highlighted registry entries which are unable to open or delete

Second, I tried the command line and here is the output:

RegDelNull HKLM\SYSTEM\CurrentControlSet\Control\GraphicsDrivers\Configuration -s

RegDelNull v1.11 – Delete Registry keys with embedded Nulls
Copyright (C) 2005-2016 Mark Russinovich
Sysinternals – http://www.sysinternals.com

Null-embedded key (Nulls are replaced by ‘*’):

HKLM\SYSTEM\CURRENTCONTROLSET\CONTROL\GRAPHICSDRIVERS\CONFIGURATION\GSM5B11???????00_08C5_7E*******^276FEB318FCC3F8845425E8FBA093A10

Delete? (y/n)

Attachments:

You must be logged in to view attached files.

[Florian Höch]

Hmm. Bunch of Unicode characters and NUL bytes in the display configuration key names, I don’t think that should happen. Possibly a graphics driver bug? To see if this is actually a valid entry, replace C:\Program Files(x86)\DisplayCAL\lib\library.zip with the attached file, then try to run the profile loader again and attach DisplayCAL-apply-profiles.log/log.1 afterwards.

Attachments:

You must be logged in to view attached files.

[ffffffff01]

Here it is. I’ve renamed the original log file and created a new log file with the attached library.zip file you provided. Thanks.

Attachments:

You must be logged in to view attached files.

[ffffffff01]

upload another log file which is in the same folder.

Attachments:

You must be logged in to view attached files.

[Florian Höch]

Ok, please try again after replacing library.zip with the attached file (you need to rename it from library-1.zip to library.zip).

• This reply was modified 5 years, 9 months ago by Florian Höch.

Attachments:

You must be logged in to view attached files.

[ffffffff01]

Thanks for the great help. Just now, I managed to replace the corrupt configuration entry with a good clean registry hive from another PC and then import the original .reg file. Now the corrupt entries are gone and i can log the color profile fine now. 🙂

[Author]

Posts