Pix4D crashes during step 1 even with very small projects. I have tried adjusting different setting, updating GPU, and reinstalling Pix4D. I get this error code in event viewer. Does anyone have a solution?
Hello,
It is difficult to say why you are experiencing a crash from this event log. When you uninstalled Mapper, did you do a complete uninstall which includes deleting some leftover folders in the registry? If not, please follow the steps in the support article below.
Hi, I’m experiencing the same issue.
The app worked perfectly for two months, but after returning from vacation, it suddenly started crashing on the first step.
It either crashes or I get an error in the console, with the cause pointing to camera.dll. I’ve tried completely uninstalling the app (including clearing the registry and all related files) and reinstalling, but the problem persists.
In case of error but no crash I get this:
[Info]: Statistics before adding tracks error: 0.115019 nrProjections: 2791098 nrTracks: 751924 trackSize: 751924 s0(0) s1(0) s2(415066) s3(133645) s4(63485) s5(139728)
[Info]: Add tracks with error 2.5
[Processing]: Add matches.
[Processing]: Substep Rematch finished.
[Error]: Caught unknown exception during initial processing!
[Info]: OS Power Save: Enable
[Info]: >>>Step1<<< done in 02m:26s:777ms / 2.44628 min.
In case of the crash I’ve attached the event viewer logs and also the logs from the app.
The personal details from logs were trimmed because of security issues.
I have gone through removing pix4d and the troubleshooting and it crashes for some users but for other users it isn’t. We can run it using the same images and sometimes it will crash and throw the camera.dll error. I’ve gone through removing the graphics drivers and readding with the desktop drivers as well. Any other ideas or things I could look at? Thanks.
These can sometimes be difficult problems to troubleshoot, particularly if everyone has different hardware setups. It is best if you can open a support ticket.
However, there is a known issue with 13th and 14th-generation Intel CPUs that causes issues similar to what everyone is describing. So if you have a 13th or 14th-generation chip, it is highly recommended to update your computer’s BIOS. Intel released an update that fixed this problem. You can read more in the article below:
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.