# Execution crashes

The **Execution crashes** page lists binaries with the highest frequency of crashes over the last 7 days.

## Accessing Execution crashes <a href="#executioncrashes-accessingtheexecutioncrashesoverviewpage" id="executioncrashes-accessingtheexecutioncrashesoverviewpage"></a>

To access the Execution crashes dashboard, open **Alerts and Diagnostics** → **Execution crashes** from the navigation menu.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FWO14jmPBwNvLMjgoNLsN%2Fimage.png?alt=media&#x26;token=64333dd1-3f78-4308-a42a-d48b80651317" alt=""><figcaption></figcaption></figure>

## Interpreting Execution crashes <a href="#binaryprofiling-binaryprofilingtable" id="binaryprofiling-binaryprofilingtable"></a>

The **Execution crashes** page lists binaries/applications with execution crashes.

From the **Binaries with crashes** table, you can:&#x20;

* Search and sort the table to focus on specific issues.
* Access **Execution crashes details** dashboard for a selected application. Refer to the [#executioncrashes-executioncrashesdetailspage](#executioncrashes-executioncrashesdetailspage "mention").

{% hint style="info" %}
The **Binaries with crashes** table displays only the binaries running the main process. However, once a binary is selected, the dashboard includes all subprocesses.

Refer to [Binary grouping](https://docs.nexthink.com/platform/references/database-information-and-organization/binary-grouping) for more information.
{% endhint %}

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-c902fd37874e75e3e0225be6dfb6bc938954b1cb%2Fdiag-1691414656.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Binaries with crashes** table is organized by:

* **Binary name**: Click on the Binary name to access the Execution crashes detail page with troubleshooting options for a given binary.
* **OS**: Operating system, Microsoft Windows or macOS.
* **Product name**: The name of the product that matches what appears in the binary inventory. If the same binary name has multiple entries, Nexthink chooses the most common one.
* **User interface**: This column indicates if the binary has a user interface (UI). Note that certain binaries that run in the background may have configuration UI. If this is the case, a *yes* will appear for them in this column, but only if the binary runs on a Microsoft Windows operating system.
* **# devices with issues**: The absolute number of devices that have crashed within the past 7 days.
* **Crashes**: The total number of crashes within the past 7 days.

Nexthink uses cross-customer data to evaluate the reliability of various binary versions. Nexthink applies this knowledge to your environment to proactively inform you about:

* **Most stable version**: The system recommends an upgrade to the most stable binary version. There is only a recommendation if a better version is available and improvement is expected.
* **Potential crash reduction**: The potential reduction in the number of crashes, expressed in percentages. A 20% improvement means that you can expect a 20% reduction in the number of crashes compared to the number of crashes you are currently experiencing.

***

## Interpreting Execution crashes for a specific application <a href="#executioncrashes-executioncrashesdetailspage" id="executioncrashes-executioncrashesdetailspage"></a>

{% hint style="info" %}
Access the **Execution crashes** dashboard for a specific application by selecting an item from the [Execution crashes table](#binaryprofiling-binaryprofilingtable).
{% endhint %}

The Execution crashes dashboard for a specific application contains the following widgets grouped into the sections:

* **Assess issue**
* **Troubleshoot**

The top banner displays the number of devices for which system crashes have occurred:

Hover over the **Devices with issue** gauge on the right side of the banner to reveal the action menu, and **Drill down to devices—**&#x74;he Investigations page provides more information about impacted devices.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FiBAvJfQi4KUSCoRbE7gX%2Fimage.png?alt=media&#x26;token=a5e2c992-6aa8-4f0a-b3f3-b1e698ada529" alt=""><figcaption></figcaption></figure>

### Assess issue <a href="#executioncrashes-assessissue" id="executioncrashes-assessissue"></a>

From the **Assess issue** section, understand the context and scope of application crashes:

* **Number of crashes**: View application crashes over a given time period. Use the timeframe picker in the upper-right corner of the page to change the time period.
* **Number of devices with crashes:** View the number of devices with crashes over a given time period.
* **Technical**: Filter results by technical criteria such as **Operating System**, **Platform**, **Hardware model**, and **Virtualization type**.
* **Location**: Filter results by geolocation hierarchy. This section is visible only if the Geolocation feature is enabled. You can configure it on the [Product configuration](https://docs.nexthink.com/platform/user-guide/administration/system-configuration/product-configuration) page of the Administration module.
* **Organization**: Filter results by entity and organizational hierarchy.

### Troubleshoot <a href="#executioncrashes-troubleshoot" id="executioncrashes-troubleshoot"></a>

From the **Troubleshoot** section in the application-specific **Execution crashes** dashboard, you can:

* **Benchmark** execution crashes for this application across organizations.
* **Binary version Insights**, with version recommendations and more details.
* Crashes breakdowns by **OS build** and/or **Device model**.
* **Crash Details** to analyze the crash from the event log by running a pre-built remote action.

#### **Benchmark**

Compare the weekly **Percentage of devices** with application crashes in your organization against other companies that use Nexthink. The system displays the Benchmark feature when sufficient data is available.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fi71dSrU0kTX8V8zsEaDm%2Fimage.png?alt=media&#x26;token=e761fab1-6629-4ca5-91fa-1dc5825244c6" alt=""><figcaption></figcaption></figure>

#### Binary version

Nexthink uses cross-customer data to evaluate the reliability of various binary versions. Nexthink applies this knowledge to your environment to proactively inform you about:

* The **Situation in your company**, including the most unstable binary version when applicable.&#x20;
* **Insights** on the most stable version for the specific binary, along with its associated impact and benchmarking.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FWMCTuJCt4gxE7qTRYGT7%2Fimage.png?alt=media&#x26;token=6d4f906f-c460-4ea1-8058-0578f047e92a" alt=""><figcaption></figcaption></figure>

Under the **More details** table, explore metrics breakdowns and drilldowns by binary version based on the devices in your environment:

* **Version**: Binary versions your organization uses. Hover over a version to reveal the action menu and click on it.&#x20;
  * **Open binary profiling** to further investigate the issues relevant to this version of the binary.
* **Devices**: The number of devices using a given binary version.
* **Crashes**: The number of times the binary crashed for a given binary version.
* **Devices with crashes**: The number of devices with crashes is shown as an absolute number and as a percentage. The percentage displayed on the teal background shows benchmarking across all companies.
* **Time between crashes**: View the expected crash frequency for all executions. The system calculates this as the total execution time of the binary divided by the number of crashes.

#### OS build

Break down execution crashes by the operating system (OS) of the devices in your environment, running the specific binary version.

* **OS Build**: Version of the operating system the binary runs on.
* **Devices**: The number of devices using a given OS version.
* **Crashes**: The number of times the binary crashed for a given OS version.
* **Devices with crashes**: The number of devices with crashes is shown as an absolute number and as a percentage. The percentage displayed on the teal background shows benchmarking across all companies.
* **Time between crashes**: View the expected crash frequency for all executions by OS version. The system calculates this as the total execution time of the binary divided by the number of crashes.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fk1Xq09rGB4y7OBHbXxiE%2Fimage.png?alt=media&#x26;token=0a140f78-c8e5-48a5-8930-be32cd68f569" alt=""><figcaption></figcaption></figure>

#### Device model

Break down execution crashes by device models running the specific binary version.

* **Device model:** Version of the device the binary runs on.
* **Devices**: The number of devices using a given Device model.
* **Crashes**: The number of times the binary crashed for a given OS version.
* **Devices with crashes**: The number of devices with crashes is shown as an absolute number and as a percentage. The percentage displayed on the teal background shows benchmarking across all companies.
* **Time between crashes**: View the expected crash frequency for all executions by device model. The system calculates this as the total execution time of the binary divided by the number of crashes.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FKfvysuglDq0yx8kZ0JpC%2Fimage.png?alt=media&#x26;token=cd27bc76-177a-4ca3-9e4d-9b66befc765c" alt=""><figcaption></figcaption></figure>

#### **Crash details**

{% hint style="warning" %}
**Crash details** are exclusively available for Microsoft Windows-based binaries.
{% endhint %}

Analyze details of the crash from the event log by running a pre-built **Get application crash details** remote action to view the results of the event log analysis.

<details>

<summary>Executing the <strong>Get application crash details</strong> remote action on the target devices.</summary>

Follow these steps to execute the *Get application crash details* remote action on the devices of interest:

* Click on the **list of impacted devices** link in the description of the Crash details section. The link takes you to the Investigations page with the results of the query for all impacted devices.
* Select all the devices for which you wish to execute the remote action.
* Click on **Execute action** in the action bar at the bottom of the page. Refer to the [Roles](https://docs.nexthink.com/platform/user-guide/administration/account-management/roles) page to make sure you have the **Execute all remote actions** permission enabled for your role.
* Search for the *Get application crash details* remote action, select it, and click **Run on … devices**.
* Enter the name of the binary in the **Get application crash details** modal and click on the **Execute on … devices** button.

If you don’t see the *Get application crash details* remote action on the list, make sure it is configured for **Manual** triggering in the **General** tab of the remote action configuration page.&#x20;

Refer to the [Manage remote action](https://docs.nexthink.com/platform/user-guide/remote-actions/managing-remote-actions) documentation for more information.

</details>

The **Get application crash details** remote action may take a few minutes to process before the results appear in the **Crash details** section of this page.

When the data is available, you can filter execution crashes by **Crash exception code**, **Faulty application path**, **Faulty module path** and **Faulty module name**.

***

RELATED LINKS

* [Getting started with Diagnostics](https://docs.nexthink.com/platform/user-guide/alerts-and-diagnostics/getting-started-with-diagnostics)
* [Managing Remote Actions](https://docs.nexthink.com/platform/user-guide/remote-actions/managing-remote-actions)
* [Roles](https://docs.nexthink.com/platform/user-guide/administration/account-management/roles)
* [Product configuration](https://docs.nexthink.com/platform/user-guide/administration/system-configuration/product-configuration)