I’ve installed Ensenso SDK on an IPC. When opening NxView I’m getting the error which can be seen in the image attached. I have installed multiple versions of Ensenso SDK 4.0.x, and all give the same issue. Any suggestions would be helpful.
Hello Marvin,
I am not yet aware of such a problem. A search for the given error code lists references to updating the graphics driver or that AppInit_DLLs is misconfigured in the registry.
To better understand/trace the problem it would be good to know which Windows version exactly is being used (Settings → System → Info → Windows Specification). It would also be useful to know which processor, graphics card and version of the graphics card driver is being used.
Kind regards,
Joel Kaiser
Hello,
after an additional search, I noticed that we have already received a report of such a case in our history. In that case, however, a virtual environment was used and not all CPU extensions of the host were enabled on the virtual machine. Do you use a virtual environment?
Regards
Joel
Hi Marvin,
what would also be interesting is, if there are any specific security configurations on the system. You could try to launch the application with administrative rights.
Is this a normal Windows Pro, or Embedded/IoT? Maybe you can give us the model of the IPC as well?
Hi Joel,
Thank you for your reply. I am not running on a virtual environment, so the issue is not related to that.
Herewith are some specifications of the PC:
CPU:
Intel Pentium J6426 @ 2GHz
GPU:
Intel UHD graphics
IPC type: ONLOGIC HX330
specs:
Hi Marvin,
as far as I can tell at the moment, the CPU is missing the popcnt instruction, which is part of our system requirements. Why Windows now issues such a cryptic message is a mystery to me. The popcnt instruction is only used late in execution, so windows seems to check on startup which instructions are used by the program to produce this message.
To be on the safe side and make sure that the CPU does not support popcnt, you can have the information read out using software like CPU-Z | Softwares | CPUID
Kind regards
Joel Kaiser
Hi Joel,
Thanks for looking into this issue.
It seems like this CPU does support popcnt:
Do you have any other suggestions on what it could be?
I just found that we are using another IPC which is the exact same model as this one. On this IPC we do have the exact same issue.
Hi
thanks for your fast response.
Unfortunately, I don’t have a suggestion at the moment. We will now try to recreate this behavior in house and check whether we have made a mistake in the handling of the instruction sets or whatever else may be the cause.
Hi Marvin,
at the moment I am waiting for hardware to recreate the case here. In the meantime, however, it occurred to me that our Qt libraries, supplied with ensensosdk, may have been given the wrong flags. I will definitely look into this.
Depending on what knowledge you have and whether you want to/are able to become active yourself, I have two options for you.
Best regards
Joel
Hi Joel,
We wanted to use this IPC for a demo station, but since it was not working at the time we grabbed another model. We do have the intention to buy this (or similar) IPC models in the future, so it would be nice to know if it is compatible or not.
Please let us know if you have an update!
Happy holidays!
Marvin.
ps. our office is closed for the next 2 weeks during the holidays
Hi Marvin,
we can finally confirm that we can reproduce your issue on a similar system. It looks like this is a bug we can fix. Sorry for the inconvenience. We will let you know in which release this fix will be in.
best regards, Rainer
Hi Rainer,
Good to hear you guys were able to reproduce the issue! Please let us know if you have more information about the update.
Many thanks!
Hello Marvin
I have already sent you a personal message, but wanted to post the information again in this thread in case other people come across the same issue.
We have identified the problem and a global usage of the AVX instruction set had found its way in (since 3.6) and was executed without further checks on x86/x64 CPUs. The bug has been fixed internally and is planned for upcoming (bugfix) releases for 4.1/4.0/3.6. A preview version can be distributed on request.
Best regards
Joel
