- This topic has 9 replies, 4 voices, and was last updated 3 years, 1 month ago by
.
-
Posts
-
While it boots up fine, it appears to be having trouble when (manually) installing a profile, or when adding/removing monitors, probably similar to re-installing a profile.
The one apparently causing trouble has 2681 patches, but I converted it to a ‘simple’ 1xCurve+MTX.
So is it the amount of patches that makes it complex?
Is anyone else having issues with a large amount of patches in a multi-monitor setup?
Backstory: Both displays start flashing black on and off, then sometimes it works, but mostly DisplayCAL turns orange and fails while Nvidia Display driver just gives up and crashes entirely. Somehow i still get the one primary display, but playing back video and such is hardly possible without the display driver – so a reboot is the only option. As i didn’t know what the issue was I’ve tried every Nvidia driver since the beginning of time, but nothing made a difference. It made sense because Nvidia drivers are know to be buggy, and even after removing DisplayCAL (which was the first thing i did), the problem persisted. But as it turns out, the thing that remained was the display profile it had installed, only it was Windows loading it on its own. Soon as I removed the one with 2681 patches, it stopped bugging.
Okay, so i guess i was wrong about the patches.
Seems to happen now with any kind of profile, but only for one specific display (the one that had the very complex profile).
The confusing part was that even if i was trying the install a profile on the other display, it failed because apparently both of them need to be refreshed to make te change. But when i disable profiling completely on the problematic display, i can install any kind of profile on the other just fine.
So now i’m really confused as to why i can’t install a profile on this display any more, because i’m sure it used to be fine when i just started using DisplayCAL a few weeks ago. Could it be a bad cable acting up? That rebooting is okay, but installing a profile is too much? ????
It has actually installed a profile now (on both displays) after replugging the cable. Let’s see if it holds.
Really oddly specific symptoms to have from a dodgy cable connection, hard to believe it could be just that..
So is it the amount of patches that makes it complex?
It’s profile type, although for such complex profiles to be useful, they need a huge amount of patches. The opposite does not holds, a matrix profile with 500 patches will be “simple”.
I’m having a similar but perhaps even more horrible problem.
Everything was fine and then I started using DisplayCAL 3.8.9.3 to make some profiles for my TV and monitor.
At first it was all good, then I started sometimes having the screen flash a few times and it would say that it fails to load the profile right after profile creation and I tell it to install the profile, then it starts totally crashing out the graphics card so totally that nvidia system entirely disappears and my monitor gets turned into my printer!
A reboot made it all fine.
Then I would have to totally power down and cut power supply as a simple reboot would not always work.
At first that would only happen every few times I created a new profile after a reboot.
Then it started happening every single time after reboot and I used DisplayCal to create more than one profile. THe second time I would try to make a different type it would do that.
But at least a full new start would get it working fine again.
Then all of a suddent it has now entered this state where it doesn’t matter if I reboot, totally power down, it doesn’t even matter if I hook up my monitor or HDTV, whateer display, whateer anything, my entire video system crashed out the second I log in to windows, every single time!
My PC was made into an unusable disaster.
Killing off DisplayCAL service had no effect. Uninstalling DisplayCal had no effect.
I finally also then removed all profiles from the drivers/color directory but for the very simplest of all pure matrix gamma 2.4 REC709 profile I created in Photoshop on top of all the above and then rebooted a few times and finally it would let me log on without crashing out the nvidia drivers.
But if I try to load ANY other profile at all, even just by simply selecting it in Windows 10 color management screen for the graphics card/display, whether made by i1Profiler, Dell DUCS profiler, anything, never mind any DisplayCAL created profiles, the screen just starts flashing black more and more until after a few second just a total crash out. Video drivers just totally gone, display a slow, distorted ratio, bogged down mess. COlor management in Windows thinks my display is a printer! All monitors disappear in Windows. Nvidia control panels are all gone. Any drive folders I had open all close down.
My system is totally ruined! I have had to put all proejcts on hold for a couple days now as I can’t use any monitor profile at all other than for the barest, barest, most simple Photoshop creation. Even took all sorts of tricks and reboots to even get accepted.
Nothing I do restores my Windows 10 to working normally!
I sure hope I don’t have to do a nightmare full reinstall, I have so much stuff installed with so many settings, that would waste days.
I don’t know if I have ever had a piece of software so deeply appear to destroy my system before.
I mean it is so bad it is not just deleting all DisplayCal made profiles from spool/drovers/color is enough to get it work at all, but I even have to make sure that no probe based profile made any software, not even a basic Matrix profile from Dell DUCs (a sort of i1profiler variant for Dell UP2414Q which has internal calibration) can be used or it totally crashes out Nvidia card. W10 itself can no longer load any profile at all without crashing the whole system out beyond the crazy basic REC709 Gamma 2.4 profile I created in Photoshop which is as bare bones as any profile made can ever be.
Again this is even with DisplayCAL totally deleted out and removed. I also tried re-installing it and letting it take over all profile handling, hoping maybe that would fix whatever it made go bad, but nope, then it crashes out no matter what if any profile or any sort at all exists in color folder at all.
Not really sure if it is something DisplayCal set wrong and messed up or Argyll or Windows 10.
A real mess since my W10 is totally broken at the moment for any use of monitor profiles at all, can’t use wide gamut modes at all now for anything and even the REC709 Gamma 2.4 internal monitor and TV calibrations don’t have solid profiles now since I can only use a stock 100% perfect REC709 matrix plus Gamma 2.4 signature Photoshop created profile.
And not being to create DisplayCAl profiles would be a shame.
Not sure what went crazy.
Try “Display Driver Uninstaller DDU”, wipeout all nvidia GPU drivers on safe mode, reboot, reinstall, since they look to be the culprit.
Same issue, dual monitors w/ GPU crash (NVidia). In my case it’s inconsistent, otherwise exactly as described. I have to wince and change the profile and hope it survives. After reboot it’s all fine and the new profile is set.
You can reset the video driver with ctl+win+shift+b keys, (few people know). But even that doesn’t work. Requires a full reboot.
A few times I tried closing DisplayCal profile loader first and it worked, but since it’s inconsistent I don’t know if that’s the reason. The idea was that maybe it’s not prepared to have the calibration loaded into LUT yet, or they’re both trying to do it at the same time.
