> For the complete documentation index, see [llms.txt](https://docs.signcod.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.signcod.com/sign/english/basics/common-issues/blue-screen-of-death.md).

# Blue Screen

Use the repair steps for BSOD issues.

<mark style="color:$primary;">**SIGN · GUIDE**</mark>

This page collects the repair-file steps for blue screen issues when running our software.

## Repair steps <a href="#steps" id="steps"></a>

{% stepper %}
{% step %}

### Download the repair files

<a href="https://mega.nz/folder/3t9S3ZzJ#KHCfhqRxm-3wBdZogGIbdw" class="button secondary" data-icon="download">Download BSOD repair files</a>
{% endstep %}

{% step %}

### Run each file as administrator

Right-click the file and select **Run as administrator**.
{% endstep %}

{% step %}

### Confirm when prompted

If the repair files ask you to confirm or overwrite files, press `Y`.
{% endstep %}

{% step %}

### Restart your PC

After both files finish, restart your computer to apply the changes.
{% endstep %}
{% endstepper %}

## Need a hand? <a href="#support" id="support"></a>

<mark style="color:$secondary;">**SIGN SUPPORT**</mark>

The Sign team is here to help. Open a Discord ticket and include the page name, the step you reached, and a screenshot of the issue so we can help you more clearly.

<a href="https://discord.gg/siin" class="button primary" data-icon="discord">Get help on Discord</a> <a href="https://www.signcod.com/ar" class="button secondary" data-icon="globe">Visit Sign Website</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.signcod.com/sign/english/basics/common-issues/blue-screen-of-death.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.