# zCrashReport.exe

**URL:** <https://devforum.zoom.us/t/zcrashreport-exe/3094>\
**Category:** Windows\
**Created:** [January 24, 2019, 6:00pm UTC](https://devforum.zoom.us/t/zcrashreport-exe/3094 "2019-01-24T18:00:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![lkrammes](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/lkrammes/32/137_2.png) [@lkrammes](https://devforum.zoom.us/u/lkrammes)\
**Post date:** [January 24, 2019, 6:00pm UTC](https://devforum.zoom.us/t/zcrashreport-exe/3094/1 "2019-01-24T18:00:19Z")

</div>

When our application runs we initialize the sdk and then authorize with appkey/secret, then optionally authentication with username and password. However, if the app freezes/crashes on something that is unrelated to our Zoom functionality, zCrashReport.exe runs.

Does that run on all crashes? or just Zoom SDK related ones?

What wires that in to run on a crash? Initializing the sdk? Authorizing the sdk?

Thanks.

---

<div class="post-metadata">

**Author:** ![dats\_liao](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/dats_liao/32/464_2.png) [@dats\_liao](https://devforum.zoom.us/u/dats_liao)\
**Post date:** [January 30, 2019, 12:57am UTC](https://devforum.zoom.us/t/zcrashreport-exe/3094/2 "2019-01-30T00:57:45Z")

</div>

thanks for your feedback. yes, this is app level exception handler. if your app encounters the crash or main thread deadlock, we will capture the dump for troubleshooting.you can find the dump file form %appdata%/zoomsdk/logs folder.

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 6:10pm UTC](https://devforum.zoom.us/t/zcrashreport-exe/3094/3 "2020-08-21T18:10:00Z")

</div>

Closed on August 21, 2020, 6:10pm UTC


