My Gravastar keyboard suddenly stopped working correctly after a recent setup change, and now some keys are unresponsive and the lighting acts weird. I’ve tried reconnecting it and checking basic settings, but nothing has fixed it. I need help figuring out whether this is a driver, firmware, or hardware issue so I can get it working again.
Start with the boring stuff.
- Unplug the keyboard.
- Try a different USB port, direct to the PC, no hub.
- Try a different cable if it uses USB-C. A bad cable will cause dead keys and broken RGB at the same time.
- Test it on another PC. This tells you fast if the board is the problem or your setup.
If it started right after a setup change, check these next.
- Remove any keyboard software you installed or updated. Gravastar app, RGB tools, remap tools, VIA, AutoHotkey, stuff like that.
- Reboot.
- Factory reset the keyboard. The exact combo depends on model, so check the manual or product page. A lot of boards use Fn plus Esc, or hold Esc while plugging in.
- If Gravastar has firmware software, reflash the firmware. Corrupt firmware often shows up as random dead keys, weird lighting, and the board half-working.
Also open Device Manager.
9. Remove the keyboard device.
10. Unplug it.
11. Reboot.
12. Plug it back in and let Windows reinstall it.
If only some keys fail, look for:
13. Wrong layout or layer stuck on, Fn layer, Mac mode, game mode.
14. Switches not seated right, if it is hotswap.
15. Liquid or static damage, if the timing was bad and the setup change was a coincidence.
Fast test:
Use an online keyboard tester. Press every key. If dead keys stay dead on two different PCs, it is the board or firmware, not Windows.
If you post the exact Gravastar model and what ‘setup change’ means, new software, new desk, KVM, dock, BIOS setting, I can narrow it down more. Right now my money is on cable, firmware, or a stuck layer.
I’d add one angle @vrijheidsvogel didn’t really dig into: power and signal weirdness from the new setup itself.
If you moved to a dock, KVM, monitor USB port, front panel USB, or added a bunch of RGB stuff, that can absolutely make a keyboard go half-crazy. People assume “it lights up, so it has power,” but flaky power/data can still cause missed keys and bugged RGB. I actually disagree a little with the idea that dead keys automatically means firmware first. Sometimes it’s just a garbage USB path.
A few extra things to check:
- Turn off USB selective suspend in Windows power settings
- In Device Manager, for every USB Root Hub, uncheck “allow the computer to turn off this device”
- If you’re using a KVM/dock, bypass it completely for a while
- Try a powered USB hub only as a test, weirdly enough this fixes some boards
- Check if the keyboard is showing up as multiple HID devices and one is erroring out
- Boot into BIOS and test there. If keys act weird even in BIOS, it’s not your normal Windows setup
Also, if the lighting changes when pressing certain keys, that smells like a layer/profile issue or onboard memory corruption. If the unresponsive keys are clustered in one area, that points more to PCB/socket trouble than software.
One more dumb-but-real thing: if this board has per-key remap/macros stored onboard, software uninstalling won’t always clear it. You have to wipe onboard profiles too. That part gets missed a lot.
Post the exact model plus what the “setup change” was, bc that’s probly the whole story.