> 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-reference_material-list/000009036.md).

# Troubleshooting "Could not find a part of the path" errors on the NextSeq500/550 and MiniSeq

Users may encounter the following error during sequencing runs:

**Could not find a part of the path 'D:\Illumina\ImagingMemoryDump\SparkMiniDump.dmp'.**

**An error occurred while sequencing. Will now proceed to determining whether to perform a post-run wash. Originally caused by: Could not find a part of the path 'D:\Illumina\ImagingMemoryDump\SparkM...."**

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-2b0cf6444fa56fe3343a9c1b6a8b2243fdac3f2a%2Fimage1.png?alt=media)

This error results in the run stopping early and is non-recoverable.

Typically, this error is the result of a transient communication issue due to the Control Software being unable to access necessary files. Power cycling the instrument restores this connection and allows future runs to proceed without issue. There may also be an issue with the DMA Driver, so it is recommended to check the status of the DMA driver on the NextSeq 500/550 or MiniSeq as well.

**Troubleshooting steps:**

1. Check status of the DMA driver.
   1. See instructions in the Illumina Knowledge Article [Troubleshooting Bit Error on the NextSeq 500/550 and MiniSeq](/instrumentation/general/instrumentation-general-troubleshooting-list/000006684.md).
2. Power Cycle the instrument. Refer to the following instructions depending on the instrument:
   1. [How to Power Cycle the MiniSeq](/instrumentation/miniseq/instrumentation-miniseq-reference_material-list/000002010.md)
   2. [How to Power Cycle the NextSeq 500/550](/instrumentation/general/instrumentation-general-reference_material-list/000001972.md)

If after power cycling the Control sSoftware fails to initialize or the subsequent run fails with the same error, contact [Illumina Technical Support.](https://www.illumina.com/company/contact-us.html#/united-states/technical-support)

\
\
\ <br>

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