> For the complete documentation index, see [llms.txt](https://help.sbtinstruments.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sbtinstruments.com/troubleshooting/other-problems.md).

# Other problems

Problems that come without an error code.

Find what you see.

* [Does not power on](/troubleshooting/other-problems/does-not-power-on.md). The display stays dark when you switch on.
* [Display is frozen or dark](/troubleshooting/other-problems/display-is-frozen-or-dark.md). Your BactoBox® was running, then froze or went dark.
* [Stuck at spinner](/troubleshooting/other-problems/stuck-at-spinner.md). The screen says *Initializing* or *Stopping* and does not move on.
* [Program could not run to completion](/troubleshooting/other-problems/program-could-not-run-to-completion.md). A program stops with this message.
* [Flow cell does not work](/troubleshooting/other-problems/flow-cell-does-not-work.md). The screen says the flow cell is invalid, obsolete, depleted or removed.
* [Cannot connect to Access](/troubleshooting/other-problems/cannot-connect-to-access.md). Access does not open in your browser.
* [Software update failed](/troubleshooting/other-problems/software-update-failed.md). The update stops with a message.
* [The clock is wrong](/troubleshooting/other-problems/the-clock-is-wrong.md). The time is wrong, or your BactoBox® forgets it.
* [Dilution dispenser is stuck](/troubleshooting/other-problems/dilution-dispenser-is-stuck.md). The piston does not move.
* [Dilution liquid test fails](/troubleshooting/other-problems/dilution-liquid-test-fails.md). Your blank dilution liquid reads above the limits.

Got an error code? See [Error codes](/troubleshooting/error-codes.md).


---

# 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.sbtinstruments.com/troubleshooting/other-problems.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.