> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-shutdown-codes.md).

# Shutdown codes

Reference Controller 6000 shutdown codes and their causes.

Looking through a controller's **error log** (using the web browser to connect, see [Testing Controller Connections](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-testing-controller-connections.md)), every time a controller shuts down there is an **`SC` descriptor with a number**.

These codes can also be seen in **alarm messages in Command Centre** after a controller restarts.

***

## Shutdown code reference

| Shutdown Code | Meaning                    | Fault or Normal            | Likely Cause                                     |
| ------------- | -------------------------- | -------------------------- | ------------------------------------------------ |
| 0             | Normal Termination (debug) | Normal                     | —                                                |
| 1             | Remote Reset Request       | Normal                     | Reset request after doing a code download        |
| 2             | Power Fail                 | Normal                     | Power has failed                                 |
| 3             | Hardware watchdog timeout  | Software or hardware fault | S/W or H/W fault                                 |
| 4             | Startup Failed             | Software fault             | Corrupt version of controller S/W                |
| 5             | Configuration Failed       | Fault                      | Invalid configuration                            |
| 6             | Out of Memory              | Fault                      | S/W bug, or just too much going on               |
| 7             | Assertion                  | Fault                      | S/W bug, should only occur in debug versions     |
| 8             | RAM error                  | Hardware fault             | Faulty RAM chip                                  |
| 9             | Code checksum error        | Fault                      | Controller code has been corrupted               |
| 10            | FTP server running         | Normal                     | Controller was started with the `/FTP` parameter |
| 11            | Uncaught exception         | Software fault             | Depends on the exception                         |
| 12            | Caught exception           | Software fault             | Depends on the exception                         |
| 255           | Undefined Fault            | Fault                      | Almost anything                                  |

***

🔗 **Related**

* [Run LED and DIP Switches](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-run-led-and-dip-switches.md). Reading the Run LED flash patterns.
* [Testing Controller Connections](/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-testing-controller-connections.md). Reading the controller error log.


---

# 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://help.security.gallagher.com/knowledge-hub/products/cc-hardware/controllers/controller-6000/troubleshoot/controller-6000-shutdown-codes.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.