Dear Micro-Manager developers and other users,
I was wondering whether you might be able to direct us to someone who could help us debug the cause of the following Micro-Manager crashes? We urgently need Micro-Manager to work.
The steps that lead to the crashes are as follows:
System configuration:
Camera: Andor Sona-4BV6U 4.2B-6
Driver: AndorDriverPack3Setup-3.14.30022.0
USB 3.1 card: StarTech PEXUSB312A2 (provided with the Andor Sona camera)
PCIe slot: X16
Motherboard: X399 AORUS XTREME (rev. 1.0)
Micro-Manager: MMSetup_64bit_2.0.0-gamma1_20200527.exe 27-May-2020 19:53 150M
RAM: 8 GB
Sequence buffer size: 5120 MB
Crash scenario 1:
- Start Micro-Manager
- Click “Multi-D Acq.”
- Select “Multiple Positions (XY)”
- Click “Edit Positions List” and add a couple of positions by moving the stage and clicking “Mark”
- Click “Acquire!”
- Error message displayed: “Error: Internal inconsistency: unknown system exception occurred”
CoreLog attached: CoreLog20200528T005528_pid15864-crashed-when-clicked-Acquire-in-multiD-with-XY-selected.txt
Note to aid in debugging: I’m able to acquire images at multiple time points (as opposed to XY positions) in Multi-Dimensional Acquisition, as long as no other “dimensions” (e.g. XY, channels, etc.) are selected.
Crash scenario 2:
- Start Micro-Manager
- Click “Live” (images are displayed, no problem)
- Click autofocus button (binoculars)
- Error message displayed: “Error: Internal inconsistency: unknown system exception occurred”
CoreLog attached: CoreLog20200528T005013_pid5688-crashed-when-clicked-autofocus-while-live-view-on.txt"
Note to aid in debugging: Autofocus works without crashing if autofocus is started when no image is being displayed, as long as I first click menu item Tools > Refresh GUI.
Crash scenario 3:
- Start Micro-Manage
- Click “Live” (images are displayed, no problem)
- In the image window, click “Live” to stop acquisition, so “Snap” button becomes active
- Error message displayed: “Error: Internal inconsistency: unknown system exception occurred”
CoreLog attached: CoreLog20200528T004907_pid11412-crashed-when-clicked-snap-after-stopping-live-view.txt
Note to aid in debugging: Note that images from the Sona are displayed without any problem by starting Micro-Manager and clicking “Live”. It’s when we try to do other things, like autofocus, multidimensional acquisition, or snap a picture, that Micro-Manager crashes with the “Error: Internal inconsistency” message. If I try to do anything after that error then all of the MicroManager windows close and I need to restart Micro-Manager.
The CoreLog files indicate that the “Internal inconsistency” error occurs when Micro-Manager calls “CMMCore::getImage()”.
The Andor SDK3 Micro-Manager page mentions the speed of the PCIexpress slot as a possible cause of the “Internal inconsistency” error, however our PCIexpress slot is X16 and we are able to acquire images even at high frame rates without crashes using the “Live” button.
I would be happy to provide additional information if needed to help debug.
Another question I have is, how do we keep the driver for the Andor Sona up to date? I was only able to get the version we have (AndorDriverPack3Setup-3.14.30022.0) by asking our sales person who provided a link to that one file. The link on the Andor SDK3 Micro-Manager page links to a page that says “The resource cannot be found”.
Thank you in advance for any help!
Best regards,
John Ramunas
ramunas@rejuvenationtech.com
CoreLog20200528T004907_pid11412-crashed-when-clicked-snap-after-stopping-live-view.txt (120.5 KB)
CoreLog20200528T005013_pid5688-crashed-when-clicked-autofocus-while-live-view-on.txt (118.0 KB)
CoreLog20200528T005528_pid15864-crashed-when-clicked-Acquire-in-multiD-with-XY-selected.txt (240.1 KB)
