Keys Acting as if Stuck During Games

[dippydoop]

*Edit* This problem has been solved- the issue was caused by the modified registry settings for keyboard response, resetting them to their default values solved the strange input behaviour.
The default registry values are as follows:
AutoRepeatDelay: 1000
AutoRepeatRate: 500
BounceTime: 0
DelayBeforeAcceptance: 1000
Flags: 126

*********​

Hi, hopefully someone here can help, I've tried searching, but I can't seem to word it without getting a load of unrelated problems.

The problem is that I'll be playing a game (any game, it seems) and, seemingly randomly, when I release a key, it behaves as if I'm still holding the key down. I can "fix" it by pressing and releasing the problem key again, but it can be REALLY inconvenient if, for example, I'm stuck running forward like this! Any key can be affected, and it ONLY seems to be in games. The keys aren't physically sticking.

I can't be sure, but I *think* this problem started roughly when i changed my video card from a GTX 570 to an R9 280X, then back to the GTX 570 (the 280X was faulty). Each time i switched the card, I used DriverSweeper to clean the previous vendor's drivers.

I also changed to some registry entries to counter some switch bounce I was experiencing, though I don't think this caused the problem. The changes I made: HKEY_CURRENT_USER\Control Panel\Accessibility\Keyboard Response
AutoRepeatDelay: 350
AutoRepeatRate: 10
BounceTime: 30
DelayBeforeAcceptance: 0
Flags: 59

Some system info, If it helps:
OS: Windows 7 64 bit
Motherboard: Asus p6t Deluxe v1 (flashed to latest BIOS)
CPU: Intel Core i7 i920 C0 Stepping
Memory: 6GB (3x2GB)
GPU: GTX 570
PSU: Thermaltake Toughpower 850W
Storage: Intel x-25m 80GB (Boot) + Samsung Spinpoint F1 1TB
Sound Card: Asus Xonar Essence ST
Keyboard: Filco Majestouch v1 (using PS/2 connection)

Any help/insight would be much appreciated, hope this wasn't too much to read!

 

[Virgorising]

Have you tried hooking up another KB? Esp a USB KB?

I only just learned these KBs are considered the finest of Blue Switch KBs and cost a ton....so better someone familiar with them and their complexities might arrive.

Re KBs, I am a cheap date, cept I only use the lower end Cherrys (membrane) made in Germany.

I found an esoteric forum you may want to explore:

http://forums.vr-zone.com/hardware-...eyboard-club-guide-discussion-thread-916.html
___________________________________________
You can rule out drivers, or nail them as the culprit, by uninstalling those for yr working card and starting afresh, as opposed to relying on a third party app.

 

[dippydoop]

Sorry it took me a while to reply, I had to borrow someone's keyboard, and then test with it (wow, membranes feel AWFUL now!). Anyway, I was able to re-create the same behavior with this USB keyboard as well. I also tried my Filco with USB (forgoing the use of the PS/2 adapter) and the issue remains.

It's strange, I've had this keyboard for about 3 years, and the problem only started within the past few months. Like I mentioned in the first post, it *seemed* to start when I swapped my graphics card out, but I can't understand how that would influence the behaviour of my input, especially with clean driver installs.

I've actually got MX Browns in this keyboard, from my own research Blues are great for typing, but might not be so great in games where you might double-tap keys. Also, Browns are quieter, which was a big plus for me. As long as you're happy with what you've got, that's all that matters, membrane keyboards tend to be cheaper, which is a plus. I REALLY wasn't looking forward to replacing this thing!

Thanks for the forum link, I'll have a look around. Do you think it's worth me starting a thread there, even though it doesn't seem to be a fault with the keyboard now?

 

[Virgorising]

Sorry it took me a while to reply, I had to borrow someone's keyboard, and then test with it (wow, membranes feel AWFUL now!). Anyway, I was able to re-create the same behavior with this USB keyboard as well. I also tried my Filco with USB (forgoing the use of the PS/2 adapter) and the issue remains.

Nothing to apologize for!! Given I have never used beyond Cherry membrane KBs.....I think I don know what I am missing. But, I am happy with my Cherry membranes.

Good you did the test with the other KB.

Someone with more savvy in this esoteric stuff needs to weigh in, but to me, this still sounds like a drivers issue of some kind.

No WAY would I even think of replacing the KB. More delving is justified, esp given the results of your having tested the membrane KB.

Thanks for the forum link, I'll have a look around. Do you think it's worth me starting a thread there, even though it doesn't seem to be a fault with the keyboard now?

Now, not sure, but maybe not, given, as you say, you got the same result with the USB membrane KB.

 

[Virgorising]

Please identify yr CPU for us. I don't C it in the specs you shared. I am sitll unclear re if you can use integrated graphics.

 

[dippydoop]

I've filled my spec list out some more. My CPU is an old i7 i920, so no integrated graphics for me. If it helps, I've had the GTX 570 since not long after they were released, and I'm running the latest drivers.

I'm not sure its a driver issue, since it manifests on both USB and PS/2 connections. Plus, I haven't done anything to change the state of my keyboard drivers, as far as I'm aware. I'm really puzzled as to why this would just happen, and I can't shake the feeling that the problem started with that AMD card.

 

[Virgorising]

I've filled my spec list out some more. My CPU is an old i7 i920, so no integrated graphics for me.

Thanks for this; no need to defend that chip, the system I am now right now has the i7 870.....I just needed to know if you could test using integrated graphics and we now know you can't.

I'm not sure its a driver issue, since it manifests on both USB and PS/2 connections. Plus, I haven't done anything to change the state of my keyboard drivers, as far as I'm aware. I'm really puzzled as to why this would just happen, and I can't shake the feeling that the problem started with that AMD card.

I did not mean KB drivers.

 

[dippydoop]

Are you thinking video drivers? I could try another fresh install. Do you know of any reputable alternatives to Driver Sweeper? Perhaps that one missed something.

I remember this issue cropping up when I was running the 280X, along with artifacting. I don't trust my memory to say for sure whether or not it happened before installing that card, but I can't seem to remember it happening.

A bit more subjective info on the problem: It seems to happen when I'm pressing multiple keys at once; I'd also say it seems to be happening less now that I've switched to using USB, but its hard to say, sometimes I can go hours without it happening, other times, its minutes.

 

[Virgorising]

What are your settings for yr chip in the bios?

Ar all yr cores unlocked?

Can you share yr temps? What does yr GPU run at under load while gaming?

AND, it is even possible you have oveclocked yr chip to the point of creating instability. I know nothing about the stepping chips, but to me, that feels possible.

And, re your RAM, pls share the specifics. And the speed of yr sticks.

 

[Virgorising]

One more: I think I just found yr board. It appears to support 24GBs of RAM, preferably in matched pairs of sticks as usual. Given you are a gamer, I am not understanding why you have only 6GBs installed.

Please say.

If I have the right board, you have 6 slots and the board can accept 4GB sticks.

You have this powerful PSU, a CPU overclocked to the max (I think), and this demanding GPU...... and 6GBs of DDR3?:\
_____________________________________________
CORRECTION! Your board wants matched GROUPS of THREE STICKS. So what you have is proper configuration, but very possibly INADEQUATE.

(Forgive me, I am not having a good day.)

 

[Matt1970]

I have to ask. Did you actually unplug the original keyboard when you tried another keyboard?

 

[dippydoop]

In answer to Matt1970:
Yes, I unplugged the original keyboard, and used a different USB port for the test keyboard, I wanted to try to isolate the old keyboard as much as possible, though I wasn't sure if it was really necessary.

To Virgorising's questions:
I've tried running at completely stock settings, but was able to reproduce the issue. I run overclocked pretty much all the time at a fairly conservative 176 MHz base clock, which works out to nearly 3.7 GHz with a 21x multi. I have all cores enabled, including HT. Voltage is 1.25V, which is stable under Prime95 for at least 4 hours (I never leave my PC on overnight).
Temps (with OC): CPU: Not over 70C with Prime95... GPU (stock speed): 70-85C. The issue occurs on less demanding games, too.

RAM: Corsair Dominator (matched triple DIMMs), rated 1600MHz @ 8-8-8-24 latencies. With my OC settings, its running just over 1400MHz, I run it at the standard latencies and a T1 command rate.
Actually, its best to use memory in triplets for this platform, since the memory controller supports triple channel memory.
Don't forget, when Bloomfield came out, DDR3 was still pretty expensive! That memory cost nearly as much as the CPU itself, I'm glad I didn't skimp and go for 3x1GB for sure, though.

I *think* I covered everything there, if I missed anything, feel free to shout out. If you want, I can go into the BIOS and write every setting down.

Edit- just noticed the edit on your post, sorry about the lecture on triple channel memory. By inadequate, do you mean not enough? As far as I'm aware, my RAM has been big enough. VRAM on the other hand... 1.28GB is starting to get restrictive.

 

[Virgorising]

To Virgorising's questions: I've tried running at completely stock settings, but was able to reproduce the issue. I run overclocked pretty much all the time at a fairly conservative 176 MHz base clock, which works out to nearly 3.7 GHz with a 21x multi. I have all cores enabled, including HT. Voltage is 1.25V, which is stable under Prime95 for at least 4 hours (I never leave my PC on overnight). Temps (with OC): CPU: Not over 70C with Prime95... GPU (stock speed): 70-85C. The issue occurs on less demanding games, too.

Many thanks for these data. U mean yr GPU sometimes runs at 85 at IDLE? AND cpu AT 70c AT IDLE????

Actually, its best to use memory in triplets for this platform, since the memory controller supports triple channel memory. Don't forget, when Bloomfield came out, DDR3 was still pretty expensive!

Yes, re the triplets for that board, I learned that and posted a correction. But, the system I am on employs more garden variety, affordable DDR3 (dual channel), and I bought brand new good upgrade sticks to total bring system up to 8GBs even before the system arrived...on eBay, and got an amazing deal there. (My board needs sticks installed in pairs and I have only 4 slots.)

And when I got mine, the prices were good. Might you consider upgrading yr RAM?

K, just saw you caught that I had to learn about re yr triplets. I never had a board that wanted triplets.

I am stuck. But also now in doubt about yr temps! Again, did U mean under load or at idle?

Please, others weigh in!!!!!

 

[dippydoop]

Ah! I should have worded it less ambiguously. Those temps are under load. The CPU doesn't go over 70C while running an 8 thread Prime95.
The GPU ,at load, depends on the game. 70's usually for less demanding games, 85 seems to be the highest I can get it with intense games.

As for upgrading memory- I'm really not sure at the moment. Triple channel sets are getting tough to find, and the ones I can find have higher latencies than my current RAM. I could get 3x4GB for just over £100, but I'd rather think about investing in a new CPU/motherboard/RAM, than put that kinda money down for an aging system.

Oh! Just remembered, I have a sound card, will add it to the spec list. It's an Asus Xonar Essence ST (PCI).

 

[Virgorising]

Ah! I should have worded it less ambiguously. Those temps are under load. The CPU doesn't go over 70C while running an 8 thread Prime95.

You word things meticulously, so stop it. And thanks for this, I think we can now rule out overheating as the cause of yr issue.

As for upgrading memory- I'm really not sure at the moment. Triple channel sets are getting tough to find, and the ones I can find have higher latencies than my current RAM. I could get 3x4GB for just over £100, but I'd rather think about investing in a new CPU/motherboard/RAM, than put that kinda money down for an aging system.

Wow. I had no clue it would be that much! I understand the dilema.

 

[Virgorising]

Where are you dippdoop?

I was thinking about this, and if possible, I would try to reverse the changes you made to keys values you made in the Registry.

 

[dippydoop]

Sorry, sometimes I find it can help if I take a step back from a problem for a few days, might help with finding a new approach.

I'll revert the changes in my registry, and see if that works (I'll be sure to restart immediately after the changes have been made).
For completeness, the reverted registry values are:
AutoRepeatDelay: 1000
AutoRepeatRate: 500
BounceTime: 0
DelayBeforeAcceptance: 1000
Flags: 126

 

[BrightCandle]

Since it happens on different keyboards that isolates the problem to being software. That would point to it being an unintended consequence of the registry key changes you made. That strikes me as by far the most likely culprit.

 

[Virgorising]

Since it happens on different keyboards that isolates the problem to being software. That would point to it being an unintended consequence of the registry key changes you made. That strikes me as by far the most likely culprit.

Exactly wut I thought. He said above, he was going to reverse the changes he made. My challenge would be remembering the original values.

Good to write stuff down when we change values. Cept I nerver do.

 

[Virgorising]

Sorry, sometimes I find it can help if I take a step back from a problem for a few days, might help with finding a new approach.

I'll revert the changes in my registry, and see if that works (I'll be sure to restart immediately after the changes have been made).
For completeness, the reverted registry values are:
AutoRepeatDelay: 1000
AutoRepeatRate: 500
BounceTime: 0
DelayBeforeAcceptance: 1000
Flags: 59

Excellent. We will await yr report.()

 

[dippydoop]

Thanks for the extra input, BrightCandle, and obviously Virgorising. I had initially ruled out the registry edits as being the cause of the problem as I thought I applied said changes much earlier than the problem started occurring, perhaps that was a mistake, especially with my memory being what it is!

It will take a while for me to test this properly- I can't start the problem on demand, and I want to be reasonably sure before I say "yes, the problem is solved".

I'm wondering if the culprit was setting the "delaybeforeacceptance" to 0. Perhaps if I set it to even 1ms, it will allow me to keep the edits without this issue cropping up. Of course, I'll leave such testing until after I'm confident the problem has been resolved.

 

[Virgorising]

I'm wondering if the culprit was setting the "delaybeforeacceptance" to 0. Perhaps if I set it to even 1ms, it will allow me to keep the edits without this issue cropping up. Of course, I'll leave such testing until after I'm confident the problem has been resolved.

I think you are very thorough and sharp. So, soon, you will know if that altered value messed you up or not.

 

[dippydoop]

Problem solved! Turns out, it was the registry settings in the first place. With the default registry settings, I could not replicate the issue. I also tried the modified registry settings with different values for DelayBeforeAcceptance including 1, 30 and 100, all to no avail. Playing games and even typing were pretty adversely affected with the latter two settings, but I was able to test long enough to replicate the issue.
I'm not sure which setting is responsible, or if it is the combination, but at this point, the occasional spacebar bounce is preferable to what I was having before.

I just want to thank everyone who commented in this thread, especially Virgorising, you've been really helpful! I'll update the main post so that others may more easily find the solution if they have the same problem.