#18726 (Bug) Whole screen turns blue/green/violet etc.

+1 1

Closed as Not A Bug
Created by hinterlufer

Last modified


After some time after login, my whole screen turns blue, green or violet (like putting a colored filter over the monitor). Restarting fixes the issue until it appears again.

The issue is reproducable by clicking on the “install” button for the color profile in DisplayCAL. The selected monitor will then express the bug. It also appears after some time (10 min to hours).

I am running a very fresh install of Win10 Build 1903, DisplayCal Version 3.8.3

Edit: attached a picture of what my screen does look like


logs (application/x-7z-compressed | 2019-07-16 19:34:26)
IMG_20190717_183232 (image/jpeg | 2019-07-17 18:38:20)


11 thoughts on “Whole screen turns blue/green/violet etc.”

  1. If you have calibrated to a custom whitepoint, this whitepoint will be enforced by the calibration if it’s done via the calibration and not monitor controls. This is not an error, but how it’s supposed to work.

  2. I wish they had posted a reason why this was closed as “not a bug.” This issue began with that last Windows update (May 2019). DisplayCal 3.8.3 was supposed to offer a workaround, but then MS released a patch to fix the underlying issue—a bug in their update’s handling of color profiles. Since 3.8.3 and the patched May update have both been introduced, the issue has come back. However, the issue ONLY occurs when DisplayCal is installed.

    I, too, am on a fresh install of Win10, May update, patch, and DisplayCal 3.8.3. Uninstall DC3 removes the issue. Quitting DC3 also will sometimes correct the issue a moment later. Launching DC3 *immediately* triggers the issue.

    If this is a bug with MS’s most recent patch still, it’d be helpful to know that. It’s definitely an incompatibility between DC3 and that patch. It is *not* a custom whitepoint issue.

  3. Also, to Hinterlufer: Installing the profile via DC3 as a system default, rather than a user default, has definitely reduced the number of occurrences for me. It still happens on startup, but turning off the monitor and back on again is consistently the easiest and fastest way to correct the problem here (not rebooting). Having the profile as the system default has removed the recurrences that happen during my work day, so I’m only dealing with this issue at start up now.

  4. DisplayCal 3.8.3 was supposed to offer a workaround

    There is no supposed workaround (never was).

    but then MS released a patch to fix the underlying issue

    No, the only thing that MS patched was calibration loading not working at all (see sticky thread in help & support forum).

    Quitting DC3 also will sometimes correct the issue a moment later

    There is no need for DisplayCAL to run in the background, and you shouldn’t keep it running. Only run it if you want to calibrate & profile.

    It’s definitely an incompatibility between DC3 and that patch.

    If that were the case, the issue would be readily reproducible by others, and the details would be clear. Both isn’t the case at all.

    Installing the profile via DC3 as a system default, rather than a user default, has definitely reduced the number of occurrences for me.

    That could indicate you have some broken profiles installed and assigned, or some other software interfering (another software perhaps cannot as easily interfere if a profile is assigned  as system default, because it requires admin privileges to do that).

  5. I feel like this issue is currently discussed in the following thread although it’s not entirely clear if the other users are having the same or a similar issue (some write of solid colors)

    Problem Since 1903 Update

    What does stick out, however, is that all users reporting this problem are using Radeon graphics and W10 1903.

    @Kevin: are you using Radeon graphics as well?

    It still happens on startup, but turning off the monitor and back on again is consistently the easiest and fastest way to correct the problem here (not rebooting)

    I tried that at one occurrence and it fixed it for like 10s until it happened again.

    If that were the case, the issue would be readily reproducible by others, and the details would be clear. Both isn’t the case at all.

    as stated above, in the thread above several people are having those or similar problems.

    Installing the profile via DC3 as a system default, rather than a user default, has definitely reduced the number of occurrences for me.

    That could indicate you have some broken profiles installed and assigned, or some other software interfering (another software perhaps cannot as easily interfere if a profile is assigned  as system default, because it requires admin privileges to do that).

    I did install the profiles as system default from the beginning and still experience the issue.

     

    One important detail is, that the problem only seems to occur when the profile loader is running. When I disable the profile loader (through startups) and then start DC and click the install profile, everything works as intended. Also, when I created a new profile yesterday and installed it, there were no problems even after several hours. Now, after a restart with the profile loader installed the problem is reproducable by either waiting X amount of time or running DC and click the install profile button.

    As I see it, it has to do something with the 1903 Update, Radeon drivers and the profile loader.

  6. Florian: 1 – Didn’t read patch notes closely. 2 – I’m referring to the loader., which is always running. 3 – The issue is reproducible by a number of people I know (also all on Radeon), who simply don’t bother to log in and engage in these types of forums.

    Hinter: Yes, Radeon Rx570. The problem goes away when I toss in my Nvidia or when I use different calibration software.

  7. Would also like to add that they are not broken profiles. Clean install included new calibration. In my situation, I have also bought new displayport cables AND an entirely NEW MONITOR, which I also created a new profile for. On both monitors, both cables, the issue only occurs when the Radeon and DC profile LOADER are installed.

  8. One important detail is, that the problem only seems to occur when the profile loader is running. When I disable the profile loader (through startups) and then start DC and click the install profile, everything works as intended. Also, when I created a new profile yesterday and installed it, there were no problems even after several hours. Now, after a restart with the profile loader installed the problem is reproducable by either waiting X amount of time or running DC and click the install profile button.

    Confirmed and reproduced. I”ll add that “X amount of time” here is reliably as soon as the loader loads in at startup.

  9. Hinter: I read the other thread you posted, pretty sure that’s the same issue.

    I’m also noticing that a lot of people are talking about DC3 in that thread and I think they’re making the same casual reference I did: referring to the Profile Loader as DC3.

Comments are closed.