#1882 (Bug) DisplayCAL Profile Loader 3.1 crash/application error on Win10 shutdown

+1 0

Closed as Fixed
Component: DisplayCAL | Milestone: 3.1.1
Created by Warner

Last modified

I have Win10 Pro (x64) on a laptop and desktop. I am also using the Classic Shell start menu interface on both machines. For my laptop, when performing a regular shutdown of Windows, the main Windows screen disappears as usual, but then a blue background screen appears with the heading “Closing 1 app and shutting down” plus “This app is preventing shutdown”. In a separate box there appears “DisplayCAL-apply-profiles.exe – Application Error” and “The instruction at 0x0000000002476B86 referenced memory at 0x00000000FFFFFFFF. The memory could not be read. Click on OK to terminate the program”. The desktop also gets the same error on shutdown but with different memory addresses referenced. For my desktop, I also sometimes get a different error message on shutdown where the separate box displays an error that says “The exception Privileged instruction (0xc0000096) occurred in the application at location 0x000000000253A95A. Click on OK to terminate the program.” Clicking on OK terminates the program and then allows Win10 to shutdown properly.

DisplayCAL-apply-profiles (application/zip | 2016-02-21 20:19:05)

30 comments on “DisplayCAL Profile Loader 3.1 crash/application error on Win10 shutdown”

  2. Thanks, that fixed the problem in both the laptop and the desktop.  No more crashing during shutdown and restart.  Also I appreciate that the Win10 notification windows no longer pop in and out which I see you eliminated in this beta version.

  3. Actually, I spoke too soon.  My laptop seems to be error-free now on restart/shutdown, but my desktop still has the same error on restart/shutdown.

  4. It is inconsistent on the desktop computer.  I just did a restart now and it was fine, but the previous restart had the same error.

    1. It seemed fine for a day yesterday but unfortunately just had the same error this morning when shutting down the desktop computer.

    2. With this 3.1.0.3 beta, it seemed fine for a day yesterday but unfortunately just had the same error this morning when shutting down the desktop computer.

  6. Sure that it is actually the beta loader that is running? (Safest way to make sure would be to uninstall all previous versions)

    1. I will try the full uninstall later tonight instead of just overwriting the existing install (I do exit the loader first though before overwriting) and when you hover the cursor over the loader icon it does say 3.1.0.3 beta.

      1. That’s good. Just overwriting the exe won’t work, you’ll need to copy the whole folder otherwise it’ll still use the old libraries (which contain the actual profile loader code).

        1. I have been copying in and overwriting the entire folder and not just the .exe of the loader.

  7. With the 3.1.0.3 version when I had installed it by just overwriting the previous install, it only had the error that one time that I had posted.  I then tried your advice and completely uninstalled the DisplayCAL program and just manually installed the program.  So far the 3.1.0.3 loader has not crashed on me.  I was waiting for a whole day to go by before reporting back and so far it has been fine.  Maybe there was something left over by just overwriting, who knows?  I know for sure, previously, I had closed down the loader completely  before installing by overwriting.  Maybe the clean install of 3.1.0.3 did the trick?  Since you uploaded 3.1.0.4, I will try that also with a clean install and report back.  Thanks.

  8. So far the 3.1.0.3 loader has not crashed on me.

    Many thanks, that’s great news.

    Since you uploaded 3.1.0.4, I will try that also with a clean install and report back.

    Great, thank you.

  9. Version 3.1.0.4 beta seems stable.  No crashes of the loader at all on restart/shutdown on both Win10 machines.

  10. I’ve had what appears to be exactly the same problem on several Win 7 machines.  Unfortunately, it is NOT fixed for me with 3.1.0.4.

    I did completely uninstall DisplayCAL and then manually installed the new files.  The loader does report itself as 3.1.0.4.

    The problem is somewhat intermittent in that it does not happen EVERY time,  but it does happen most of the time.

  11. It may help for me to report another message that I get under the same conditions, but much more infrequently:

    “C++ assertion “IsModal() failed at  … dialog.cpp (221) in wxDialog::EndModal():EndModal called for non-modal dialog”

    1. Hmm , from the log it looks like the 3.1.0.4 loader exits OK. At the moment, I have no idea what the cause of your crash could be, as it looks like the crash happens after the logging system shuts down (which is the very last thing that happens before exiting completely) and so there’s no trace of it in the log.

      1. Sorry to be so long replying, but I was trying some things to see if I could narrow down the conditions that cause this (3.1.0.5 is no better).  I’ve tried it now on 4 different machines and get the same result on each.  The only thing that I can think of that MIGHT be different from your setup is that all these machines have 2 or more monitors.  Do you have a Win 7 machine with multiple monitors?

        Since it doesn’t fail absolutely every time (only 95% or more), I’m wondering if the problem might be some other component (that you have some dependency on) shutting down just before it shuts down.

        The cases in which this is a real problem for me is where I am shutting down a machine remotely and this keeps the machine from shutting down.  (In other cases where I am shutting the machine down manually, it’s just a nuisance.)  I’ve determined that I can add code to shut the profile loader down before I shut down the machine.  That would be a workaround for me but, of course, I’d rather have the problem solved.

        1. Do you have a Win 7 machine with multiple monitors?

          Both my Win7 and Win10 have a dual monitor setup.

          I’ve determined that I can add code to shut the profile loader down before I shut down the machine.  That would be a workaround for me but, of course, I’d rather have the problem solved.

          There’s very little chance for me finding a fix as the problem is not reproducible on my end.

          1. That seems to have fixed it.  I tried several times and could not make it fail.  If anything changes, I’ll report back.  Thanks.

      1. Guess I spoke too soon again.  It happened just once now  on shutdown with my Win10 desktop computer.  Overall though, very rarely and it is easy enough to  hit OK and then it will shutdown.

  14. That is correct.  No problems for me with 3.1.0.4 and 3.1.0.5.  With that other guy, who knows?

Comments are closed.