Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
check for software update for the rgb controller on the mouse
Probably not. See most software like that uses system level drivers or lower and that means that the writers of the software have to have it play nice with other software that exists there, including anticheats.
Now, think about this...how many people use that software and hardware that utilises it, and how profitable is it?
In most cases the software isn't profitable and is added as an afterthought to push sales up that are already on a margin. That means that development isn't a priority, and when development isn't a priority, it means that testing isn't either.
And if you work in the system space and code is buggy, then you can expect freezing/crashing to happen often from literally any interaction between said software and the system or another component.
You can report it to the software writer, but I doubt they will care. Here;s an example of a nother piece of bad low level software: armoury crate. Really bad and has been for years. Can't go a day on MSDN without seeing someone crashing and freezing up because of it, and yet it's never been fixed. And that was by a motherboard manufacturer that sells millions of motherboards a year.
If they won't fix it, don't think anyone else will fix similar software...
if the op is mining or has mining malware maybe, but even then, the gpu will throttle when overheating, not locking up the system
@op
is anything in windows logs