> 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/general/instrumentation-general-troubleshooting-list/000006684.md).

# Troubleshooting Bit Error on the NextSeq 500/550 and MiniSeq

* The following error occurs when launching the Control Software or during the pre-run check of the imaging system on the NextSeq 500/550 or MiniSeq.
* This error can result from a transient communication issue or an issue with the optical system.
* Typically the error can be resolved by power cycling the instrument.
* **Note**: Bit rate error is resolved in instruments upgraded to NextSeq 500/550 Control Software (NCS) v4.0.1.

**Error Language**: Bit error check failed Originally caused by: DMA Read failed with return code 32. ![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-1167f64d687febeedca7895d277d3f4458cd6d54%2Fimage1.jpg?alt=media\&token=4509743a-2550-4a24-9545-98f2ff072c68)

**Figure 1.** "Bit error check failed Originally caused by: DMA Read failed with return code 32"

**Troubleshooting steps:**

1. Open **Control Panel** → **Device Manager** and verify *Illumina DMA Driver* under Data Acquisition is loaded or not.
   * If *Illumina DMA Driver* is present, power cycle the instrument once and restart the run.
   * If *Illumina DMA Driver* is **NOT** present, power cycle the instrument once. Login to **sbsadmin** and open the **Control Panel** → **Device Manager** to verify if *Illumina DMA Driver* under Data Acquisition is now loaded or not. If *Illumina DMA Driver* is present now, restart the run.
2. If *Illumina DMA Driver* is still **NOT** present, power cycle the instrument a second time. Login to **sbsadmin**, and open the **Control Panel** → **Device Manager** to check if *Illumina DMA Driver* under Data Acquisition is now loaded or not. Note that sometimes the second power cycle is required.
   * If *Illumina DMA Driver* is present now, restart the run.
   * If *Illumina DMA Driver* is still **NOT** present, contact [Illumina Technical Support](https://www.illumina.com/company/contact-us.html#/united-states/technical-support).

**To power cycle the instrument:**

1. From the home screen, select **Manage Instrument**.
2. Select **System Shutdown Options**.
3. Select **Shutdown** to close the control software and turn off the instrument.
4. When the instrument is off, wait 3-5 minutes and turn the instrument back on by pressing the power button in the front.
5. Allow the control software initialize.

**Additional resources:**

* [NextSeq 500 and NextSeq 550 Sequencing System Guide](https://sapac.support.illumina.com/downloads/nextseq-500-550-systems-product-documentation.html)
* [MiniSeq System Guide](https://support.illumina.com/downloads/miniseq-system-guide-1000000002695.html)
* For further information, search for Knowledge Base article [How to Power Cycle the NextSeq 500/550](https://knowledge.illumina.com/instrumentation/general/instrumentation-general-reference_material-list/000001972.md) or [How to Power Cycle the MiniSeq.](https://knowledge.illumina.com/instrumentation/miniseq/instrumentation-miniseq-reference_material-list/000002010.md)

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #6684), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000006684%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/general/instrumentation-general-troubleshooting-list/000006684.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.
