Windows Dev Center

Crash count reports

Important noteImportant Note:

This topic applies to the earlier Windows Phone Dev Center dashboard and not the new unified Dev Center dashboard. Since we are still in the process of migrating all developer accounts, the info here may not apply if your account has already been migrated to the new dashboard. For more info, see Using the unified Dev Center dashboard.

Here is some info to help you better understand crash reporting in Windows Phone Dev Center.

Any unhandled exception in the app process will trigger a crash dump. However, if the crash is in the OS code, we don’t show it as an app crash.


Crash reports don’t include app crashes from phones running Windows Phone OS versions earlier than 7.0.7355.

By default, the Crash counts page shows the five apps that crash the most within the selected start and end date period. If you want to view other apps, you’ll need to select them individually in the App dropdown. When multiple apps appear on the chart, clicking the app legends will hide unnecessary apps to help you focus on the ones you want to see.

Clicking Export creates an Excel spreadsheet of stack traces. Dev Center exports stack traces for all apps or for just one app, depending on the filter selection. If you have several apps, it’s easier to export them all at the same time. Note that when you export stack traces into Excel, you’re not limited to five apps as you are in the Crash count page.

The Excel spreadsheet shows the current, hot issues in the app. It lists the top ten crashes in the last 30 days. Each row represents a crash error condition in the app, not an individual occurrence of a crash. For instance, if one bug in the app caused the same crash to occur fifteen times (across one or more phones), you’ll see just one row in the Excel file, because the stack trace for all the fifteen occurrences would look the same. You might see some duplicate entries if multiples flows lead to the same bug.

In addition to the problem function, exception type, and stack trace, we also provide a .cab file for download if the crash occurred on Windows Phone 8. The .cab file contains crash data that can help you debug your app.

In order to debug with a .cab file, you need:

  1. WinDbg (x86 version)

  2. Symbols for your app

    Use the symbols for the version of your app in which the crash occurred.

  3. Symbols for Windows Phone 8

    These are publicly available. See instructions on the Microsoft Public Symbols page.

For more details about how to debug a .cab using WinDbg, see Analyzing a User-Mode Dump File with WinDbg.

Caution noteCaution:

Look at the crash counts regularly to keep informed of the most frequent app crashes. We advise that you address the top issues first.

Export files are in Open XML Excel format and you can view them using Microsoft Excel. If you want to parse these files programmatically, use Open XML SDK.

© 2015 Microsoft