#14621 (Bug) Unhandled exception at 0x003A2257 (faulthandler.pyd) in DisplayCAL.exe

+1 0

Closed as Works For Me
Component: DisplayCAL
Created by coquecigrue

Last modified


at 14:22:08,904
on windows 7 with displaycal 3.7.1 I at the end of calibration a crash occur
debugger tell me:

Unhandled exception at 0x10002257 (faulthandler.pyd) in DisplayCAL.exe: 0xC0000005: Access violation reading location 0x0000004D

displaycal. 1.log :

2018-11-25 14:22:08,158 Input black XYZ: 0.000352 0.000351 0.000293
2018-11-25 14:22:08,160 Input white XYZ: 0.964200 1.000000 0.824900
2018-11-25 14:22:08,234 Output black RGB: 0.0000 0.0000 0.0000
2018-11-25 14:22:08,236 Output white RGB: 99.9998 100.0000 100.0000
2018-11-25 14:22:08,338 Filling cLUT…
2018-11-25 14:22:08,563 100%
2018-11-25 14:22:08,904 Smoothing B2A1…
2018-11-25 14:32:01,289 ================================================================================
2018-11-25 14:32:01,289 DisplayCAL.exe 3.7.1.0 2018-11-01T23:35:36.906Z
2018-11-25 14:32:01,305 Windows 7 Ultimate Service Pack 1 Build 7601 x86_64
2018-11-25 14:32:01,305 Python 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)]
2018-11-25 14:32:01,305 CA file C:\Program Files (x86)\DisplayCAL\cacert.pem
2018-11-25 14:32:01,305 Faulthandler 3.0


displaycrash (application/zip | 2018-11-25 15:07:38)
Prime95 (image/png | 2018-11-26 13:15:52)


7 thoughts on “Unhandled exception at 0x003A2257 (faulthandler.pyd) in DisplayCAL.exe”

  1. nothing  suspect,

    As it crash I was monitoring  ram, processor  and nothing special

    I use a macpro 2008 with 14g of ram and it works fine under windows7

    1. You’re segfaulting at random points. Run prime95 for a few hours to check if the system is really stable.

      You said you’re running Windows. Is this a virtual machine or via bootcamp?

  2. ran the torture test for 17hours, no problem

    tried again to run DisplayCal. crashed the same …

    it seems  DC do not like the cocktail mix hard mac & soft windows

    was able to calibrate with i1

    HCFR works fine

    Thanks anyway

    Attachment:
    1. Well, there’s something wrong with the system, either hardware, or software (drivers probably). Just run it natively under macOS.

Comments are closed.