> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000006676.md).

# Troubleshooting "Instrument Shell has Stopped Working" on the NovaSeq 6000

The "Instrument Shell has Stopped Working" error on the NovaSeq 6000 is a Windows error that can indicate transient communications issues or hardware problems. This error manifests as the NovaSeq Control Software (NVCS) crashing, and the pop-up shown below appearing on the screen.

*"Instrument Shell has stopped working. A problem caused the program to stop working correctly. Please close the program."*

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-7e327800e6f3d51b43a8a527e7aa4046c29b660c%2Fimage1.jpg?alt=media\&token=29347d77-e6e6-4cc4-89e6-ab571372af2b)

**Troubleshooting:**

1. Select **Close the program** from the options shown in the pop-up window.
2. Power cycle the instrument.
   1. For further information, see Knowledge Base article [How to Power Cycle the NovaSeq 6000.](/instrumentation/general/instrumentation-general-reference_material-list/000002470.md)
3. Attempt to restart NVCS.
4. If initialization fails or same error recurs, collectthe following log files:
   * NovaSeq Control Software logs folder: C:\ProgramData\*\Illumina\NovaSeq\NovaSeq Control Software\Logs (zipped)
5. After collecting the logs, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support) to assist with the next steps.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6676), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006676%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# 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://knowledge.illumina.com/instrumentation/novaseq-6000/instrumentation-novaseq-6000-troubleshooting-list/000006676.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.
