What happens is we have a contact sync application. Soon after pressing a button that starts the main logic of the syncing in the application, the application stops working and Windows (7 in this case) says our application “has stopped working” after which the only possibility is to close the application via a button entitled “Close the application”.
One weird thing is that, on my development machine, the application works fine. It does not crash, does not throw any errors whatsoever. But, when packaged as an installer and installed on other machines it does stop working as described above.
Please let me know what apps I can use for debugging this better, how to find out more about this error, what is triggering it, how it can be solved etc.
Thanks in advance.
later edit
This is what is printed out in the event viewer log:
Faulting application name: ourappname.exe, version: 1.2.9.0, time stamp: 0x4f3926c8
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec49caf
Exception code: 0xc0000374
Fault offset: 0x000c33bb
Faulting process id: 0xecc
Faulting application start time: 0x01ccea61773d12e0
Faulting application path: C:\Program Files\path\to\ourappname.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: bb3977f0-5654-11e1-9a84-0800275ba797
Does that help?
Set up a global uncaught exception handler and log the error. For good measure, you can write a memory dump of your application and use WinDbg along with SOS.dll to get a rather precise look at what’s going on in your app (dbghelp.dll ships alongside WinDbg in Debugging Tools for Windows).