How to Find and Read Log Files

When to Use Logs

Log files help you diagnose persistent issues when basic troubleshooting steps have not resolved the problem. The SignalRGB support team will often ask for your logs when you submit a bug report.

Logs record what the application was doing leading up to an error. They give the support team context that screenshots alone cannot provide.

---

Finding Log Files

Log files are stored at:

%LocalAppData%\WhirlwindFX\SignalRgb\Logs

Steps to navigate to the logs folder:

1. Press Win + R to open the Run dialog.
2. Type %LocalAppData%\WhirlwindFX\SignalRgb\Logs and press Enter.
3. The logs folder opens in File Explorer.

Tip

Sort by Date Modified (newest first) to find the most recent log. Look for files larger than 5 KB — very small files are usually empty or incomplete. Ignore any files ending in .old.

If the folder is empty or logs are not being written, try launching SignalRGB as Administrator.

---

Opening the Device Information Page

The Device Information page shows a snapshot of every device SignalRGB currently detects, including firmware versions, connection state, and driver details. This is one of the fastest ways to confirm whether a device is being recognized correctly.

Open the Device Information page directly from within SignalRGB:

signalrgb://app/view/debuginfo

Paste this link into your browser address bar or the Windows Run dialog (Win + R) while SignalRGB is running.

---

Enabling Verbose Logging

Standard logs may not capture enough detail for complex issues. Verbose logging records more activity and gives the support team a fuller picture.

1. Open SignalRGB.
2. Go to Settings > Application > Advanced.
3. Enable Verbose Logging or Debug Mode.
4. Reproduce your issue. Restart the app, trigger the bug, or repeat the steps that cause the problem.
5. Disable verbose logging after capturing the issue. Leaving it on can affect app performance.

Caution

Verbose logging increases log file size. Disable it once you have reproduced the issue to avoid unnecessary disk usage.

---

What to Include in a Bug Report

Providing the right information upfront speeds up the support process. Before submitting a report, gather the following:

• The most recent log file, sorted by date
• Any crash dump files (.dmp) found in the logs folder
• A screenshot of the Device Information page (signalrgb://app/view/debuginfo)
• Your device brand, model, and connection type (USB, PCIe, etc.)
• The steps you took to reproduce the issue

Note

Log files may contain your PC username and device names. Review the file before sharing if privacy is a concern.

---

Capturing a CPU Stack Trace

If SignalRGB is hanging or consuming unexpected CPU, a stack trace helps the team identify exactly which thread or operation is causing the problem.

Use Process Explorer (a free Microsoft Sysinternals tool):

1. Download Process Explorer from the Microsoft Sysinternals website.
2. Run Process Explorer as Administrator.
3. Locate SignalRgb.exe in the process list.
4. Right-click the process and select Properties.
5. Go to the Threads tab and click Stack on the thread using the most CPU.
6. Take a screenshot of the stack trace and include it in your bug report.