Large number of crash-type reports without FailureHash or stack trace — clarification needed

Hello,

We have been analyzing the crash reports under the "Game Health: Failures and Events" section in Partner Center for our Windows game "The Walking Dead Survivors".

We have noticed that a very large proportion of reported events have EventType = crash, but do not contain any FailureHash, FailureName, or stack trace. These events also typically have only 1 occurrence per device.

We suspect these might be caused by user force-quitting the app, system shutdowns, or other non-exceptional terminations. However, they are currently being counted as crashes in the analytics report, which could significantly distort our crash rate metrics.

Could you please clarify:

1. Under what conditions does Partner Center record a crash without a FailureHash?
2. Are force-close actions (e.g., Task Manager, ALT+F4, system shutdown) included as crash-type events?
3. What is the best way to distinguish true code crashes from these events?

We would appreciate any technical explanation or documentation you can provide, and guidance on how to better interpret and filter these events.

I will attach sample report data

Thank you in advance.