> For the complete documentation index, see [llms.txt](https://cookiebunker.gitbook.io/cookiebunker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cookiebunker.gitbook.io/cookiebunker/dma/4k-dc500-fuser/troubleshooting-and-indicators.md).

# Troubleshooting & Indicators

### **Indicator Lights (Front Panel)**

* **DC** → Monitor detected
* **RX0** → Host PC detected
* **RX1** → Secondary PC detected
* **RH** → Overlay enabled

{% hint style="info" %}
If a light is **off**, that signal is not detected.
{% endhint %}

***

### **On-Screen Info (Press K1)**

Shows:

* MAIN: Host resolution & Hz
* SECOND: Secondary resolution & Hz
* ALPHA: Overlay strength
* BD: Firmware date
* UID: Device ID
* EDID: Mode A or B
* SEC: Activation status

***

### **EDID Modes (Critical)**

* **Mode A (Default)** – Universal compatibility
* **Mode B** – Native display compatibility

If you get **no image**, switch to **Mode B**\
\&#xNAN;*(Long-press K1 for 5 seconds → auto reboot)*

***

### **Common Fixes (90% of Issues)**

#### **No Image but All Lights On**

1. Long-press **K3** (factory reset)
2. Power off everything → reconnect cables
3. Reset monitor to factory defaults
4. Switch EDID Mode (K1 long press)

#### **Black Screen When Launching Games**

* Disable **G-SYNC**
* Match in-game resolution to desktop
* Reset GPU control panel settings

#### **Repeating / Tiled Screen**

* Set **same resolution on both PCs**
* Switch EDID Mode
* Factory reset (K3)

#### **Artifacts / Image Shift**

* Factory reset (K3)
* Reboot fuser

***

#### Final Notes

* Always use **certified HDMI 2.1 FRL 48 Gbps or DP 1.4+ cables**
* Plug cables into the **GPU**, not motherboard ports
* When in doubt: **K3 long-press reset**


---

# 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://cookiebunker.gitbook.io/cookiebunker/dma/4k-dc500-fuser/troubleshooting-and-indicators.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.