# Signal RGB closes when the CPU is under hevay load - i.e. stress testing/benchmarking **URL:** \ **Category:** Support\ **Created:** [September 12, 2026, 4:49pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113 "2026-09-12T16:49:14Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Chrimajon](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@Chrimajon](https://forum.signalrgb.com/u/Chrimajon)\ **Post date:** [September 12, 2026, 4:49pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/1 "2026-09-12T16:49:14Z")
As in the title, if the CPU is hitting 100% usage, Signal will usually close (not completely shut down), so the lighting goes off and more importantly, the fans slow down. ---
**Author:** ![Benny](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/benny/32/1893_2.png) [@Benny](https://forum.signalrgb.com/u/Benny)\ **Post date:** [September 12, 2026, 6:00pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/2 "2026-09-12T18:00:49Z")
We’ve got a few questions here, but also, we’d need to look at logs to see what’s up. The best way to for us to look into this is by sending us a bug report through the bug icon found on the upper right corner of the app. That way, we’ll have logs to look at and go from there. ---
**Author:** ![Chrimajon](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@Chrimajon](https://forum.signalrgb.com/u/Chrimajon)\ **Post date:** [September 12, 2026, 6:11pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/3 "2026-09-12T18:11:43Z")
Report submitted! Thanks for any help. ---
**Author:** ![Chrimajon](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@Chrimajon](https://forum.signalrgb.com/u/Chrimajon)\ **Post date:** [September 18, 2026, 6:56pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/4 "2026-09-18T18:56:02Z")
So much for the ‘support’ on software with a paid subscription. Thanks for nothing. ---
**Author:** ![Benny](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/benny/32/1893_2.png) [@Benny](https://forum.signalrgb.com/u/Benny)\ **Post date:** [September 19, 2026, 5:12pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/5 "2026-09-19T17:12:44Z")
Sorry for the wait, that’s frustrating, totally get it. We’ve been replying to submitted reports as they come in, but there’s a real backlog right now so some are taking longer to get to. Do you have your ticket number from that bug report? ---
**Author:** ![Chrimajon](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@Chrimajon](https://forum.signalrgb.com/u/Chrimajon)\ **Post date:** [September 20, 2026, 5:14pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/6 "2026-09-20T17:14:59Z")
No ticket number and if I was supposed to attach log files it didn’t give me any option to do so, but I can attach them to an email if needed ---
**Author:** ![Benny](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/benny/32/1893_2.png) [@Benny](https://forum.signalrgb.com/u/Benny)\ **Post date:** [September 20, 2026, 7:40pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/7 "2026-09-20T19:40:32Z")
Yes, it’s not supposed to since we’ll have all the logs and information about your setup if you sent the bug report through the bug icon found on the app. If you didn’t get a response from us, it’s likely that it didn’t go through since we’ve already answered all the new queries. Could you send us an email to [support@signalrgb.com](mailto:support@signalrgb.com) instead and we’ll see if that goes through? ---
**Author:** ![Chrimajon](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@Chrimajon](https://forum.signalrgb.com/u/Chrimajon)\ **Post date:** [September 25, 2026, 10:29am UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/8 "2026-09-25T10:29:31Z")
Any further response from you or are we done? Your crappy software is now shutting down randomly at any time. ---
**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\ **Post date:** [September 25, 2026, 2:08pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/9 "2026-09-25T14:08:51Z")
Did you end up sending that email through? Happy to follow-up on your ticket! You should get a ticket # in response. In the meantime, have you tried the beta? You can enable it under **Settings \> Updates**. For an issue like this we definitely would want to get more info than we can gather over a forum where we’re limited to ~500 characters per response. For example, we have no idea what your build is. ---
**Author:** ![Chrimajon](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@Chrimajon](https://forum.signalrgb.com/u/Chrimajon)\ **Post date:** [September 25, 2026, 8:36pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/10 "2026-09-25T20:36:12Z")
I sent the email. I can attach logs to an email if you want. ---
**Author:** ![Benny](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/benny/32/1893_2.png) [@Benny](https://forum.signalrgb.com/u/Benny)\ **Post date:** [September 26, 2026, 6:49pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/11 "2026-09-26T18:49:46Z")
Thanks for sending the email. We’ll respond to it within the day. If you haven’t heard from us at all, let us know here. ---
**Author:** ![Chrimajon](https://avatars.discourse-cdn.com/v4/letter/c/f08c70/32.png) [@Chrimajon](https://forum.signalrgb.com/u/Chrimajon)\ **Post date:** [September 26, 2026, 7:29pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/12 "2026-09-26T19:29:25Z")
We’re going round in circles. I won’t get an answer, I’ll reply saying ‘no response’ and you’ll say send an email. Hopeless. I’m better off dumping Signal and going for something else. Your tech support is atrocious. You still haven’t said " yes, please attach some logs, so we can see what’s going on". Tells me all I need to know. ---
**Author:** ![Benny](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/benny/32/1893_2.png) [@Benny](https://forum.signalrgb.com/u/Benny)\ **Post date:** [September 27, 2026, 5:19pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/13 "2026-09-27T17:19:39Z")
We’ve cleared out our email queue at this point, so if you sent that email to [support@signalrgb.com](mailto:support@signalrgb.com), you should have gotten a reply by now. If you haven’t heard back, that likely means it didn’t go through on our end. Could you try sending it again and let us know here once you have? We’ll keep an eye out for it. ---
**Author:** ![SignalBadger](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.signalrgb.com/signalbadger/32/1654_2.png) [@SignalBadger](https://forum.signalrgb.com/u/SignalBadger)\ **Post date:** [September 28, 2026, 3:43pm UTC](https://forum.signalrgb.com/t/signal-rgb-closes-when-the-cpu-is-under-hevay-load-i-e-stress-testing-benchmarking/10113/14 "2026-09-28T15:43:04Z")
There’s not really a good way to provide the complete log history over forums. What was your ticket #? As Benny said, we’re happy to follow-up and want to help you. With more info to work with, we can likely try some troubleshooting and escalate to the developers if we’re unable to resolve it with our steps. Here to help!