I have a SGK3 Keyboard. Which is working just fine under Windows (and generic drivers) However when using the Keyboard under Linux certain, (internal) Macros, related to Keyboard-RGB will lead to Linux not receiving any more inputs from the Keyboard. Only thing i then can do is reconnect the keyboard by pulling it from usb and reconnecting it.

Sometimes i can press such a combo once or twice without any issues. But i always can reproduce it. However it doesn't happen on Windows no matter how hard i try or spam these Keys. So my guess is this is a linux exclusive issue.
I also tried a Linux-Live-USB to get sure it's wasn't just my distru. And it happens there as well.
Only the RGB-Hotkeys are affected, other Hotkeys like increasing Volume or opening Email don't have this issue. When pressing these RGB-Macros the Keyboard might "flicker" for a split second (Which is considered normal based on the Manual) so my guess is that there is some kind of fast disconnect/reconnect happening? Though dmesg doesn't report any disconnect.

I already tried disabling these hotkeys by modifying and disabling the scancode for these combos (all the RGB-Combos share the same Scancode for some reason) using a a90-custom-keyboard.hwdb though that didn't solve the issue. The USB Driver in use is xhci_hcd.
I already asked in some other forums yet it seems like nobody really knows a solution or how i could track down this issue. So i thought of asking here as well

Mainboard is a MSI b550 a Pro (lastest Uefi).

The keyboard depends on proprietary software on Windows to do programming and high-speed polling. It is quite likely using keycodes for communication that have no special meaning on Windows but are used by bash or X-Windows. Ctrl-S would be a good bet. You can use the showkey program on Linux to track down what codes are being sent by the keyboard, and maybe you can make a custom keyboard profile using xmodmap/XKeyCaps to mitigate any harmful effects. Probably simpler to just use a generic keyboard when using Linux.