Keyboard is unresponsive only in comp

Technical Support
1

At first I thought it was an issue with my keyboard, but now I’m not so sure. I see that there are threads about this issue in other forums like reddit as well, going back a few years. This issue happens sporadically. I will always be in the middle of a comp match, then my keyboard will not respond to any input. My character would then be stuck moving forward. My mouse still works and I can pivot my character to run in a straight line in any other direction but, always straight. No keys work, even ctrl + alt + del does not. Unplugging and re-plugging doesn’t work. I have to completely reboot my computer. I’ve tried: unplugging and re-plugging, re-plugging in a different port, new keyboard in a different port, new keyboard in old port, updated chipset for motherboard, checked drivers for the keyboard, checked for any errors, made sure Windows energy saving is off, even checked that Windows sticky is off. None has worked. There was one time, very recently and not when this issue started, where I saw my profile was corrupted, but it made my keyboard act in a different way, it was more of delayed reaction than unresponsiveness altogether. I also rectified this error by repairing the corrupted files. I have been banned so many times because even if I come back to the match and finish it, I technically left. I know people will ask why did I continue playing if there’s a problem? Well, sometimes it happens once a day and then for days nothing. In fact, this barely popped up maybe a few months ago, again, spontaneously and without cause or reason. It also only happens in COMP, never in QP (or maybe I just haven’t played the same amount of time in QP to check). When I get banned for these keyboard unresponsiveness, I go to play QP and not a single issue. I can’t recreate this issue elsewhere. I play many games and this doesn’t and never has happened there, even if I play another game right after my keyboard goes unresponsive in Overwatch2! What can this be? I don’t get it. I am so frustrated and there is no end in sight. The only solution I have is to never play Overwatch2.

I don’t know what to give to maybe provide insight to what maybe causing my issue so please forgive me if I’m listing useless info but I have:
NVIDIA GeForce RTX4090
ASUS Prime Z790 -A Wifi motherboard
13th Gen Intel Core i9 13900k
32G of RAM
1tb of Samsung SSD
CORSAIR - K70 RGB MK. 2 SE RAPIDFIRE keyboard
Logitech G Pro X Superlight Wireless Gaming mouse

2

Sounds like your keyboard drivers stop working in the middle of the match. Have you reached out to Corsair at all?

3

No, I have not. I didn’t think to reach out to Corsair as when it kept happening, I decided to use another keyboard my Logitech G910. The same issue occurs even if I plug in the G910 to a different port/s. I’ve also checked that there is no updates to any drivers, Windows updates or any other necessary files. This happens exclusively in Overwatch, nowhere else.

4

The game software doesn’t have system permissions to turn off USB power to your keyboard.

I checked a few Reddit threads about keyboards turning off mid-game and it’s not exclusive to any particular developer, but it’s almost always a driver or power issue.

Is Windows is turning off the device to save power?
Device Manager → Expand Keyboards → right-click Keyboard and select Properties → Power Management tab → Uncheck “Allow the computer to turn off this device to save power” → click OK

There is a power issue with your CPU that Intel acknowledged.

5

Run a input recorder and u will find that often in Overwatch the game is just not responding while input is indeed being send.

6

All that would prove is that your computer isn’t processing the input through the board to the onboard storage, or that the storage is slow.

7

But that makes no sense since my USB extension bypasses the chipset and goes straight for the CPU? The input is already processed by the CPU, if the software which records the input shows the correct input but the game has not responded to the input then it’s obviously not a hardware issue.

I should have said input received instead of send.

8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.