Wpf App crashing when closing


Finally we received the Beckhoff PC which will be running at the customer. The Beckhoff PC is a CX5140-0125. Installed is a 32 Bit Windows 7 Embedded Standard OS.

Since it is 32 Bit, I installed the CVB 13.00.006 (Win32) setup. Installation went fine, setting up connected Cameras/Devices working fine, opening the device also works fine, capturing images works fine, everything works as expected until I close the application, then the window closes but it crashs. I can not debug it, i cant find out what the issue is, i can give you no more than this crash window log:

Problem signature:
Problem Event Name: APPCRASH
Application Name: WpfAviPlayback.exe
Application Version:
Application Timestamp: 5b1518eb
Fault Module Name: CVCIMG.DLL
Fault Module Version:
Fault Module Timestamp: 59c4ecd2
Exception Code: c0000005
Exception Offset: 000a9278
OS Version: 6.1.7601.
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:

If the online privacy statement is not available, please read our privacy statement offline:

I installed Remote Debugging Tools on the Beckhoff to try debugging and find out where this happens, and it happens after OnExit, so basically after the App is closed.

This happens in my own project as well as in the WpfGenICamExample project which you posted to me in another thread (just changed from loading avi files to a real device).

On my development machine, this error doesnt occur, and the development machine is running WIndows 10, so I dont know whether this might be worth the information?

Edit: On my development machine it also seems to crash, but not visible to the user. However I installed WinDbg and this is logged when the app closes:

(2374.11f4): Access violation - code c0000005 (!!! second chance !!!)
eax=00000000 ebx=33472a5d ecx=0981e1f4 edx=059a4480 esi=0981e1e8 edi=ffffffff
eip=0f0f9278 esp=00eff63c ebp=00eff65c iopl=0 nv up ei pl nz ac po nc
cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210212
0f0f9278 ff10 call dword ptr [eax] ds:002b:00000000=???

Maybe that helps to locate the issue? :smile:
Thanks in advance

1 Like

Hi @johmarjac,

we have not seen this, yet. But if you can reproduce it in WinDbg you could save a dump via

.dump /f C:\Users\<YourUserName>\Documents\WpfAviPlayback.dump

and contact support@stemmer-imaging.de on how to send us the file.

@parsd I cannot run WinDbg on Target Machine, only on Developer Machine.
Also I cant find a way to input any commands into WinDbg such as .dump
In CMD this command doesnt work either, where do I have to enter that?

The dump of your development machine would be fine. Normally you should have the process window with a command prompt at the bottom:

@parsd Ok, I was using the Windows 10 App from Microsoft Store, seems like this feature is missing there. I am currently manually reinstalling Windows SDK to install Debugging Tools as they seem to be missing in my currently installed Windows SDK (installed by VS2017). Quite annoying, when I have the dump, I will contact support@stemmer-imaging.de

Thanks for the help

Meanwhile I´ve contacted support and after some days of investigation we found the issue and it has to do with Device Discovery.

Thanks for the great support.

1 Like