new_disprd failed with instrument access failed

[nizmoz]

New install on my new PC.  I can’t seem to get it to work.  If anyone can look at the logs below, it would be great.  I have tried reinstalling everything and nothing works. I disabled RGB Fusion as I saw someone else say to do that as I have a Gigabyte Aorus Xtreme board.

I am using the ColorMunki Display.  I am a noob to using this, so any advice with steps would benefit me greatly.  Thank you!

18:35:54,130 Calibrate & profile
18:35:54,168
18:35:54,226 Detecting output levels range…
18:35:54,230 ——————————————————————————–
18:35:54,230 Session log: 0_16
18:35:54,230
18:35:54,230 Working directory:
18:35:54,232 c:\
18:35:54,232 users\
18:35:54,232 russel~1\
18:35:54,233 appdata\
18:35:54,233 local\
18:35:54,233 temp\
18:35:54,233 DisplayCAL-xgewds\
18:35:54,233
18:35:54,233 Command line:
18:35:54,234 C:\Users\Russell ↲
↳ Z\AppData\Roaming\DisplayCAL\dl\Argyll_V2.1.1\bin\dispread.exe
18:35:54,234 -v
18:35:54,234 -D8
18:35:54,236 -k
18:35:54,236 “C:\Program Files (x86)\DisplayCAL\linear.cal”
18:35:54,236 -d1
18:35:54,236 -c1
18:35:54,236 -yn
18:35:54,236 “-P0.500166168162,0.500495540139,1.0”
18:35:54,236 0_16
18:35:54,237
18:35:54,528 DisplayCAL: Starting interaction with subprocess
18:35:54,542 get_a_display called with ix 0
18:35:54,543 MonitorEnumProc() called with hMonitor = 0x10001
18:35:54,543 MonitorEnumProc() set initial monitor info: 0,0 3440,1440 name ‘\\.\DISPLAY1’
18:35:54,545 get_displays about to get monitor information for 0
18:35:54,545 Mon 0, name ‘\\.\DISPLAY1\Monitor0’
18:35:54,545 Mon 0, string ‘Generic PnP Monitor’
18:35:54,546 Mon 0, flags 0x3
18:35:54,546 Mon 0, id ‘MONITOR\DELA0A6\{4d36e96e-e325-11ce-bfc1-08002be10318}\0007’
18:35:54,546 Mon 0, key ↲
↳ ‘\Registry\Machine\System\CurrentControlSet\Control\Class\{4d36e96e-e325 ↲
↳ -11ce-bfc1-08002be10318}\0007’
18:35:54,546 EnumDisplayDevices failed on ‘\\.\DISPLAY1’ Mon = 1
18:35:54,546 get_displays added description ‘DISPLAY1, at 0, 0, width 3440, height 1440 ↲
↳ (Primary Display)’ to display 0
18:35:54,546 Selected ix 0 ‘\\.\DISPLAY1′ DISPLAY1, at 0, 0, width 3440, height 1440 ↲
↳ (Primary Display)’
18:35:54,546 Argyll ‘V2.1.1’ Build ‘MSWin 32 bit’ System ‘Windows V10.0 SP 0’
18:35:54,548 new_icompath: called with mask 0x1ffff
18:35:54,548 icoms_refresh_paths: called with mask = 0x1ffff
18:35:54,549 icoms_refresh_paths: looking for HID device
18:35:54,549 hid_get_paths: called
18:35:54,551 found HID device ‘\\?\hid#virtualdevice&10&col03#2&d21ad2d&0&0002#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}\kbd’, inst 1 but unable get PID and VID
18:35:54,552 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c081&mi_00#9&34799d9c&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 2 but not one we’re looking for
18:35:54,552 found HID device ‘\\?\hid#vid_1b1c&pid_0c10#7&1f19fe3b&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 3 but not one we’re looking for
18:35:54,553 found HID device ‘\\?\hid#virtualdevice&10&col01#2&d21ad2d&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 4 but unable get PID and VID
18:35:54,555 found HID device ‘\\?\hid#vid_046d&pid_c232#2&6aae8d8&0&0000#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}\kbd’, inst 5 but not one we’re looking for
18:35:54,555 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c081&mi_01&col01#9&585e811&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}\kbd’, inst 6 but not one we’re looking for
18:35:54,555 found HID device ‘\\?\hid#vid_046d&pid_c231#2&2d0d5a5a&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 7 but not one we’re looking for
18:35:54,555 found HID device ↲
↳ ‘\\?\hid#vid_1b1c&pid_1b09&mi_00#9&256f8e92&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}\kbd’, inst 8 but not one we’re looking for
18:35:54,555 found HID device ↲
↳ ‘\\?\hid#vid_1532&pid_0037&mi_01&col01#8&295beb72&0&0000#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}\kbd’, inst 9 but not one we’re looking for
18:35:54,555 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c081&mi_01&col02#9&585e811&0&0001#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 10 but not one we’re looking for
18:35:54,555 found HID device ↲
↳ ‘\\?\hid#vid_1532&pid_0037&mi_02#8&3b9742be&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}\kbd’, inst 11 but not one we’re looking for
18:35:54,556 found HID device ↲
↳ ‘\\?\hid#vid_0d8c&pid_0014&mi_03#9&374442dc&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 12 but not one we’re looking for
18:35:54,556 found HID device ↲
↳ ‘\\?\hid#vid_048d&pid_8297&col01#6&1d60bfb1&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 13 but not one we’re looking for
18:35:54,556 found HID device ‘\\?\hid#vid_0765&pid_5020#7&1620cacc&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 14 that we’re looking for
18:35:54,556 icompaths_add_hid ‘(null)’ got dctype 0x0
18:35:54,558 icompath_set_usb ‘hid:/14 (X-Rite i1 DisplayPro, ColorMunki Display)’ ↲
↳ returning dctype 0x10004
18:35:54,558 found HID device ↲
↳ ‘\\?\hid#vid_048d&pid_8297&col02#6&1d60bfb1&0&0001#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 15 but not one we’re looking for
18:35:54,558 found HID device ↲
↳ ‘\\?\hid#vid_1b1c&pid_1b09&mi_02#9&223eecf2&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}\kbd’, inst 16 but not one we’re looking for
18:35:54,558 found HID device ↲
↳ ‘\\?\hid#vid_1532&pid_0037&mi_01&col02#8&295beb72&0&0001#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 17 but not one we’re looking for
18:35:54,559 found HID device ‘\\?\hid#virtualdevice&10&col04#2&d21ad2d&0&0003#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 18 but unable get PID and VID
18:35:54,561 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c081&mi_01&col03#9&585e811&0&0002#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 19 but not one we’re looking for
18:35:54,561 found HID device ↲
↳ ‘\\?\hid#vid_1532&pid_0037&mi_01&col03#8&295beb72&0&0002#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 20 but not one we’re looking for
18:35:54,562 found HID device ↲
↳ ‘\\?\hid#vid_1532&pid_0037&mi_01&col04#8&295beb72&0&0003#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 21 but not one we’re looking for
18:35:54,562 found HID device ‘\\?\hid#virtualdevice&10&col02#2&d21ad2d&0&0001#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}\kbd’, inst 22 but unable get PID and VID
18:35:54,562 found HID device ‘\\?\hid#vid_1532&pid_0037&mi_00#8&584adb0&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 23 but not one we’re looking for
18:35:54,562 found HID device ↲
↳ ‘\\?\hid#vid_1532&pid_0037&mi_01&col05#8&295beb72&0&0004#{4d1e55b2-f16f- ↲
↳ 11cf-88cb-001111000030}’, inst 24 but not one we’re looking for
18:35:54,563 found HID device ‘\\?\hid#vid_0451&pid_ca01#8&24b5e32e&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 25 but not one we’re looking for
18:35:54,563 found HID device ‘\\?\hid#virtualdevice&10&col05#2&d21ad2d&0&0004#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 26 but unable get PID and VID
18:35:54,563 found HID device ‘\\?\hid#vid_2f96&pid_0100&mi_02#7&38be05e&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 27 but not one we’re looking for
18:35:54,563 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c081&mi_01&col04#9&585e811&0&0003#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 28 but not one we’re looking for
18:35:54,565 found HID device ‘\\?\hid#vid_1b1c&pid_1b09&mi_01#9&19850d0&0&0000#{4d1e55b2 ↲
↳ -f16f-11cf-88cb-001111000030}’, inst 29 but not one we’re looking for
18:35:54,565 found HID device ↲
↳ ‘\\?\hid#vid_046d&pid_c081&mi_01&col05#9&585e811&0&0004#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’, inst 30 but not one we’re looking for
18:35:54,565 icoms_get_paths: returning 1 paths and ICOM_OK
18:35:54,565 icoms_refresh_paths: looking for USB device
18:35:54,565 usb_get_paths opening device ‘\\.\libusb0-0001’
18:35:54,565 usb_get_paths opening device ‘\\.\libusb0-0002’
18:35:54,565 usb_get_paths opening device ‘\\.\libusb0-0003’
18:35:54,565 usb_get_paths opening device ‘\\.\libusb0-0004’
18:35:54,566 usb_get_paths opening device ‘\\.\libusb0-0005’
18:35:54,566 usb_get_paths opening device ‘\\.\libusb0-0006’
18:35:54,566 usb_get_paths opening device ‘\\.\libusb0-0007’
18:35:54,568 usb_get_paths opening device ‘\\.\libusb0-0008’
18:35:54,568 usb_get_paths opening device ‘\\.\libusb0-0009’
18:35:54,568 usb_get_paths opening device ‘\\.\libusb0-0010’
18:35:54,568 usb_get_paths opening device ‘\\.\libusb0-0011’
18:35:54,569 usb_get_paths opening device ‘\\.\libusb0-0012’
18:35:54,569 usb_get_paths opening device ‘\\.\libusb0-0013’
18:35:54,569 usb_get_paths opening device ‘\\.\libusb0-0014’
18:35:54,569 usb_get_paths opening device ‘\\.\libusb0-0015’
18:35:54,569 usb_get_paths opening device ‘\\.\libusb0-0016’
18:35:54,571 icoms_refresh_paths: now got 1 paths
18:35:54,571 icoms_refresh_paths: looking for serial ports
18:35:54,571 serial_get_paths: called with mask = 131071
18:35:54,571 serial_get_paths: looking up the registry for serial ports
18:35:54,572 serial_get_paths: There don’t appear to be any serial ports
18:35:54,572 icoms_refresh_paths: we now have 1 devices and are about to sort them
18:35:54,572 icompaths_make_dslists ‘hid:/14 (X-Rite i1 DisplayPro, ColorMunki Display)’ ↲
↳ dctype 0x10004
18:35:54,572 icoms_refresh_paths: returning 1 paths and ICOM_OK
18:35:54,572 Number of patches = 3
18:35:54,572 Setting up the instrument
18:35:54,572 new_inst: called with path ‘hid:/14 (X-Rite i1 DisplayPro, ColorMunki ↲
↳ Display)’ type ‘i1D3’
18:35:54,572 new_icoms ‘hid:/14 (X-Rite i1 DisplayPro, ColorMunki Display)’ itype ‘i1D3’ ↲
↳ dctype 0x10004
18:35:54,572 icom_copy_path_to_icom ‘hid:/14 (X-Rite i1 DisplayPro, ColorMunki Display)’ ↲
↳ returning dctype 0x10004
18:35:54,572 i1d3_init_coms: called
18:35:54,573 i1d3_init_coms: About to init HID
18:35:54,573 icoms_set_hid_port: About to set HID port characteristics
18:35:54,573 hid_open_port: about to open HID port ‘hid:/14 (X-Rite i1 DisplayPro, ↲
↳ ColorMunki Display)’ path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#7&1620cacc&0&0000#{4d1e55b2-f16f-11cf
18:35:54,573 -88cb-001111000030}’
18:35:54,658 hid_open_port: Failed to open path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#7&1620cacc&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’ with err 32
18:35:54,660 hid_open_port: Failed to open path ↲
↳ ‘\\?\hid#vid_0765&pid_5020#7&1620cacc&0&0000#{4d1e55b2-f16f-11cf- ↲
↳ 88cb-001111000030}’ with err 32
18:35:54,660 i1d3_init_coms: set_hid_port failed ICOM err 0x20000
18:35:54,660 init_coms returned ‘Communications failure’ (Communications failure)
18:35:54,660 new_disprd failed because init_coms failed
18:35:54,663 icoms_del: called
18:35:54,663 dispread: Error – new_disprd failed with ‘Instrument Access Failed’
18:35:54,663
18:35:54,767 DisplayCAL: Reached EOF (OK)
18:35:54,769 …aborted.

Calibrite Display Pro HL on Amazon  
Disclosure: As an Amazon Associate I earn from qualifying purchases.

[Florian Höch]

Make sure no other software is using the device (error 32 is a sharing violation, i.e. device in use by another process). Disable X-Rite Device Services Manager when in doubt.

[nizmoz]

Yeah, no other software that I could find was doing it. I uninstallef xrite software too.  What I finally did was move it from the USB 2.0 ports I had to the 3.1 port and it started to work fine after that.  No idea why?

[Florian Höch]

There are some really badly written motherboard/USB peripheral utilities that grab any USB (2?) device they can get their hands on.

[e30Birdy]

I have the same issue with DisplayCal. Error 32. I have stopped the x-rite process and uninstalled LG Config studio and the x-rite software. How do I figure out what software is using my device?

• This reply was modified 2 years, 9 months ago by e30Birdy.

[e30Birdy]

I think i figured it out and it is Gigabyte RGB Fusion since that software sucks

[Author]

Posts