Wooting TWO HE occasionally acts up on reboot

[tired prism]

Hey uh I haven't faced anything like this before so not exactly sure how to describe it, but sometimes when I restart my PC, on reboot the rgb on keyboard doesn't work and it struggles to keep up with keystrokes (misses some inputs, also feels slow), opening wootility does show that it detects keyboard, changing profiles and stuff doesn't fix RGB or anything. It does thankfully fix itself after another boot. But what I'm worried about is, is it slowly going to get worse/happen more frequently?

[bitter swift]

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

• Cancel an order?
• Return/Refund an order?
• Get assistance with placing an order?
• Change the items in your order?
• Change your shipping address to a different country?
• Return a recent purchase?
• Get warranty support?

All of these types of requests need to be made via the Wooting Support Wizard!

[gritty lava]

I've had a similar issue and found I had too much power draw on my internal usbs I moved some stuff around to a powered usb hub and that fixed the issue

[tired prism]

I will give this a try 👍

[quasi pelican]

Also, RGB can be affected by 3rd party apps trying to take control of the keyboard.

[tired prism]

It is easy to look into those, but none of the other applications were affecting the RGB. (no such program is added to startup, and this issue occurs even before you sign in into your windows account/user). If the only problem was RGB, I wouldn't really mind it much, but some inputs not registering and it feeling very sluggish is something that can't really be ignored.

[quasi pelican]

Yeah sounds like some kind of power issue with your ports then. Are you using the stock cable plugged directly into the motherboard?

[tired prism]

Yes its the stock cable, but I am not sure if its the culprit since it does work fine most of the time, it's just restarting that can 'sometimes' cause that weird issue.

[quasi pelican]

Does it go back to normal after a bit when you’re experiencing problems? Wondering if it may just be that your cpu is struggling during boot

[tired prism]

No, not even the RGB came back on after waiting for 10ish mins(can't really keep on waiting for more as I do need the keyboard to work properly), and I have a hard time believing that its cpu struggling when everything else works perfectly. CPU is i7 13700KF btw.

[quasi pelican]

As someone who had 2 14900k cpus, it can still happen…mind you, my cpus nuked themselves. Maybe someone from wooting will be able to help out in the next day (they periodically check these threads).

[tired prism]

Not entirely sure what you mean by nuked themselves, I guess you didn't undercloak them/didn't get beefy enough liquid cooler/air flow issues and they slowly started to deteriorate and crash for most of the stuff? I do manage and monitor my components frequently and I haven't really had much issues with them, except this weird one with the keyboard rn.

[quasi pelican]

They did 14900k things. First one was due to bios issues (used to do a bunch of overclocking on a test bench before there were any reports of them dying and companies releasing new bios’s). RMA’d it and got another that was blue screening from day one. Just par for the course with Intel I guess 🤷🏻‍♂️. Using amd on both my builds now.

[tired prism]

Yeah Intel has had real quality issues with some previous gen CPUs and now even performance issues with latest ones. But I live in a country with pretty hot weather so I tend to undervolt and tiny bit ubderclock my CPU anyway to minimize temps/heat generation. That just worked out for me, considering how most of the ones that pushed for performance ended up having stability issues. I did plan on moving to 9800X3D + upgrade my 4080 on 9800X3D's launch but eh not that much of a justifiable purchase for me, considering the new Nvidia GPUs (except 5090) are lackluster too.

[quasi pelican]

Yeah, I’m in a place where it snows at least 8 months a year (just shy of 2000cm for the ‘24-25 winter season). The one I cranked to the max was actually more stable than the one I didn’t touch the bios settings at all on. Also, as someone who’s got 2 5090’s right now, they’re great. But there’s definitely diminishing returns with the cost. And with the absolutely obsurd cost of gpu’s currently, nothing is worth it. I’d just keep the 4080 until 60 series drops if I were you.

[tired prism]

Yeah I avoided 4090 pretty much only because it would heat up my room more than I would be comfortable with, even with air conditioning, 4090 and now 5090 are really good GPUs otherwise(though a bit less raw performance improvement as they focused on dlss4) so I'm pretty much going to have to wait for next 6080 for more VRAM and hopefully somewhat reasonable power consumption. Also congrats on getting 5090 considering the scalping situation.

[quasi pelican]

I used the hot stock app (at least available in the US) which can automatically purchase stuff for you. Got lucky on release week.

[green jungle]

Do you have Fast Boot on? There has been a few cases where that causes issues.

If not then maybe this could help. It doesn't sound exactly like the same issue but might be worth trying the test build #1354496567423271083 message