# Workflow: System crash troubleshooting

## Problem <a href="#problem" id="problem"></a>

You can only troubleshoot system crashes after they have happened, requiring proactive investigations or submitting a ticket. In any case, this disrupts your service desk team as they must reach out to affected devices and/or manually open tickets to diagnose the underlying cause. These manual troubleshooting scenarios tend to be quite simple and repetitive as with simple and common fixes, but they still cost you time.

## Solution <a href="#solution" id="solution"></a>

Orchestrate the troubleshooting of system crashes with a real-time workflow triggered after any system crash. The workflow will automatically notify the owner of the affected device, check and update any pending drivers, and open and close a ServiceNow ticket. The system crash error code will be automatically retrieved and parsed through chatGPT to add the root cause and additional troubleshooting context inside the ticket as a worknote.

## **Expected value** <a href="#expected-value" id="expected-value"></a>

This fully hands-off system crash troubleshooting workflow will:

* Reduce employee frustration related to a system crash by automating the incident report for them
* Save service desk time by reducing manual troubleshooting and automating ticket management
* Prevent future tickets by automating a fix or providing the proper root cause to investigate for service desk teams.

## Get started <a href="#get-started" id="get-started"></a>

Configure and start using your packs by following these links:

| [Configuration guide: System crash troubleshooting](/platform/library-packs/l1-support/workflow_-system-crash-troubleshooting/configuration-guide_-system-crash-troubleshooting.md) |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Usage guide: System crash troubleshooting](/platform/library-packs/l1-support/workflow_-system-crash-troubleshooting/usage-guide_-system-crash-troubleshooting.md)                 |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nexthink.com/platform/library-packs/l1-support/workflow_-system-crash-troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.