> 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/iseq-100/instrumentation-iseq-100-troubleshooting-list/000007019.md).

# Troubleshooting Black Chromium Screen on the iSeq 100

When users open Chromium on the iSeq 100 and find the window is entirely black, sometimes users may be able to type in the address bar, but the window itself will not change, even when refreshed. This may result from a communications issue on the instrument or a side-effect of hardware acceleration in Google Chromium.

**To troubleshoot this issue:**

1. Power Cycle the instrument as described in the **Knowledge Base article Power Cycling the iSeq 100**. Reopen Chromium once the instrument re-initializes.
2. Turn off Hardware Acceleration in Chromium as follows:
   1. Create a Google Chromium shortcut on theDesktop
   2. Right-click the shortcut, and select **Properties**.
   3. Select **Shortcuts** tab.
   4. In the Target window, add the following text: "\[space]-disable-gpu" (the path should look like chrome.exe” -disable-gpu”).
   5. Save changes.
   6. Open Chrome and select **Settings** > **Show advanced settings**.
   7. Disable the **Use hardware acceleration when available** option.

If these steps do not re-establish Chromium's normal function, contact [Illumina Technical Support](https://support.illumina.com/).

\
\
\ <br>

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