> 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-x-x-plus/instrumentation-novaseq-x-x-plus-troubleshooting-list/000008271.md).

# How to troubleshoot "The instrument encountered a thermal coolant error" on the NovaSeq X Series

**Background** The NovaSeq X and X Plus Series of instruments utilize several coolant loops to ensure normal thermal operation of the instrument. Issues with any of these Thermal Loops will typically present as Critical system errors that prevent or stop sequencing runs to ensure the instrument does not become damaged. These issues typically present with the following error message:\
\*\* ![](/files/OThsU8uwXU1hUeLBugPc)\
\*\*

"Critical System Error: The instrument encountered a thermal coolant error. Please shutdown the instrument and contact Illumina Technical Support".

**Troubleshooting Actions**

1. Contrary to the error statement, **do not** immediately power cycle the instrument.
2. Collect the following Logs depending on error context:
   1. If during a sequencing run, collect the following files:
      1. The Logs.zip file from the /usr/local/illumina/runs/\[RunID]/Logs directory
      2. The entire InstrumentAnalyticsLogs folder in the /usr/local/illumina/runs/\[RUN\_ID] directory
   2. If during initialization or instrument idle, collect the following files:
      1. The entire `novaseq-x-series-control-software` folder in the /usr/local/illumina/logs directory
      2. The entire non\_run folder in the /usr/local/illumina/performance\_analytics\_data/ directory
3. Contact [Illumina Tech Support](https://www.illumina.com/company/contact-us.html) for next steps to troubleshoot this issue.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #8271), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000008271%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 dynamically by asking a question.

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

```
GET https://knowledge.illumina.com/instrumentation/novaseq-x-x-plus/instrumentation-novaseq-x-x-plus-troubleshooting-list/000008271.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
